Skip to content

Latest commit

 

History

History
30 lines (23 loc) · 619 Bytes

File metadata and controls

30 lines (23 loc) · 619 Bytes

Testing pod rescheduling after draining a worker node

This experiment demonstrates how Kubernetes reschedules pods when a node is drained.

Steps

  1. Deploy a test application:

    kubectl create deployment nginx --image=nginx --replicas=3
  2. Check pod distribution:

    kubectl get pods -o wide
  3. Drain a worker node:

    kubectl drain k3s-worker-1 --ignore-daemonsets --delete-emptydir-data
  4. Observe rescheduling:

    kubectl get pods -o wide
  5. Uncordon the node:

    kubectl uncordon k3s-worker-1