My worker node status is Ready,SchedulingDisabled

scheduling disabled represents that node got into maintenance mode , as you drained nodes of the pods which has prerequisite that the node must be in maintenance . check the spec of that nodes kubetcl get nodes node-name -o yaml

 taints:
  - effect: NoSchedule
    key: node.kubernetes.io/unschedulable
    timeAdded: "2022-06-29T13:05:11Z"
  unschedulable: true

so when you want it to be back to schedulable state you will have to put node out of maintenance means uncordon it

kubectl uncordon <node-name>

I know it's similar to above answers but one should know what's happening behind the scenes .


I fixed it using:

kubectl uncordon <node-name>

To prevent a node from scheduling new pods use:

kubectl cordon <node-name>

Which will cause the node to be in the status: Ready,SchedulingDisabled.

To tell is to resume scheduling use:

kubectl uncordon <node-name>

More information about draining a node can be found here. And manual node administration here

Tags:

Kubernetes