Kubernetes - Advanced Deployment Patterns
You deployed a new version of your app with label
version: v2 but traffic is still going only to v1. What is a likely cause?You deployed a new version of your app with label version: v2 but traffic is still going only to v1. What is a likely cause?
medium📝 Troubleshoot Q14 of 15
Step-by-Step Solution
Solution:
Step 1: Check service selector labels
If the service selector targets version v1, traffic won't reach v2 pods.Step 2: Verify deployment replicas and pod status
If replicas for v2 are zero or pods are not running, no v2 pods receive traffic.Final Answer:
All of the above -> Option DQuick Check:
Service selector + replicas + pod status all affect traffic [OK]
Quick Trick: Check service selector, replicas, and pod health for traffic issues [OK]
Common Mistakes:
- Only checking one cause and ignoring others
- Assuming pods labeled v2 always run
- Not verifying service selectors
Master "Advanced Deployment Patterns" in Kubernetes
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kubernetes Quizzes