Difference between revisions of "Kubectl uncordon"

From wikieduonline
Jump to navigation Jump to search
Line 10: Line 10:
 
  ip-10-0-1-25.us-east-2.compute.internal    Ready                      <none>  4d19h  v1.20.11-eks-f17b81
 
  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  Ready,[[SchedulingDisabled]]  <none>  4d19h  v1.20.11-eks-f17b81
 +
 +
 +
 +
ip-10-0-3-240.us-east-2.compute.internal  NotReady,[[SchedulingDisabled]]  <none>  4d19h  v1.20.11-eks-f17b81
 +
  
 
== Related ==
 
== Related ==

Revision as of 17:19, 13 December 2022

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.20.11-eks-f17b81


Related

See also

Advertising: