weird issue when creating any networking pluging

[K-Hamdy]

i have a weird issue when creating any networking plug in, it ends up in CrashLoopBackOff state on the worker node, the control node seems to be working.

Versions

kubeadm version (use kubeadm version):

Environment:

• Kubernetes version (use kubectl version):
  Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
  Server Version: v1.29.3
• Cloud provider or hardware configuration:
  VM on HyperV 2022
• OS (e.g. from /etc/os-release):
• Ubuntu 22
• Kernel (e.g. uname -a):
  Linux k8s-cn1 6.5.0-27-generic Implement support for Kubelet Dynamic Configuration #28~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 15 10:51:06 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
• Container runtime (CRI) (e.g. containerd, cri-o):
  containerd
• Container networking plugin (CNI) (e.g. Calico, Cilium):
• Others:

What happened?

any networking plug in i try it ends up in CrashLoopBackOff state

What you expected to happen?

to be in running state

How to reproduce it (as minimally and precisely as possible)?

install any CNI

Anything else we need to know?

[neolit123]

kubeadm is CNI setup agnostic, so likely there is something else going on your setup and it's not a kubeadm issue.
please, check support channel links from the bot below.

/support

[github-actions]

Hello, @K-Hamdy 🤖 👋

You seem to have troubles using Kubernetes and kubeadm.
Note that our issue trackers should not be used for providing support to users.
There are special channels for that purpose.

Please see:

• https://github.com/kubernetes/kubeadm#support