Kubernetes - Advanced Deployment Patterns
An Ingress resource has both 'canary: "true"' and 'canary-weight: "50"' annotations, but traffic is not splitting as expected. What is a common misconfiguration causing this?
An Ingress resource has both 'canary: "true"' and 'canary-weight: "50"' annotations, but traffic is not splitting as expected. What is a common misconfiguration causing this?
medium📝 Troubleshoot Q7 of 15
Step-by-Step Solution
Solution:
Step 1: Verify canary service selector presence
Canary traffic routing requires correct selector labels on canary service.Step 2: Understand impact of missing selector
Without selector, Ingress cannot route traffic to canary, so split fails.Final Answer:
The canary service selector is missing or incorrect -> Option CQuick Check:
Missing canary selector = no traffic split [OK]
Quick Trick: Always set correct selector labels for canary service [OK]
Common Mistakes:
- Confusing TLS config with traffic splitting
- Assuming primary endpoints affect canary split
- Believing canary-weight must be below 10
Master "Advanced Deployment Patterns" in Kubernetes
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kubernetes Quizzes