-
Environmental Info:
Node(s) CPU architecture, OS, and Version:
Steps To Reproduce:
Expected behavior: Actual behavior: Additional context / logs:
Click me
kubectl get nodes -o yaml
|
Beta Was this translation helpful? Give feedback.
Replies: 6 comments
-
kubectl describe -n kube-system pod/kube-controller-manager-$(hostname)
|
Beta Was this translation helpful? Give feedback.
-
You don't appear to have any ipv6 cidrs allocated for your nodes: spec:
podCIDR: 10.42.0.0/24
podCIDRs:
- 10.42.0.0/24
providerID: rke2://<redacted-host> I noticed you said that you |
Beta Was this translation helpful? Give feedback.
-
I also see that the controller-manager args are showing only a single ipv4 cidr: |
Beta Was this translation helpful? Give feedback.
-
I did changes after the first start. I checked the documentation and did not find that it can not be changed after the first start. |
Beta Was this translation helpful? Give feedback.
-
CNI selection and cluster/service CIDRs cannot be changed once the cluster has already been started. We can leave this open to track adding this to the docs if you'd like. |
Beta Was this translation helpful? Give feedback.
-
Hey! I've upgraded successfully from k3s to rke2 because the rke2 docs are not stating that it can't be changed after initial setup and now i've stuck in the same situation. Folke |
Beta Was this translation helpful? Give feedback.
CNI selection and cluster/service CIDRs cannot be changed once the cluster has already been started. We can leave this open to track adding this to the docs if you'd like.