问题原文
原帖链接 · sfgroups · CC BY-SA 4.0
I am trying to join new node to existing v1.21.3 cluster with Calico CNI. join command giving clusterCIDR warning.
How to fix this subnet warning message?
# kubeadm join master-vip:8443 --token xxx --discovery-token-ca-cert-hash sha256:xxxx
[preflight] Running pre-flight checks
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
W0809 14:10:27.717696 75868 utils.go:69] The recommended value for "clusterCIDR" in "KubeProxyConfiguration" is: 10.201.0.0/16; the provided value is: 10.203.0.0/16
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
update:
I was using 10.201.0.0/16 during the cluster setup, later I changed to 10.203.0.0/16. not sure where its still getting 10.201.0.0/16 subnet value.
Here is the sub net value.
# sudo cat /etc/kubernetes/manifests/kube-controller-manager.yaml | grep cluster-cidr
- --cluster-cidr=10.203.0.0/16
kubectl cluster-info dump | grep cluster-cidr
"--cluster-cidr=10.203.0.0/16",
"--cluster-cidr=10.203.0.0/16",
"--cluster-cidr=10.203.0.0/16",
step to update pod CIDR from 10.201.0.0/16 to 10.203.0.0/16
- using this command updated the kubeadm-confg configmap
kubectl -n kube-system edit cm kubeadm-config
podSubnet: 10.203.0.0/16
- Updated kuber-controller-manger and restarted it.
sed -i 's/10.201.0.0/10.203.0.0/' /etc/kubernetes/manifests/kube-controller-manager.yaml
after updating the IP.
all config shows subnet as 10.203.0.0 but pods creating in `10.201.0.0' subnet.
# kubectl get cm kube-proxy -n kube-system -o yaml |grep -i clusterCIDR
clusterCIDR: 10.203.0.0/16
# kubectl get no -o yaml |grep -i podcidr
podCIDR: 10.203.0.0/24
podCIDRs:
podCIDR: 10.203.1.0/24
podCIDRs:
podCIDR: 10.203.2.0/24
podCIDRs:
podCIDR: 10.203.3.0/24
podCIDRs:
podCIDR: 10.203.5.0/24
podCIDRs:
podCIDR: 10.203.4.0/24
podCIDRs:
podCIDR: 10.203.6.0/24
podCIDRs:
已采纳解答
原帖链接 · Mikolaj S. · CC BY-SA 4.0
I managed to replicate your issue. I got the same error. There is a need to update few other configuration files.
To fully change pods and nodes IP pool you need to update podCIDR and ClusterCIDR values in few configuration files:
update ConfigMap
kubeadm-confg- you did it alreadyupdate file
/etc/kubernetes/manifests/kube-controller-manager.yaml- you did it alreadyupdate node(s) definition with proper
podCIDRvalue and re-add them to the clusterupdate ConfigMap
kube-proxyinkube-systemnamespaceadd new IP pool in Calico CNI and delete the old one, recreate the deployments
Update node(s) definition:
- Get node(s) name(s):
kubectl get no- in my case it'scontroller - Save definition(s) to file:
kubectl get no controller -o yaml > file.yaml - Edit
file.yaml-> updatepodCIDRandpodCIDRsvalues with your new IP range, in your case10.203.0.0 - Delete old and apply new node definition:
kubectl delete no controller && kubectl apply -f file.yaml
Please note you need to do those steps for every node in your cluster.
Update ConfigMap kube-proxy in kube-system namespace
- Get current configuration of
kube-proxy:kubectl get cm kube-proxy -n kube-system -o yaml > kube-proxy.yaml - Edit
kube-proxy.yaml-> updateClusterCIDRvalue with your new IP range, in your case10.203.0.0 - Delete old and apply new
kube-proxyConfigMap:kubectl delete cm kube-proxy -n kube-system && kubectl apply -f kube-proxy.yaml
Add new IP pool in Calico and delete the old one:
Download the Calico binary and make it executable:
sudo curl -o /usr/local/bin/calicoctl -O -L "https://github.com/projectcalico/calicoctl/releases/download/v3.20.0/calicoctl" sudo chmod +x /usr/local/bin/calicoctlAdd new IP pool:
calicoctl create -f -<<EOF apiVersion: projectcalico.org/v3 kind: IPPool metadata: name: my-new-pool spec: cidr: 10.203.0.0/16 ipipMode: Always natOutgoing: true EOFCheck if there is new IP pool:
calicoctl get ippool -o wideGet the configuration to disable old IP pool ->
calicoctl get ippool -o yaml > pool.yamlEdit the configuration: -> add
disabled:truefordefault-ipv4-ippoolin thepool.yaml:apiVersion: projectcalico.org/v3 items: - apiVersion: projectcalico.org/v3 kind: IPPool metadata: creationTimestamp: "2021-08-12T07:50:24Z" name: default-ipv4-ippool resourceVersion: "666" spec: blockSize: 26 cidr: 10.201.0.0/16 ipipMode: Always natOutgoing: true nodeSelector: all() vxlanMode: Never disabled: trueApply new configuration:
calictoctl apply -f pool.yamlExcepted output of the
calicoctl get ippool -o widecommand:NAME CIDR NAT IPIPMODE VXLANMODE DISABLED SELECTOR default-ipv4-ippool 10.201.0.0/16 true Always Never true all() my-new-pool 10.203.0.0/16 true Always Never false all()Re-create pods that are in
10.201.0.0network (in every namespace, includingkube-systemnamespace): just delete them and they should re-create instantly in new IP pool range , for example:kubectl delete pod calico-kube-controllers-58497c65d5-rgdwl -n kube-system kubectl delete pods coredns-78fcd69978-xcz88 -n kube-system kubectl delete pod nginx-deployment-66b6c48dd5-5n6nw etc..You can also delete and apply deployments.
After applying those steps, there is no warning about clusterCIDR value when adding new node. New pods are created in proper IP pool range.
Source:
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
