How do you do progressive delivery (canary, blue-green) in a GitOps setup?
What they are really testing: Whether you know GitOps does not natively do traffic-shifted canaries and that you add a progressive-delivery controller (Argo Rollouts, Flagger) with automated analysis and rollback.
A real interview question
How do you do progressive delivery (canary, blue-green) in a GitOps setup?
What most people say
drag me
“GitOps does canary deployments automatically when you push a change.”
It does not. A GitOps controller does a normal rollout. Traffic-shifted, metric-analyzed canaries need a dedicated controller like Argo Rollouts or Flagger layered on top, with automated analysis and rollback.
The follow-ups they ask next
What does the analysis step in a canary actually do?
At each traffic increment it queries metrics (error rate, latency, custom SLOs) and compares the canary against the baseline; if the metrics regress, it halts and rolls back automatically instead of continuing the rollout.
Does adding Argo Rollouts mean you are no longer doing GitOps?
No, the Rollout and its analysis are declared in git and reconciled by the GitOps controller. Progressive delivery layers on top of GitOps; it does not replace the git-as-source-of-truth model.
What the interviewer is listening for
- Knows plain GitOps is a standard rollout
- Adds Argo Rollouts/Flagger for canary/blue-green
- Knows automated metric analysis + auto-rollback, still declared in git
What sinks the answer
- Thinks GitOps canaries automatically
- No notion of a rollout controller
- Unaware of analysis/auto-rollback
If you genuinely do not know
Say this instead of freezing. Reasoning out loud from what you do know beats silence every single time, and a good interviewer is listening for exactly that.
“Plain GitOps does [a standard rollout, not a metric-driven canary]. Add [Argo Rollouts or Flagger for canary/blue-green: shift traffic in steps]. At each step they [run analysis on metrics (error rate/latency) and auto-rollback if it regresses]. It stays GitOps because [the rollout strategy is declared in git and reconciled by the controller]; progressive delivery [layers on top].”
Keep going with gitops
Foundation
What is GitOps, and what problem does it solve?
Foundation
What is the difference between push-based and pull-based deployment, and why does GitOps prefer pull?
Foundation
What are the core principles of GitOps?
Junior
What are Argo CD and Flux, and how do they differ?
Junior
How does drift detection and self-healing work in GitOps?
Junior
How do you structure repositories for GitOps? Should app code and deployment config live together?
Knowing the answer is not the same as recalling it under pressure
Sign in to send the questions you fumble to spaced recall, so they come back right before you would forget them, and learn the concepts behind them with hands-on labs.
Start free