What problem can a breaking API change cause during a rolling update?
Tests if you know rolling updates run mixed versions, so breaking API changes crash cross-traffic. Good answer: note old and new pods serve together, watch probes fail, and monitor 5xx spikes. Red flag: claiming Kubernetes isolates versions during rollout.
WHAT IT TESTS: Whether you know rolling updates run old and new pods together, so breaking API changes cause cross-version failures. ANSWER OUTLINE: Note that the Service sends traffic to both ReplicaSets during rollout; explain that breaking request or response contracts make old-to-new calls fail; detect via readiness probe failures, HTTP 5xx spikes, and canary checks. RED FLAG: Believing zero-downtime means zero-risk, or that Kubernetes drains old pods before starting new ones.
Read the original → geeksforgeeks.org
- #kubernetes
- #rolling-update
- #deployment
- #observability
- #api-design
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.