A tax-payment API needs a canary so only a small fraction of users hit v2. Using Deployments and a Service (no service mesh), what approach fits?
Select an answer to reveal the explanation.
Short Explanation
Canary is a tiny tasting table next to the main buffet—few v2 replicas, lots of stable, same Service ticket. Replica weighting does the split without a mesh. Trashing most stable Pods first is chaos, not canary.
Full Explanation
A primitive canary places a small replica count of the new version behind the same Service as the stable Deployment so only a fraction of endpoints are v2. RollingUpdate maxUnavailable settings alone do not define a lasting canary mix. Service meshes are optional; CKAD expects Deployments and Services for this pattern.