Interview Kubernetes, Docker, Helm & Podman

How does Kubernetes handle a node that becomes NotReady?

Kubernetes, Docker, Helm & Podman · Intermediate level

Answer

When a node becomes NotReady, Kubernetes stops treating it as healthy, stops routing to affected endpoints as conditions update, and eventually evicts Pods after configured toleration periods. Controllers then recreate Pods elsewhere if capacity exists.

Technical explanation

Node conditions and taints such as node.kubernetes.io/not-ready influence scheduling and eviction behavior.

Stateful workloads may require careful storage reattachment before replacement Pods become healthy.

Troubleshooting starts from state and events: get, describe, logs, previous logs, events, and then node/runtime/network checks.

Separate scheduling failures, image pull failures, runtime failures, app failures, and traffic-routing failures so you do not fix the wrong layer.

Operational commands like drain and rollback must respect PDBs, probes, and workload disruption tolerance.

Hands-on example

1. In a non-production namespace, create this safe broken scenario: simulate a NotReady node in a lab and observe taints and rescheduling.

2. Follow a fixed triage order: kubectl get, describe, logs or logs --previous, events, rollout status, node status, and then runtime/network checks.

3. Fix only one variable at a time so the root cause is clear rather than accidentally masked.

4. Save the commands and final diagnosis as an interview-ready incident walkthrough.

Preparing for an interview?

Check how well your resume matches the role with our free resume checker— match score, ATS check, and the skills you're missing.

More Kubernetes, Docker, Helm & Podman interview questions

← All Kubernetes, Docker, Helm & Podman questions