Prev Next

Maven / GitOps Interview Questions

What is declarative infrastructure and why does GitOps require it?

Declarative infrastructure means specifying the desired end state of a system rather than the sequence of commands needed to reach it. A Kubernetes Deployment manifest is declarative — it says "I want 3 replicas of this container image running with these environment variables." The Kubernetes control plane figures out the steps (schedule pods, pull images, attach volumes) to achieve that state. By contrast, a shell script that runs kubectl scale, kubectl set image, and kubectl rollout in sequence is imperative — the outcome depends on the starting state.

GitOps requires declarative infrastructure for a specific technical reason: the reconciliation loop works by comparing two representations of system state — the declared state in Git and the live state reported by the Kubernetes API. Both sides of the comparison must be in the same format for the diff to be meaningful.

  • Imperative commands like kubectl run describe a one-time action, not a persistent state. You cannot store "kubectl scale to 5" in Git and compare it to the current replica count; you can store spec.replicas: 5 and compare it.
  • Idempotency follows naturally from declarative configs — applying the same manifest twice produces the same result, which means the operator can safely reconcile as often as it likes.
  • Drift detection only works if the desired state can be parsed, normalised, and diffed against the live API server response. Declarative YAML makes this straightforward.

Common declarative formats used with GitOps: Kubernetes YAML manifests, Helm values.yaml files (rendered to manifests by the operator), Kustomize overlay patches, and Crossplane Composite Resource Claims.

What is the defining characteristic that makes a Kubernetes manifest 'declarative'?
Why can imperative kubectl commands not serve as the desired state in a GitOps reconciliation loop?

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