pf9-kube Fails to Start on Master Node(s)
PreviousUncordon Node After Maintenance to Make it Schedulable AgainNextUnable to Start pf9-kube Service on Master Node
Last updated
Cluster stays in a Pending state after creation.
One of the Master nodes is reporting as "Offline" or in an "Error Authorizing State"
In the Flannel logs on the node located at /var/log/pf9/kube/flannel.log, the following error can be observed.
{"log":"E1010 XX:XX:XX.583282 1 main.go:280] Error registering network: failed to acquire lease: out of subnets<br>","stream":"stderr","time":"XXXX-XX-XXTXX:XX:XX.1234Z"}Platform9 Managed Kubernetes - v3.6.0 and Higher
The container CIDR parameter specified during the cluster creation was too small.
Delete the existing cluster and try deploying a fresh cluster with Container CIDR values as /16.
Verify that cluster creation completes successfully and all the nodes become Ready.
Last updated
