forgejo/infrastructure-documentation
1
0
Fork 0
mirror of https://code.forgejo.org/infrastructure/documentation synced 2024-11-22 03:21:10 +00:00
Code Issues Activity

k8s: the ipv6 range for nodes must not conflict with cluster/service

Browse source
This commit is contained in:
Earl Warren 2024-10-06 12:06:13 +02:00
parent aeda8706d3
commit efedb1db3c
No known key found for this signature in database
GPG key ID: 0579CB2928A78A00
1 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
README.md
View file

@ -799,7 +799,7 @@ iface enp5s0 inet6 static
#### k8s node #### k8s node
The `10.88.1.5` and `fd01::5` IPs are assigned to the interface with VLAN 4002. The `10.88.1.5` and `fe88::5` IPs are assigned to the interface with VLAN 4002.
``` ```
auto enp5s0.4002 auto enp5s0.4002
@ -808,7 +808,7 @@ iface enp5s0.4002 inet static
netmask 255.255.0.0 netmask 255.255.0.0
vlan-raw-device enp5s0 vlan-raw-device enp5s0
mtu 1400 mtu 1400
up ip addr add fd01::5/48 dev enp5s0.4002 up ip addr add fe88::5/48 dev enp5s0.4002
``` ```
### k8s first server node ### k8s first server node
@ -827,7 +827,7 @@ disable:
```sh ```sh
sudo apt-get install curl sudo apt-get install curl
curl -sfL https://get.k3s.io | INSTALL_K3S_EXEC="--write-kubeconfig-mode=644 --cluster-init --node-ip=10.88.1.5,fd01::5" sh - curl -sfL https://get.k3s.io | INSTALL_K3S_EXEC="--write-kubeconfig-mode=644 --cluster-init --node-ip=10.88.1.5,fe88::5" sh -
curl -fsSL https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash - curl -fsSL https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash -
``` ```
@ -850,7 +850,7 @@ The token is found on the first node in the `/var/lib/rancher/k3s/server/token`
```sh ```sh
sudo apt-get install curl sudo apt-get install curl
master_node_ip=10.88.1.5 master_node_ip=10.88.1.5
second_server_ip=10.88.1.6,fd01::6 second_server_ip=10.88.1.6,fe88::6
curl -sfL https://get.k3s.io | INSTALL_K3S_EXEC="--write-kubeconfig-mode=644 --token $token --server https://$master_node_ip:6443 --node-ip=$second_server_ip" sh - curl -sfL https://get.k3s.io | INSTALL_K3S_EXEC="--write-kubeconfig-mode=644 --token $token --server https://$master_node_ip:6443 --node-ip=$second_server_ip" sh -
curl -fsSL https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash - curl -fsSL https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash -
``` ```
@ -863,7 +863,7 @@ The token is found on one of the master nodes in the `/var/lib/rancher/k3s/serve
```sh ```sh
master_node_ip=10.88.1.5 master_node_ip=10.88.1.5
etcd_node_ip=10.88.1.3,fd01::3 etcd_node_ip=10.88.1.3,fe88::3
curl -fL https://get.k3s.io | sh -s - server --token "$token" --server https://$master_node_ip:6443 --cluster-init --disable-apiserver --disable-controller-manager --disable-scheduler --write-kubeconfig-mode=644 --node-ip=$etcd_node_ip --cluster-cidr=10.42.0.0/16,fd01::/48 --service-cidr=10.43.0.0/16,fd02::/112 curl -fL https://get.k3s.io | sh -s - server --token "$token" --server https://$master_node_ip:6443 --cluster-init --disable-apiserver --disable-controller-manager --disable-scheduler --write-kubeconfig-mode=644 --node-ip=$etcd_node_ip --cluster-cidr=10.42.0.0/16,fd01::/48 --service-cidr=10.43.0.0/16,fd02::/112
``` ```