Skip to content
New issue

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

Network plugin returns error: cni plugin not initialized #147

Open
stoica353 opened this issue Nov 12, 2024 · 0 comments
Open

Network plugin returns error: cni plugin not initialized #147

stoica353 opened this issue Nov 12, 2024 · 0 comments

Comments

@stoica353
Copy link

Hello,

I try to use the vagrant scripts but is not working well.
The nodes are up but not ready:

MemoryPressure False Tue, 12 Nov 2024 09:41:48 +0000 Tue, 12 Nov 2024 09:41:48 +0000 KubeletHasSufficientMemory kubelet has sufficient memory available
DiskPressure False Tue, 12 Nov 2024 09:41:48 +0000 Tue, 12 Nov 2024 09:41:48 +0000 KubeletHasNoDiskPressure kubelet has no disk pressure
PIDPressure False Tue, 12 Nov 2024 09:41:48 +0000 Tue, 12 Nov 2024 09:41:48 +0000 KubeletHasSufficientPID kubelet has sufficient PID available
Ready False Tue, 12 Nov 2024 09:41:48 +0000 Tue, 12 Nov 2024 09:41:48 +0000 KubeletNotReady container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized

My local subnet : 192.168.1.0/24

And I use:
kubeadm init --apiserver-advertise-address=172.16.16.100 --pod-network-cidr=172.18.0.0/16
or
kubeadm init --apiserver-advertise-address=172.16.16.100 --pod-network-cidr=192.169.0.0/16

Should I include one of the interface to my localsubnet?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant