Join Log in
Score:0
avatar Server

I installed kubeadm for Linux + Windows Server 2019 but it shows not ready for Windows Server node

US flag
cengiz.ilkerli

I installed kubeadm and kubernetes as a master-worker on Linux machines and Windows Server machines, kubectl and kubelet are running on both, when I say get nodes, I see both nodes, but I could not pass Not Ready for Windows Server machine, Master node ready is ok, calio works too

For Windows Server machine It says NetworkReady=false, but despite all my searches, I couldn't find how to set the network for kubeadm on Windows Server 2019 :(

Linux Machine

dev_cengizilkerli@TST-DEVOPSDMAN:~$ kubectl version --short
Flag --short has been deprecated, and will be removed in the future. The --short output will become the default.
Client Version: v1.26.0
Kustomize Version: v4.5.7
Server Version: v1.26.0

    
dev_cengizilkerli@TST-DEVOPSDMAN:~$ kubectl get pods -A
NAMESPACE     NAME                                      READY   STATUS    RESTARTS       AGE
default       firstpod                                  1/1     Running   0              9d
kube-system   calico-kube-controllers-7bdbfc669-jzqvw   1/1     Running   1 (13d ago)    28d
kube-system   calico-node-dbm5c                         1/1     Running   1 (13d ago)    28d
kube-system   coredns-787d4945fb-r2msf                  1/1     Running   1 (13d ago)    28d
kube-system   coredns-787d4945fb-stcrz                  1/1     Running   1 (13d ago)    28d
kube-system   etcd-tst-devopsdman                       1/1     Running   3 (13d ago)    28d
kube-system   kube-apiserver-tst-devopsdman             1/1     Running   3 (13d ago)    28d
kube-system   kube-controller-manager-tst-devopsdman    1/1     Running   20 (33h ago)   28d
kube-system   kube-proxy-fddtk                          1/1     Running   1 (13d ago)    28d
kube-system   kube-scheduler-tst-devopsdman             1/1     Running   22 (33h ago)   28d

Problem --> Status Not Ready

dev_cengizilkerli@TST-DEVOPSDMAN:~$ kubectl get nodes
NAME             STATUS     ROLES           AGE   VERSION
tst-devopsdman   Ready      control-plane   28d   v1.26.0
tst-devopsdw02   NotReady             15d   v1.26.0

Windows Server Machine Problem --> Status Not Ready

PS C:\Users\dev.cengiz.ilkerli> kubectl get nodes
NAME             STATUS     ROLES           AGE   VERSION
tst-devopsdman   Ready      control-plane   28d   v1.26.0
tst-devopsdw02   NotReady             15d   v1.26.0

Describe Windows Server Node

  Type             Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message
  ----             ------  -----------------                 ------------------                ------                       -------
  MemoryPressure   False   Thu, 26 Jan 2023 09:57:33 +0300   Wed, 11 Jan 2023 09:25:36 +0300   KubeletHasSufficientMemory   kubelet has sufficient memory available
  DiskPressure     False   Thu, 26 Jan 2023 09:57:33 +0300   Wed, 11 Jan 2023 09:25:36 +0300   KubeletHasNoDiskPressure     kubelet has no disk pressure
  PIDPressure      False   Thu, 26 Jan 2023 09:57:33 +0300   Wed, 11 Jan 2023 09:25:36 +0300   KubeletHasSufficientPID      kubelet has sufficient PID available
  Ready            False   Thu, 26 Jan 2023 09:57:33 +0300   Wed, 11 Jan 2023 09:25:36 +0300   KubeletNotReady              container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized

Problem: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized

I examined the explanations I found on the internet, but I could not take action.

129
0 + 0
ธงชาติไทย
Elon Musk
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.