kubectl-cordon
Mark a node as unschedulable, preventing new pods from being assigned to it. tldr-pages
On several platforms
Several platforms
Mark a node as unschedulable
kubectl cordon node_nameIdentifyMark multiple nodes as unschedulable
kubectl cordon node_name1 node_name2 ...IdentifyMark a node as unschedulable in a specific context
kubectl cordon node_name --context context_nameIdentify--contextThe name of the kubeconfig context to use kubectl referenceMark nodes matching a label selector as unschedulable
kubectl cordon --selector label_key=label_valueIdentify--selectorSelector (label query) to filter on, supports '=', '==', '!=', 'in', 'notin'.(e.g. -l key1=value1,key2=value2,key3 in (value3)). kubectl referenceSimulate the changes without actually cordoning the nodes
kubectl cordon node_name --dry-run=noneIdentify--dry-runMust be "none", "server", or "client". kubectl reference