Prev Next

Maven / GitOps Interview Questions

How does GitOps fit into a platform engineering strategy?

Platform engineering is the discipline of building Internal Developer Platforms (IDPs) that give application teams self-service access to infrastructure and deployment capabilities through well-defined abstractions. GitOps is the delivery mechanism underneath the platform — it ensures that everything the IDP provisions or configures is continuously reconciled to its declared state, without platform engineers manually applying changes.

Key integration points:

  • Golden path templates: Platform teams define standardised GitOps repository templates (via Backstage Software Templates, Cookiecutter, or custom scaffolding) that new services bootstrap from. The template pre-wires the CI pipeline, the Kustomize overlay structure, the Argo CD Application CR, and the required RBAC/AppProject — so a developer starts with a working GitOps setup from day one.
  • Self-service via PR: Rather than filing a Jira ticket to get a new namespace or a database, a developer fills in a form in Backstage, which opens a PR to the config repo. An Argo CD ApplicationSet or Crossplane Composition is triggered by that PR merge, provisioning the requested resources automatically. The platform team approves the template once; individual team requests need no manual platform-team intervention.
  • Crossplane + GitOps for infrastructure: Developers request cloud resources (databases, queues, storage) by committing Crossplane Claim CRs to the config repo. The GitOps operator applies them; Crossplane provisions the cloud resources. Connection secrets are injected via External Secrets Operator. The developer only interacts with Git and a Kubernetes-style API — never with cloud consoles.
  • Policy-as-code as a platform service: Platform teams manage Kyverno ClusterPolicies and OPA/Gatekeeper ConstraintTemplates in Git. Every team's workload automatically inherits these guardrails because the GitOps operator applies the policies to all clusters. Compliance is built in, not bolted on.
  • Observability configuration as GitOps: Prometheus, Grafana, Loki, and alerting rules are themselves deployed and managed via GitOps, ensuring every cluster has a consistent observability stack that can be audited and version-controlled like any other workload.

The net result: developers interact with Git and a friendly UI, not Kubernetes directly. Platform teams own the templates and policies, not the individual deployments. GitOps closes the loop between expressed intent and running reality for every layer of the platform.

In a GitOps-backed Internal Developer Platform, what does a developer submit to request a new service deployment or cloud resource?
Which tool is commonly used to scaffold Golden Path GitOps repository templates for new services in a platform engineering 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