Needed help with kubernates nodes NotReady state

DevSecOps
#1

When I follow the same steps as in video, after installation script run it’s showing the node are in Not Ready state. I describe for more info >> getting Kube-proxy starting

And it’s from last 20 min but still nodes are not in ready state

Using Azure cloud >> using same config from session .json

#2

Hello @glis_training3_chtf,
First, describe nodes and see if it reports anything:

$ kubectl describe nodes

#3

Greetings guys,
Think am facing the same challenge, been having a hard time with this error following the devsecops video training instruction. Anyone knows why and how to fix this error, kindly help pls.
I’m deploying in the master node in AzureCloud and am using the “install-script.sh” provided by the trainer. I understand It seems in my cluster, there is only one node and that has taints and may be why am not getting it deployed on the master node. But how do i go about removing the taints on a master node, what changes do i need o make and where should the changes be made exactly? Thanks in advance for your quick response.

Screen Shot 2023-02-08 at 03.30.25
Screen Shot 2023-02-08 at 03.30.251051×599 60.6 KB

#4

Hi @Sammy-Chuks,

Please check the taints on the master node.

kubectl get nodes

Then, fetch the applied/default taint.

kubectl describe node <node-name> | grep -i taint

Then, add a minus sign at the end of the taint to remove the applied/default taint.

kubectl taint node <node-name> <taint>-

Regards,

#5

Please follow the above steps and let us know.

#6

Hello everybody,

running the install-script.sh the node not get Ready status.

It was not possible install the CNI plugin.
k describe node output show this:

Conditions:
  Type             Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message
  ----             ------  -----------------                 ------------------                ------                       -------
  MemoryPressure   False   Sun, 12 Feb 2023 17:59:03 +0000   Sun, 12 Feb 2023 17:28:40 +0000   KubeletHasSufficientMemory   kubelet has sufficient memory available
  DiskPressure     False   Sun, 12 Feb 2023 17:59:03 +0000   Sun, 12 Feb 2023 17:28:40 +0000   KubeletHasNoDiskPressure     kubelet has no disk pressure
  PIDPressure      False   Sun, 12 Feb 2023 17:59:03 +0000   Sun, 12 Feb 2023 17:28:40 +0000   KubeletHasSufficientPID      kubelet has sufficient PID available
  Ready            False   Sun, 12 Feb 2023 17:59:03 +0000   Sun, 12 Feb 2023 17:28:40 +0000   KubeletNotReady              runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized

From commands of installation script this one didn’t work for me:
kubectl apply -f "https://cloud.weave.works/k8s/net?k8s-version=$(kubectl version | base64 | tr -d '\n')"

root@devsecops-cloud:~# curl "https://cloud.weave.works/k8s/net?k8s-version=$(kubectl version | base64 | tr -d '\n')"
curl: (6) Could not resolve host: cloud.weave.works

Checking weave documentation I saw that it is possible install with this command from the VM:
kubectl apply -f https://github.com/weaveworks/weave/releases/download/v2.8.1/weave-daemonset-k8s.yaml

Once executed this command the state was Ready and pods were accessible.

I share in case it can help someone else.

1 Like