Prev Next

Maven / GitOps Interview Questions

How do you structure a GitOps repository — app-of-apps, environment folders, overlays?

The way you structure a GitOps config repo determines how easily you can promote changes between environments, onboard new applications, and keep per-environment differences small and reviewable. There is no single correct layout, but three patterns dominate.

1. Kustomize base + environment overlays (most common): Each application has a base/ directory with shared manifests and an overlays/ directory with one folder per environment. Each overlay folder contains a kustomization.yaml that references the base and adds environment-specific patches (image tag, replica count, config values).

gitops-config/
├── apps/
│   └── my-app/
│       ├── base/
│       │   ├── deployment.yaml
│       │   ├── service.yaml
│       │   └── kustomization.yaml
│       └── overlays/
│           ├── dev/
│           │   └── kustomization.yaml  # patches: image tag, replicas=1
│           ├── staging/
│           │   └── kustomization.yaml  # patches: image tag, replicas=2
│           └── prod/
│               └── kustomization.yaml  # patches: image tag, replicas=5
└── argocd/
    └── apps/
        ├── my-app-dev.yaml   # Application CR for dev overlay
        ├── my-app-staging.yaml
        └── my-app-prod.yaml

2. App-of-apps: A single root Argo CD Application points to the argocd/apps/ folder above. Argo CD syncs that folder, creating all the child Application CRs. This allows managing all Application registrations via Git without applying them manually.

3. Separate config repo per environment: Stricter separation — production config lives in a separate repo with tighter branch protection and access control. Suitable for regulated environments but adds overhead when updating shared base configs.

The app repo / config repo split (keeping source code and deployment manifests in separate repositories) is an orthogonal best practice that improves the separation of concerns between CI (build) and CD (deploy).

In a Kustomize-based GitOps repo, where do environment-specific patches such as replica counts and image tags live?
What does the app-of-apps pattern achieve in an Argo CD GitOps setup?

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