We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
master节点重加后一直notready: "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized"
Type: bug report
加点容器都正常: #kubectl get pod -A -owide |grep |grep hybridnet kube-system hybridnet-daemon-2hrrf 1/1 Running 0 44m kube-system hybridnet-manager-578644b4dd-lcbv6 1/1 Running 0 5m24s kube-system hybridnet-webhook-668b75b9f4-wl67v 1/1 Running 0 4m17s
#kubectl get node -A -owide |grep NotReady control-plane,master 2d10h v1.28.2 containerd://1.6.28
cat /etc/os-release
uname -a
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Bug Report
master节点重加后一直notready: "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized"
Type: bug report
What happened
master节点重加后一直notready: "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized"
加点容器都正常:
#kubectl get pod -A -owide |grep |grep hybridnet
kube-system hybridnet-daemon-2hrrf 1/1 Running 0 44m
kube-system hybridnet-manager-578644b4dd-lcbv6 1/1 Running 0 5m24s
kube-system hybridnet-webhook-668b75b9f4-wl67v 1/1 Running 0 4m17s
#kubectl get node -A -owide |grep
NotReady control-plane,master 2d10h v1.28.2 containerd://1.6.28
What you expected to happen
How to reproduce it (as minimally and precisely as possible)
Anything else we need to know?
Environment
cat /etc/os-release
): alios7.2uname -a
): 4.19The text was updated successfully, but these errors were encountered: