Managed Kubernetes
Latest
Frequently Asked Questions
Solutions
How Tos
Internal Only
Templates
Powered By

Title
Message
Create new category
What is the title of your new category?
Edit page index title
What is the title of the page index?
Edit category
What is the new title of your category?
Edit link
What is the new title and URL of your link?
Kubernetes Node in NotReady State After Reboot for Containerd Runtime Cluster
Copy Markdown
Open in ChatGPT
Open in Claude
Problem
- A Kubernetes (master or worker) node that has been rebooted (e.g. due to a maintenance activity) is showing as
NotReady.
Node Status
xxxxxxxxxx$ kubectl get nodesNAME STATUS ROLES AGE VERSIONmaster1 NotReady master 34d v1.21.3master2 Ready master 34d v1.21.3master3 Ready master 34d v1.21.3- A description of the node similarly reports
KubeletNotReadydue to the CNI plugin being uninitialized.
Node Description
$ kubectl describe node master1.....Conditions:Ready False Mon, 13 Jun 2022 21:42:05 +0000 Mon, 13 Jun 2022 21:32:01 +0000 KubeletNotReady container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initializedEnvironment
- Platform9 Managed Kubernetes - v5.4 and Higher
- Kubernetes - All 1.21 versions except v1.21.3-pmk.183
- Runtime - Containerd
Cause
Due to an upstream issue in containerd, the CNI config is not reloaded when the directory is deleted and recreated during the Platform9 Kubernetes stack initialization.
Resolution
- This issue is now fixed on the pf9-kube-1.21.3-pmk.183. and above releases.
Workaround
- Verify that the CNI configuration directory referenced by containerd is not empty.
For Flannel based clusters the directory should contain the following files:
Javascript
xxxxxxxxxx# ls -l /etc/cni/net.d/total 4-rw-r--r-- 1 root root 362 Jun 16 14:45 10-flannel.conflistFor Calico based clusters the directory should contain the following files:
Bash
xxxxxxxxxx# ls -l /etc/cni/net.d/total 8-rw-r--r-- 1 root root 730 Jun 16 14:16 10-calico.conflist-rw------- 1 root root 3094 Jun 16 14:16 calico-kubeconfig- Restart containerd service on the affected node.
Restarting containerd will not affect restart any running containers
Bash
xxxxxxxxxx# sudo systemctl restart containerdThe Kubernetes nodes should now all show as Ready .
- Verify the status of the node after restarting containerd
Node Status
xxxxxxxxxx# kubectl get nodesNAME STATUS ROLES AGE VERSIONmaster1 Ready master 34d v1.21.3master2 Ready master 34d v1.21.3master3 Ready master 34d v1.21.3VariableType to search · ESC to discard
GlossaryType to search · ESC to discard
InsertType to search · ESC to discard
No matches
Last updated on
Was this page helpful?
Discard Changes
Do you want to discard your current changes and overwrite with the template?
Archive Synced Block
Message
Create new Template
What is this template's title?
Delete Template
Message