Product wants header-based canary routing for internal testers. At CKAD depth with basic Service weighting only, what should the candidate conclude?
Select an answer to reveal the explanation.
Short Explanation
Plain Services are coin-flip load balancers across endpoints—they don’t read HTTP headers. Replica-weighted canary is the CKAD bread-and-butter; fancy header splits need Ingress (or similar), not mesh trivia for the exam core.
Full Explanation
ClusterIP Services distribute traffic among Ready endpoints without HTTP header matching. Replica-weighted canaries using Deployments and Services stay in core CKAD scope. Header- or path-based splits require Ingress or controller capabilities; sessionAffinity and port-forward are not substitutes for production header canaries.