Nodes Not ready state

Question

Hi Team,

I am trying to provision AKS cluster and the nodes are ending with Not ready state. These are the system/default nodes. Can you please help me with this.

Steps tried:

Multiple times re-provisioned the cluster and VMSS.
Deleted nodes and start them manually.

Answer 1

Hi @Santhosh kumar Bhandari ,

Thank you for your question.

What is the error you see when the AKS creation fails?

In general, the most common issue people face with this type of problem is the network setup. Make sure that the created nodes/VMs are able to reach the internet.

Take a look at this document for the endpoints that the cluster has to have access to.

Please Accept the answer if the information helped you. This will help us and others in the community as well.

Answer 2

Hello Santhosh kumar Bhandari,

Welcome to microsoft Q&A, thankyou for posting your query here.

Use the kubectl get events command to search for any error events associated with the nodes not reaching readiness. The reason for the issue may be shown by these occurrences.

Get thorough details about the particular node and possible causes for its "Not Ready" state by using the command kubectl describe node <node-name>.Look through the impacted node's kubelet logs. To review the logs, you must gain access to the virtual machine instance that is hosting the node.

Nodes that are unable to attain a "Ready" status are frequently the result of network problems. Check to see if the nodes can access the necessary endpoints for AKS capability and have internet connectivity.

https://learn.microsoft.com/en-us/azure/aks/outbound-rules-control-egress

Examine the diagnostics overview provided by Azure Kubernetes Service (AKS) to find possible problems on the nodes." Issues with IOPS performance, SNAT failures, and node faults may be revealed by this.

Please check if the cause of the problems is described below by clicking on these links.

https://github.com/Azure/AKS/issues/587

https://learn.microsoft.com/en-us/troubleshoot/azure/azure-kubernetes/availability-performance/node-not-ready-after-being-healthy

Hope this helps you.

If an answer has been helpful, please consider accepting the answer to help increase visibility of this question for other members of the Microsoft Q&A community. If not, please let us know what is still needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!

Answer 3

I had to dig a bit into the AKS architecture.

I found the issue, When we use the AKS with the Authorized ip enabled. It is not adding the node IP range with the cluster which is causing the cluster to restrict the node ip range.

I think, the cluster should be able to add the default Node pool IP ranges automatically while provisioning to avoid the cluster restricting the default Node pools.