kubectl uncordon: Usage, Options & Common CI Errors

Make a node schedulable again after maintenance or a drain.

kubectl uncordon clears the unschedulable flag on a node so the scheduler can place new pods there again. It is the essential cleanup step after a cordon or drain, and the one automation most often forgets.

What it does

kubectl uncordon NODE sets spec.unschedulable=false, reversing a cordon (or the cordon that drain applied). Existing pods are unaffected - uncordon only re-enables future scheduling. It is idempotent: uncordoning an already-schedulable node is a harmless no-op.

Common usage

Terminal

kubectl drain ip-10-0-1-5 --ignore-daemonsets
# ... node maintenance ...
kubectl uncordon ip-10-0-1-5
kubectl get nodes                       # SchedulingDisabled should be gone

Common errors in CI

The classic automation bug is a forgotten uncordon: a maintenance job cordons or drains a node, the uncordon step fails or is skipped, and new pods pile up Pending with "0/N nodes are available: N node(s) were unschedulable". Always run uncordon in a trap/finally so it executes even when the maintenance step errors. Because uncordon is idempotent, re-running it in a retried pipeline is safe. If pods stay Pending after uncordon, the node may still carry a taint (uncordon does not remove taints) - check kubectl describe node.

Related guides

kubectl Cheat Sheet: Commands for Everyday KubernetesA kubectl cheat sheet - get, describe, logs, apply, rollout, debug, and context commands for daily Kubernetes… kubectl drain --force: Usage, Options & Common CI Errorskubectl drain --force evicts pods including unmanaged bare pods. The DaemonSet and local-data flags, the PDB… kubectl taint nodes: Usage, Options & Common CI Errorskubectl taint nodes adds or removes node taints that repel pods without tolerations. Taint effects, removing… kubectl describe node: Usage, Options & Common CI Errorskubectl describe node shows taints, conditions, allocatable, and pod pressure. Diagnosing unschedulable pods…