Using kubectl uncordon allows administrators to re-enable scheduling on a Kubernetes node that was previously cordoned off. When a node is cordoned, it prevents new pods from being scheduled onto it, typically for maintenance or troubleshooting purposes. Uncordoning a node makes it available again for pod scheduling.
Here are some examples of how to use kubectl uncordon:
Example 1: Uncordon a specific node named node-1:
kubectl uncordon node-1
This command instructs Kubernetes to allow pod scheduling on node-1 again. Verification can be done by checking the node’s status using:
kubectl get nodes node-1
Example 2: Uncordon a node using its IP address:
kubectl uncordon 192.168.1.100
This command uncordons the node with the IP address 192.168.1.100.
Example 3: Uncordon the first unavailable node listed:
kubectl get nodes -o name | head -n 1 | xargs -I{} kubectl uncordon {}
This example uses a pipeline to uncordon the first node returned by kubectl get nodes. Verification involves checking the status of the node post-uncordon.
Example 4: Uncordon a node by label selector:
kubectl uncordon $(kubectl get nodes -l environment=production -o name)
This command uncordons all nodes labeled with environment=production. Verification requires checking the status of each node labeled accordingly.
Example 5: Uncordon all nodes at once:
kubectl get nodes -o name | xargs -I{} kubectl uncordon {}
Executing this command uncordons every node in the Kubernetes cluster simultaneously.
Example 6: Uncordon a node after draining it:
kubectl drain node-2 --ignore-daemonsets --force && kubectl uncordon node-2
This sequence first drains node-2 of pods and then uncordons it. Verification involves ensuring no pods remain on node-2 after the drain and checking its status.
Example 7: Uncordon a node with force if it’s already uncordoned:
kubectl uncordon --force node-3
This command forces the uncordon operation on node-3, even if it is already uncordoned. Verification checks the status of node-3 to confirm scheduling is allowed.
Example 8: Uncordon a node with more verbose output:
kubectl uncordon --v=6 node-4
This command provides detailed debugging information during the uncordon operation on node-4.
Example 9: Uncordon a node using a dry run:
kubectl uncordon --dry-run=client node-5
This performs a dry run of the uncordon operation on node-5, providing feedback without making actual changes.
Example 10: Uncordon a node with a timeout:
kubectl uncordon --timeout=30s node-6
This command sets a timeout of 30 seconds for the uncordon operation on node-6. Verification involves checking the status of the node within the specified timeout period.
Also check similar articles.
How to Cordon Kubernetes Nodes with kubectl cordon
Monitor Resource Usage with kubectl top
Access Cluster Information Using kubectl cluster-info
Managing Kubernetes Certificates with kubectl certificate
Implement Auto-Scaling in Kubernetes with kubectl autoscale
Discussion about this post