Question

You run a web application as a Deployment with 3 replicas spread across a 3-node cluster. One worker node suddenly goes offline due to a hardware failure. After a few minutes, you notice the application is still serving traffic normally at full capacity. Which Kubernetes behavior best explains why the desired number of Pods was restored?

Accepted Answer

The Deployment's ReplicaSet controller observed fewer Ready Pods than desired and created replacement Pods, which the scheduler placed on the remaining healthy nodes.

Answer

The kube-scheduler detected the failure and directly restarted the missing Pods on the failed node once it recovered.

Answer

The kubelet on the failed node reconnected to the API server and migrated its Pods to another node automatically.

Answer

kube-proxy re-created the lost Pods on healthy nodes to keep the Service endpoints populated.