Nodes are going in Ready,SchedulingDisabled status?

Question

Nodes are going in Ready,SchedulingDisabled status?

Tanul 1,226

Hello,

Nodes are automatically going in Ready,SchedulingDisabled status. Any suggestions please. How to debug ?

Prrudram-MSFT 19,966 Reputation points

2023-04-28T14:54:20.96+00:00
Hello @Tanul

When a node in an Azure Kubernetes Service (AKS) cluster goes into the "Ready,SchedulingDisabled" status, it means that the node is not able to schedule new pods. This can happen for a variety of reasons, such as resource constraints, network issues, or other problems.

To debug this issue, you can try the following steps:

Check the logs for the node to see if there are any error messages or other issues that may be causing it to go into the "Ready,SchedulingDisabled" status. You can do this by running the following command: kubectl logs <node-name>

Check the status of the pods running on the node to see if there are any issues with the pods that may be causing the node to go into the "Ready,SchedulingDisabled" status. You can do this by running the following command: kubectl get pods --all-namespaces -o wide

Check the resource utilization of the node to see if there are any resource constraints that may be causing the node to go into the "Ready,SchedulingDisabled" status. You can do this by running the following command: kubectl describe node <node-name>

Check the network connectivity of the node to see if there are any network issues that may be causing the node to go into the "Ready,SchedulingDisabled" status. You can do this by running the following command: kubectl exec -it <pod-name> -- /bin/bash

If none of these steps help in identifying the issue, you can contact microsoft azure technical support for further assistance.
Tanul 1,226 Reputation points

2023-04-28T15:06:44.13+00:00

@Prrudram-MSFT Is it a command. Does it exist for nodes?

kubectl logs <node-name>
Prrudram-MSFT 19,966 Reputation points

2023-04-28T16:52:27.9633333+00:00

@Tanul

For the commands please check the below link.

https://kubernetes.io/docs/reference/kubectl/cheatsheet/
Prrudram-MSFT 19,966 Reputation points

2023-05-03T13:32:55.07+00:00

@Tanul
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!

Prrudram-MSFT 19,966 Reputation points

2023-04-28T14:54:20.96+00:00

Hello @Tanul

When a node in an Azure Kubernetes Service (AKS) cluster goes into the "Ready,SchedulingDisabled" status, it means that the node is not able to schedule new pods. This can happen for a variety of reasons, such as resource constraints, network issues, or other problems.

To debug this issue, you can try the following steps:

Check the logs for the node to see if there are any error messages or other issues that may be causing it to go into the "Ready,SchedulingDisabled" status. You can do this by running the following command: kubectl logs <node-name>

Check the status of the pods running on the node to see if there are any issues with the pods that may be causing the node to go into the "Ready,SchedulingDisabled" status. You can do this by running the following command: kubectl get pods --all-namespaces -o wide

Check the resource utilization of the node to see if there are any resource constraints that may be causing the node to go into the "Ready,SchedulingDisabled" status. You can do this by running the following command: kubectl describe node <node-name>

Check the network connectivity of the node to see if there are any network issues that may be causing the node to go into the "Ready,SchedulingDisabled" status. You can do this by running the following command: kubectl exec -it <pod-name> -- /bin/bash

If none of these steps help in identifying the issue, you can contact microsoft azure technical support for further assistance.
Tanul 1,226 Reputation points

2023-04-28T15:06:44.13+00:00

@Prrudram-MSFT Is it a command. Does it exist for nodes?

kubectl logs <node-name>
Prrudram-MSFT 19,966 Reputation points

2023-04-28T16:52:27.9633333+00:00

@Tanul

For the commands please check the below link.

https://kubernetes.io/docs/reference/kubectl/cheatsheet/
Prrudram-MSFT 19,966 Reputation points

2023-05-03T13:32:55.07+00:00

@Tanul
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 1

Sedat SALMAN 10,495

If you have enabled the cluster autoscaler, it may have marked some nodes as unschedulable to ensure efficient resource utilization. This is normal behavior and should not cause any issues.

Check if any taints have been applied to the nodes. Taints can make nodes unschedulable unless a pod has a matching toleration

kubectl describe node <node_name>

Nodes can be marked as unschedulable if they were cordoned manually using the kubectl cordon command.

kubectl uncordon <node_name>

Tanul 1,226 Reputation points

2023-04-28T11:29:19.8066667+00:00

@Sedat SALMAN It has this taint

Taints: node.kubernetes.io/unschedulable:NoSchedule

But no one has added this.. How to know which user or process did this?

Should I just uncordon?
Sedat SALMAN 10,495 Reputation points

2023-05-01T08:03:53.23+00:00

If you see a taint on a node that is causing it to be unschedulable, and you don't know why it was added, you can try to investigate who or what added the taint by looking at the audit logs in Kubernetes.

Nodes are going in Ready,SchedulingDisabled status?

1 answer

Activity