Difference between revisions of "Kubectl uncordon"
Jump to navigation
Jump to search
| Line 17: | Line 17: | ||
* <code>[[kubectl drain]]</code> | * <code>[[kubectl drain]]</code> | ||
* <code>[[kubectl cordon]]</code> | * <code>[[kubectl cordon]]</code> | ||
| − | * <code>[[kubectl get nodes]]</code> | + | * <code>[[kubectl get nodes -o wide]]</code> |
== Related == | == Related == | ||
Revision as of 10:03, 24 October 2023
kubectl uncordon mark node as schedulable.
kubectl uncordon ip-10-0-1-25.us-east-2.compute.internal node/ip-10-0-1-25.us-east-2.compute.internal uncordoned Verify: kubectl get nodes -w NAME STATUS ROLES AGE VERSION ip-10-0-1-25.us-east-2.compute.internal Ready <none> 4d19h v1.20.11-eks-f17b81 ip-10-0-3-240.us-east-2.compute.internal Ready,SchedulingDisabled <none> 4d19h v1.20.11-eks-f17b81
ip-10-0-3-240.us-east-2.compute.internal NotReady,SchedulingDisabled <none> 4d19h v1.23.13-eks-xxxxx
Related commands
Related
- How can I check, scale, delete, or drain my worker nodes in Amazon EKS?
SchedulingDisabledFailedScheduling
See also
- K8s nodes:
get | uncordon | cordon | drain | taint | describe | patch ] nodes - Kubernetes nodes,
node.kubernetes.ioK8s Node controller (node-controller),MemoryPressure, DiskPressure, NodeHasDiskPressure, events, NodeNotReady, Node-pressure Eviction, RemovingNode, ProviderID,kubectl node-shell, kubectl describe nodes
Advertising:
