it-wiki:kubernetes:change_cluster_network
Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
| Nächste Überarbeitung | Vorhergehende Überarbeitung | ||
| it-wiki:kubernetes:change_cluster_network [2023/08/12 09:14] – angelegt marko | it-wiki:kubernetes:change_cluster_network [2023/10/05 12:03] (aktuell) – [Changing the default ip range] marko | ||
|---|---|---|---|
| Zeile 13: | Zeile 13: | ||
| <code bash> | <code bash> | ||
| / | / | ||
| + | </ | ||
| + | and this file: | ||
| + | <code bash> | ||
| + | / | ||
| </ | </ | ||
| - | After doing this in all master nodes and rebooting I can see that the services are using 172.26.0.0/16 range. | + | Backup |
| + | <code bash> | ||
| - | Probably it will give an error for 172.26.0.1 as this ip is not recognized by the PKI. | + | Save all svcs and recreate svcs: |
| + | <code bash> | ||
| + | kubectl get svc --all-namespaces | grep -v -w kubernetes| awk '$4 !~ / | ||
| - | In k8s 1.12 it can be fixed using: | + | kubectl get svc --all-namespaces | awk '$4 !~ / |
| + | |||
| + | kubectl apply -f all_svc.yaml | ||
| + | </ | ||
| + | |||
| + | update the cluster DNS: | ||
| <code bash> | <code bash> | ||
| - | kubeadm alpha phase certs all --apiserver-advertise-address 0.0.0.0 | + | kubectl get svc -A |grep dns |
| - | --apiserver-cert-extra-sans=< | + | |
| </ | </ | ||
| + | change entry in | ||
| + | / | ||
| + | for the intern connecting to kube-api server | ||
| + | <code bash> | ||
| + | server: https:// | ||
| + | </ | ||
| + | and change init.yml file | ||
| + | <code bash> | ||
| + | networking: | ||
| + | serviceSubnet: | ||
| + | podSubnet: 172.20.0.0/ | ||
| + | </ | ||
| + | |||
| + | # change kubelet config | ||
| + | <code bash> | ||
| + | kubectl -n kube-system edit cm kubelet-config | ||
| + | </ | ||
| + | |||
| + | update the apiserver certs: | ||
| + | <code bash> | ||
| + | kubeadm init phase certs apiserver --config=kubeadm.yaml | ||
| + | |||
| + | kubeadm upgrade node phase kubelet-config | ||
| + | |||
| + | systemctl restart kubelet | ||
| + | </ | ||
| + | |||
| + | |||
| + | After doing this in all master nodes and rebooting I can see that the services are using 172.26.0.0/ | ||
it-wiki/kubernetes/change_cluster_network.1691831643.txt.gz · Zuletzt geändert: von marko