A developer tries to implement a web API canary by creating a Job that runs the v2 image once. Why is that the wrong workload?
Select an answer to reveal the explanation.
Short Explanation
A Job is a one-and-done chore—great for batch, terrible as a standing canary waiter. Web canaries need long-running Deployment replicas sitting behind a Service. Don’t cast a Job in that role.
Full Explanation
Deployment strategies such as canary apply to durable, replicated application Pods selected by a Service. Jobs run finite tasks to completion and are not the primitive for serving a fraction of ongoing HTTP traffic. completions and restartPolicy do not implement Service traffic splits.