GitOps Principles and Argo CD Interview Questions (2027)

35 GitOps and Argo CD interview questions: the four OpenGitOps principles, pull vs push, drift, self-heal, repo layout, promotion, secrets and scale.

Sep 17, 2025 - 14:13
Nov 10, 2026 - 16:56
 0  87
GitOps Principles and Argo CD Interview Questions (2027)

GitOps with Argo CD interview questions check whether you understand the four OpenGitOps principles (declarative, versioned and immutable, pulled automatically, continuously reconciled) and can show how Argo CD puts each one into practice: Applications that point at Git, automated sync with self-heal, drift detection, and promotion between environments through commits instead of manual deploys.

This page focuses on GitOps as a method and on how Argo CD implements it. For Argo CD configuration and features in depth, read 70+ Argo CD interview questions. For troubleshooting and design cases, our keeper page is scenario-based Argo CD interview questions, and CLI work is in real-time Argo CD questions. Background reading: what GitOps is. Facts were checked against opengitops.dev and the Argo CD documentation in November 2026.

Key takeaways

  • GitOps is defined by four principles from the OpenGitOps project under the CNCF. Quote them accurately.
  • Argo CD is a pull-based agent: it runs in the cluster, reads Git and reconciles the cluster to match.
  • Running kubectl apply from a CI job is declarative but not GitOps, because nothing keeps reconciling afterwards.
  • Promotion between environments is a Git change (a commit or merge), and rollback is a revert.
  • Secrets need a pattern that keeps plaintext out of Git: Sealed Secrets, SOPS or an external secrets operator.
  • Senior candidates are asked about repository layout, multi-cluster ownership and how CI and CD hand off.

The four principles and how Argo CD maps to them

OpenGitOps principleWhat it meansHow Argo CD implements it
DeclarativeDesired state is expressed declarativelyKubernetes manifests, Helm charts, Kustomize overlays referenced by an Application
Versioned and immutableDesired state is stored with immutability, versioning and full historyGit repository (or OCI/Helm source) at a tracked revision; every sync records the commit
Pulled automaticallyAgents pull desired state from the sourceThe repo server and application controller poll or receive webhooks and fetch from Git
Continuously reconciledAgents observe actual state and apply desired stateApplication controller compares live and desired state; automated sync with self-heal corrects drift

Freshers: GitOps fundamentals

1. What is GitOps?

GitOps is a way of operating systems where the desired state is declared in a versioned store such as Git, and software agents continuously pull that state and reconcile the running system to match it. Changes happen through commits and reviews, not manual commands.

2. What are the four GitOps principles?

Declarative, versioned and immutable, pulled automatically, and continuously reconciled. They are published by the OpenGitOps project, a CNCF sandbox project.

3. What is Argo CD?

Argo CD is a declarative GitOps continuous delivery tool for Kubernetes. It is part of the Argo project, which has graduated in the CNCF.

4. What is the difference between push-based and pull-based deployment?

In push-based deployment a CI system holds cluster credentials and applies changes from outside. In pull-based deployment an agent inside the cluster fetches desired state from Git. Pull keeps cluster credentials inside the cluster and adds continuous reconciliation.

5. Why is Git a good source of truth?

It gives history, authorship, review through pull requests, signed commits if you need them, and an easy rollback by reverting. Every change to production becomes auditable.

6. What is drift?

A difference between what is declared in Git and what is running, usually from a manual kubectl edit or a controller changing a field. Argo CD reports this as OutOfSync.

7. What is an Argo CD Application?

A custom resource that tells Argo CD where the desired state lives (repo, revision, path) and where to deploy it (destination cluster and namespace), plus a sync policy.

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: orders-staging
  namespace: argocd
spec:
  project: default
  source:
    repoURL: https://git.example.com/platform/deploy.git
    targetRevision: main
    path: apps/orders/overlays/staging
  destination:
    server: https://kubernetes.default.svc
    namespace: orders
  syncPolicy:
    automated:
      prune: true
      selfHeal: true

8. What do Synced and Healthy mean?

Sync status says whether live state matches Git. Health status says whether the resources are working, for example whether a Deployment has its replicas available. An app can be Synced but Degraded.

9. How do you roll back in GitOps?

Revert the commit in Git and let Argo CD sync. Argo CD also has a history-based rollback, but it does not work while automated sync is enabled, because Git would win again.

10. Does GitOps replace CI?

No. CI still builds, tests and publishes images. GitOps handles delivery: CI updates the image tag in the deployment repository, and Argo CD rolls it out.

2 to 5 years: applying the principles

11. Why is running kubectl apply from a pipeline not GitOps?

It meets the declarative principle but not continuous reconciliation. After the job ends, nobody notices or fixes drift, and the CI system needs cluster credentials.

12. What do prune and selfHeal do?

prune deletes resources that were removed from Git. selfHeal re-syncs when the live state drifts even though Git did not change. Without self-heal, automated sync only acts on new commits.

13. Should application code and deployment manifests share a repository?

Argo CD's best-practices guide recommends separate repositories. It keeps deploy history clean, avoids CI loops when a tag update commits back, and lets you give different people access to each.

14. How would you structure a repository for dev, staging and production?

A common layout is a Kustomize base per app with an overlay per environment, or a Helm chart with a values file per environment. Each environment has its own Application pointing at its overlay path.

apps/
  orders/
    base/
    overlays/
      dev/
      staging/
      production/

15. How do you promote a release from staging to production?

Change the image tag or chart version in the production overlay through a pull request that someone approves. The merge is the deployment. Tools such as Argo CD Image Updater or a CI job can open that pull request automatically.

16. Why prefer environment folders over environment branches?

Branches per environment drift apart and need constant merging. Folders on one branch make differences visible in a single diff and keep promotion as a small, reviewable change.

17. How do you keep secrets out of Git?

Commit only encrypted or referenced secrets: Sealed Secrets (encrypted with a cluster key), SOPS-encrypted files decrypted by a plugin, or an external secrets operator that reads from Vault or a cloud secret manager. Argo CD's docs list these approaches and caution against injecting secrets during manifest generation.

18. How does Argo CD learn about new commits?

It polls repositories on an interval (three minutes by default, configurable) and can also receive Git webhooks to refresh immediately.

19. What are sync waves and hooks for?

Waves order resources within a sync using an annotation, for example creating a namespace and config before the Deployment. Hooks run jobs at points such as PreSync and PostSync, useful for database migrations.

20. How do you handle fields that other controllers change, such as replicas set by an HPA?

Remove the field from Git if another controller owns it, or configure ignoreDifferences for that field so Argo CD does not report drift or fight the controller.

21. What is an AppProject?

A grouping that limits which repositories, clusters, namespaces and resource kinds its Applications may use, plus project-level roles. It is the main tenancy boundary in Argo CD.

22. What does the app-of-apps pattern solve?

Bootstrapping. One parent Application points at a folder of Application manifests, so adding an app is a commit to that folder. ApplicationSets do the same job with generators.

Senior: GitOps at scale

23. When do you use ApplicationSets?

When the same app goes to many clusters or environments, or one Application per directory or per pull request is needed. Generators such as cluster, Git, list, matrix and pull request create the Applications from a template.

24. Hub-and-spoke or one Argo CD per cluster?

A central instance gives one view and less to run, but it is a single point of failure and needs network access and credentials for every cluster. One instance per cluster isolates failures and credentials but adds operating cost. Many teams use a central instance per region or per business unit.

25. How do you prove what is in production for an audit?

Git history plus pull request approvals show who changed desired state and who approved it. Argo CD's sync history records which revision was applied and when.

26. How do you stop people bypassing GitOps with kubectl?

Limit write access in the cluster through RBAC so humans get read-only access in production, enable self-heal so manual edits are reverted, and keep a documented break-glass procedure.

27. How does progressive delivery fit with GitOps?

Argo Rollouts adds canary and blue-green strategies as Kubernetes resources stored in Git. Argo CD syncs the Rollout, and Rollouts handles traffic shifting and analysis.

28. What changed for Argo CD 3.0 that a senior should know?

The upgrade notes list annotation-based resource tracking as the default, fine-grained RBAC for update and delete on application resources, and logs RBAC enforced by default. Read the upgrade guide before moving from 2.x.

29. How does GitOps apply beyond application deployments?

The same principles manage cluster add-ons, policies and even cloud infrastructure through Kubernetes-native controllers such as Crossplane. Our GitOps deployment best practices and GitOps tools for Kubernetes cover the options.

30. How do you compare Argo CD and Flux in an interview?

Both are CNCF graduated GitOps tools that follow the same principles. Argo CD offers a web UI, Applications and AppProjects for multi-tenancy. Flux is a set of controllers (source, kustomize, helm and others) driven by custom resources. Pick based on team needs, not popularity.

Scenario questions

31. An engineer hot-fixes production with kubectl and Argo CD reverts it. Who is wrong?

The process worked as designed. The fix should go through Git, possibly with an expedited review. If a true emergency requires a manual change, follow the break-glass procedure and commit the same change to Git straight away.

32. CI commits a new image tag, which triggers CI again in an endless loop. How do you fix it?

Move manifests to a separate repository, or have CI skip commits from its own bot user or with a skip marker. The separate repository is the cleaner fix.

33. Production must deploy only after a change has run in staging for a day. How?

Keep production on manual or gated promotion: an automated job opens the promotion pull request after the soak period and checks, and an approver merges it.

34. Pruning deleted a resource you needed. How do you prevent it?

Restore it in Git, then protect critical resources with the Prune=false sync option annotation, and review diffs before enabling prune on a new app.

35. You manage 40 clusters with the same add-ons. What design do you propose?

An ApplicationSet with a cluster generator, cluster labels to choose variants, values per cluster group in Git, and AppProjects to restrict what each team can deploy.

Practise it

Install Argo CD on a local cluster, create a deployment repository with base and overlays, and practise promotion by pull request, drift and self-heal, rollback by revert and a Sealed Secret. Kubernetes skills underpin all of this; our CKA training in Pune (Kharadi classroom or live online) covers the cluster side, and how GitOps keeps Git and cluster state in sync explains reconciliation in more depth.

FAQ

What are the four GitOps principles?

Declarative, versioned and immutable, pulled automatically, and continuously reconciled, as published by OpenGitOps.

Is Argo CD the only GitOps tool?

No. Flux is the other widely used CNCF graduated option, and some platforms build GitOps into their own products.

How is rollback done in GitOps?

By reverting the change in Git. Argo CD's own rollback works only when automated sync is off.

Should manifests live with application code?

Argo CD's best practices recommend a separate repository for manifests to keep history and access separate and avoid CI loops.

How do I handle secrets in a GitOps repository?

Store encrypted or referenced secrets only, using Sealed Secrets, SOPS or an external secrets operator. Never commit plaintext.

What does selfHeal do in Argo CD?

It makes Argo CD re-sync when live state drifts from Git, reverting manual changes even when no new commit arrived.

How often does Argo CD check Git?

Every three minutes by default, adjustable in configuration, and immediately when a webhook is configured.

References

What's Your Reaction?

Like Like 0
Dislike Dislike 0
Love Love 0
Funny Funny 0
Angry Angry 0
Sad Sad 0
Wow Wow 0
Mridul I am a passionate technology enthusiast with a strong focus on DevOps, Cloud Computing, and Cybersecurity. Through my blogs at DevOps Training Institute, I aim to simplify complex concepts and share practical insights for learners and professionals. My goal is to empower readers with knowledge, hands-on tips, and industry best practices to stay ahead in the ever-evolving world of DevOps.