Prev Next

Maven / GitOps Interview Questions

What is progressive delivery and how does it relate to GitOps — Argo Rollouts, Flagger?

Progressive delivery is the practice of releasing changes incrementally to a subset of users or traffic rather than all-at-once. Common strategies include canary releases (route 5% of traffic to the new version, ramp up if metrics look healthy), blue-green (maintain two identical environments and switch traffic between them), and A/B testing. The goal is to catch problems on a small blast radius before full rollout.

GitOps stores the desired final state. Progressive delivery tools manage the transition path to get there. A Git commit declaring a new image tag triggers the start; a separate tool decides how fast and safely to promote it.

Argo Rollouts: A Kubernetes controller that replaces standard Deployment resources with a Rollout CRD. The Rollout spec includes a strategy block defining canary steps or blue-green configuration. Argo CD syncs the Rollout manifest from Git; Argo Rollouts then manages the actual pod progression, traffic shifting (via Istio, NGINX, ALB), and Analysis template queries (Prometheus metrics, Datadog, Kayenta). If metrics fail, Rollouts automatically aborts and rolls back.

Flagger: Works alongside Flux CD. You keep deploying regular Kubernetes Deployments via Flux; Flagger watches them and creates primary/canary Deployment pairs automatically. It uses Prometheus or Datadog metrics to gate each traffic increment and integrates with Istio, App Mesh, Linkerd, and Nginx for traffic management. Canary objects are fully managed by Flagger — you only maintain the primary Deployment in Git.

Neither tool conflicts with GitOps — the rollout strategy CR itself is stored in Git and managed by the GitOps operator. Git records the intent; Argo Rollouts or Flagger executes the progression safely.

Which tool works natively alongside Flux CD to automate metrics-gated canary promotions?
What Kubernetes resource type does Argo Rollouts introduce to replace standard Deployments for canary/blue-green control?

Invest now in Acorns!!! 🚀 Join Acorns and get your $5 bonus!

Invest now in Acorns!!! 🚀
Join Acorns and get your $5 bonus!

Earn passively and while sleeping

Acorns is a micro-investing app that automatically invests your "spare change" from daily purchases into diversified, expert-built portfolios of ETFs. It is designed for beginners, allowing you to start investing with as little as $5. The service automates saving and investing. Disclosure: I may receive a referral bonus.

Invest now!!! Get Free equity stock (US, UK only)!

Use Robinhood app to invest in stocks. It is safe and secure. Use the Referral link to claim your free stock when you sign up!.

The Robinhood app makes it easy to trade stocks, crypto and more.


Webull! Receive free stock by signing up using the link: Webull signup.

More Related questions...

What is GitOps and what core principles does it define? How does GitOps differ from traditional CI/CD pipelines? What is the 'single source of truth' principle in GitOps? What are the two GitOps deployment models: push-based vs pull-based? What is a GitOps operator and what role does it play? What is declarative infrastructure and why does GitOps require it? How does GitOps improve security and auditability compared to script-based deployments? What Git branching strategies are commonly used with GitOps? What is drift detection and how does a GitOps operator handle drift? What is the difference between GitOps and Infrastructure as Code (IaC)? What is Argo CD and how does it implement GitOps? How does Argo CD's sync process work — desired state vs live state? What are Argo CD Applications and ApplicationSets? How do you structure a GitOps repository — app-of-apps, environment folders, overlays? What is Flux CD and how does it differ from Argo CD? How does Flux's source-controller and kustomize-controller work together? How do you manage secrets in a GitOps workflow — Sealed Secrets, SOPS, External Secrets Operator? How do you handle multiple environments (dev/staging/prod) in a GitOps repo? How does image automation work in Flux for continuous delivery? What are Argo CD sync policies — automated vs manual — and sync waves? How do you roll back a deployment using GitOps? How do you integrate GitOps with a CI pipeline — separation of concerns? What is progressive delivery and how does it relate to GitOps — Argo Rollouts, Flagger? How do you handle Helm charts in a GitOps workflow? How do you use Kustomize overlays in a GitOps repository? How do you implement multi-cluster GitOps at scale? How does Argo CD handle RBAC and multi-tenancy? What are the Argo CD app-of-apps and ApplicationSet patterns and when do you use each? How do you implement GitOps for infrastructure provisioning with Crossplane and Cluster API? How do you observe and alert on GitOps sync failures in production? How do you manage database schema migrations in a GitOps workflow? How do you implement policy enforcement in a GitOps pipeline — OPA/Gatekeeper, Kyverno? What are the limitations and anti-patterns of GitOps? How do you migrate an existing deployment pipeline to GitOps? How does GitOps fit into a platform engineering strategy?
Show more question and Answers...

Testing

Comments & Discussions