You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After rebooting a Node pods are stuck in container creating with this error
Warning FailedCreatePodSandBox 1s kubelet (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_coredns-7c65d6cfc9-prlbd_kube-system_335070f1-cc11-4569-bf97-e2ba7d480ee2_0(a1e1f9e2930f82a9d88d50b6245a88310d610bd04229384a24b354d172c2030e): error adding pod kube-system_coredns-7c65d6cfc9-prlbd to CNI network "cbr0": plugin type="flannel" failed (add): loadFlannelSubnetEnv failed: open /run/flannel/subnet.env: no such file or directory
Possible Solution
Is there Documentation on how to properly remove flannel from a cluster?
I am trying to uninstall flannel and install a CNI that supports NetworkPolicies (kube-router)
Do to the wording of the error, it looks like flannel was not completely uninstalled with the kubectl command. plugin type="flannel" failed (add): loadFlannelSubnetEnv failed: open /run/flannel/subnet.env: no such file or directory
Expected Behavior
kubectl delete -f https://github.com/flannel-io/flannel/releases/latest/download/kube-flannel.yml
Should cleanly uninstall flannel
Current Behavior
After rebooting a Node pods are stuck in container creating with this error
Possible Solution
Is there Documentation on how to properly remove flannel from a cluster?
Steps to Reproduce (for bugs)
Context
I am trying to uninstall flannel and install a CNI that supports NetworkPolicies (kube-router)
Do to the wording of the error, it looks like flannel was not completely uninstalled with the kubectl command.
plugin type="flannel" failed (add): loadFlannelSubnetEnv failed: open /run/flannel/subnet.env: no such file or directory
Your Environment
Launched with
kubeadm init --pod-network-cidr=10.244.0.0/16
The text was updated successfully, but these errors were encountered: