Increase Existing Kubernetes Cluster Node Count for Flannel CNI
Problem
During cluster creation, the container CIDR value for a cluster having Flannel CNI was set to 10.20.0.0/16. This will allow for a maximum of 256 nodes considering the CNI interfaces have a /24 CIDR.
Can the Container CIDR be modified for an existing cluster to say, for example /14 to allow the addition of worker nodes beyond the current limit?
Environment
- Platform9 Managed Kubernetes - All Versions
- Flannel
Procedure
Customers will need to ensure all running pods/workloads within the cluster are terminated prior to this operation.
- Contact Platform9 Support so that they make the changes in the Backend Qbert DB to update the containerCIDR to a new subnet for the cluster.
- Once the change is done, delete cni0 and flannel0 interfaces on all the nodes part of the cluster.
- Restart the PMK stack in a rolling fashion on the Master Nodes which will tear down everything including any running pods and starts over again.
- Perform the same PMK Stack restart operation in batches or all together for the Worker nodes.
- Post that, ensure that the cni0 and flannel0 interfaces comes up with the changed CIDR values.
- Test the pod deployment and the Pod to Pod connectivity amongst the master and worker nodes.
Was this page helpful?