After updating your Kubernetes Service selector to version: green, users still reach the blue pods. Which of the following is the most probable cause?

medium📝 Troubleshoot Q6 of 15

Kubernetes - Advanced Deployment Patterns

After updating your Kubernetes Service selector to version: green, users still reach the blue pods. Which of the following is the most probable cause?

AThe Service selector syntax is invalid and ignored by Kubernetes.

BThe green pods are not ready or not running, so Service falls back to blue pods.

CThe blue pods have higher priority and override the selector.

DKubernetes caches the old selector for 24 hours before applying changes.

Step-by-Step Solution

Solution:

Step 1: Check pod readiness
Service only routes traffic to pods that are ready and match the selector.
Step 2: Impact of pod readiness on routing
If green pods are not ready or not running, the Service cannot route traffic to them, so traffic remains on blue pods.
Final Answer:
The green pods are not ready or not running, so Service falls back to blue pods. -> Option B
Quick Check:
Verify pod readiness status [OK]

Quick Trick: Service routes only to ready pods matching selector [OK]

Common Mistakes:

Assuming selector syntax errors cause fallback
Believing blue pods override selectors
Thinking Kubernetes caches selectors for long periods

Master "Advanced Deployment Patterns" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More Kubernetes Quizzes

After updating your Kubernetes Service selector to version: green, users still reach the blue pods. Which of the following is the most probable cause?

Step 1: Check pod readiness

Step 2: Impact of pod readiness on routing

Final Answer:

Quick Check:

Want More Practice?