A city website cutover must keep the old version live until operators point traffic at the new version. How should blue/green be designed with Kubernetes primitives?
Select an answer to reveal the explanation.
Short Explanation
Blue/green is two stages side by side—old show still playing while the new set finishes dress rehearsal. Keep both Deployments up, then flip the Service selector to green. One Deployment yo-yo isn’t blue/green.
Full Explanation
Blue/green with core Kubernetes primitives typically uses two Deployments that differ by version labels, with a Service whose selector is updated to send traffic to the validated green Pods. Scaling a single Deployment through recreate-like behavior or relying on Jobs to mutate proxy rules is not the standard pattern.