You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/installation/airgap.md
+22-13Lines changed: 22 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,11 +36,14 @@ This method requires you to manually deploy the necessary images to each node, a
36
36
37
37
#### Prepare the Images Directory and Airgap Image Tarball
38
38
39
-
1. Obtain the images archive for your architecture from the [releases](https://github.com/k3s-io/k3s/releases) page for the version of K3s you will be running.
40
-
2. Download the images archive to the agent's images directory, for example:
39
+
1. On internet accessible machine, download the images archive for your architecture from the [releases](https://github.com/k3s-io/k3s/releases) page for the version of K3s you will be running. For example:
3. Proceed to the [Install K3s](#2-install-k3s) section below.
46
49
@@ -90,18 +93,21 @@ Before installing K3s, choose one of the [Load Images](#1-load-images) options a
90
93
- Download the K3s binary from the [releases](https://github.com/k3s-io/k3s/releases) page, matching the same version used to get the airgap images. Place the binary in `/usr/local/bin` on each air-gapped node and ensure it is executable.
91
94
- Download the K3s install script at [get.k3s.io](https://get.k3s.io). Place the install script anywhere on each air-gapped node, and name it `install.sh`.
92
95
93
-
#### Default Network Route
94
-
If your nodes do not have an interface with a default route, a default route must be configured; even a black-hole route via a dummy interface will suffice. K3s requires a default route in order to auto-detect the node's primary IP, and for kube-proxy ClusterIP routing to function properly. To add a dummy route, do the following:
95
-
```
96
-
ip link add dummy0 type dummy
97
-
ip link set dummy0 up
98
-
ip addr add 203.0.113.254/31 dev dummy0
99
-
ip route add default via 203.0.113.255 dev dummy0 metric 1000
100
-
```
101
96
102
-
When running the K3s script with the `INSTALL_K3S_SKIP_DOWNLOAD` environment variable, K3s will use the local version of the script and binary.
97
+
<details>
98
+
<summary>**Default Network Route**</summary>
103
99
104
-
#### SELinux RPM
100
+
If your nodes do not have an interface with a default route, a default route must be configured; even a black-hole route via a dummy interface will suffice. K3s requires a default route in order to auto-detect the node's primary IP, and for kube-proxy ClusterIP routing to function properly. To add a dummy route, do the following:
101
+
```
102
+
ip link add dummy0 type dummy
103
+
ip link set dummy0 up
104
+
ip addr add 203.0.113.254/31 dev dummy0
105
+
ip route add default via 203.0.113.255 dev dummy0 metric 1000
106
+
```
107
+
</details>
108
+
109
+
<details>
110
+
<summary>**SELinux RPM**</summary>
105
111
106
112
If running on an air-gapped node with SELinux enabled, you must manually install the k3s-selinux RPM before installing K3s. This RPM includes the necessary SELinux policies for K3s to run properly. The latest version of the RPM can be found [here](https://github.com/k3s-io/k3s-selinux/releases/latest). For example, on CentOS 8:
107
113
@@ -119,6 +125,9 @@ The k3s-selinux RPM installation requires the following dependencies to be avail
119
125
120
126
See the [SELinux](../advanced.md#selinux-support) section for more information.
121
127
128
+
</details>
129
+
130
+
122
131
### Running Install Script
123
132
124
133
You can install K3s on one or more servers as described below.
0 commit comments