liveBook · Manning

Kubectl uncordon

As explained in Acing the Certified Kubernetes Administrator Exam, Second Edition

Uncordon is the operation of removing a Kubernetes node's unschedulable status so new pods can be scheduled onto it.

kubectl uncordon removes a node’s unschedulable status, allowing newly scheduled pods to use the node again. It does not evict pods already running there. section 5.2 section 5.2.1

Use uncordon as the final step of node maintenance:

  • Cordon the node to prevent new pods from being scheduled onto it. section 5.2.1
  • Drain the node to evict eligible pods and let controllers recreate them elsewhere. section 5.2.1
  • Run kubectl uncordon <node-name> to re-enable scheduling after maintenance. section 5.2
  • Verify the node no longer shows SchedulingDisabled with kubectl get no. section 5.2

Restore scheduling after draining a worker

After draining kind-worker and confirming workloads have moved, run kubectl uncordon kind-worker. Kubernetes reports node/kind-worker uncordoned, and new pods can again be scheduled there. section 5.2

How Acing the Certified Kubernetes Administrator Exam, Second Edition covers it

How deep it goes
Explains the command within a maintenance workflow and distinguishes scheduling from eviction, without detailing API internals.
Examples
Demonstrates kubectl uncordon kind-worker after draining workloads and verifies the resulting node status.
What it assumes
Assumes familiarity with nodes and pods while teaching cordon, drain, and uncordon as a maintenance sequence.
What you can do after
Operate node maintenance by restoring scheduling and verifying that SchedulingDisabled is absent.
How it connects
Connects node scheduling with cordon, drain, pods, ReplicaSets, Deployments, and DaemonSets.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Acing the Certified Kubernetes Administrator Exam, Second Edition. The section links point to the parts of the book it draws on.