Question 1

Is ArgoCD better than Flux in 2026?

Accepted Answer

Both are CNCF graduated GitOps tools. ArgoCD has the stronger UI, richer multi-tenancy (AppProjects, ApplicationSets), and is the dominant choice in India and the wider enterprise market. Flux is more modular (separate controllers for source, kustomize, helm, image automation), integrates more cleanly with FluxCD's image-update controller, and is favoured by teams that want a smaller server footprint. For most platform teams, ArgoCD's UI and ApplicationSet generators are decisive.

Question 2

How much does an ArgoCD / Kubernetes platform engineer earn in India?

Accepted Answer

₹9-28 LPA in 2026 for mid-to-senior platform/SRE roles where ArgoCD is part of the day-job. Companies hiring: Razorpay, Swiggy, Zomato, Flipkart, PhonePe, CRED, Postman, Cure.fit, plus the India offices of Intuit, Adobe, Red Hat and IBM. Specialised areas (multi-cluster fleets, RBI-regulated FinTech) push to the upper end.

Question 3

Do I need to know Helm and Kustomize before learning ArgoCD?

Accepted Answer

You need at least one. ArgoCD just renders manifests using existing tools — it doesn't replace them. Kustomize is built into kubectl and is the simpler starting point; Helm is more powerful for parameterised charts and external dependencies. In practice you'll meet both: Helm for off-the-shelf charts (cert-manager, prometheus), Kustomize for your own services.

Question 4

Can I use ArgoCD without a separate GitOps repo? Just point it at my application repo?

Accepted Answer

Technically yes, ArgoCD doesn't care which repo. But the strong production recommendation is a separate GitOps repo (or at least a separate folder/branch) because: (1) CI image-bumps shouldn't be mixed with application PRs, (2) the GitOps repo's permissions are usually narrower than the app repo's, (3) tag-and-bump from CI works cleanly without polluting your app's Git history. Most teams in India run a 'manifests' or 'gitops' repo per environment or per platform tenant.

Question 5

How does ArgoCD compare to Spinnaker or Jenkins X for CD?

Accepted Answer

Different generations. Spinnaker is heavyweight, predates Kubernetes-native CD, and is fading in 2026 except at companies with deep multi-cloud / multi-region pipeline needs. Jenkins X bet on opinionated GitOps but never reached the adoption of ArgoCD/Flux. For a Kubernetes-native CD in 2026, the choice is essentially ArgoCD vs Flux — Spinnaker is a strategic-fit question, not a default.

Question 6

What is GitOps and what are its four core principles?

Accepted Answer

GitOps is an operating model for cloud-native systems where Git is the single source of truth for both application and infrastructure state. The four principles (formalised by the OpenGitOps working group) are: (1) **Declarative** — the desired system state is described declaratively, not via imperative scripts. (2) **Versioned and immutable** — that state is stored in Git, so every change is auditable, reviewable, and revertible. (3) **Pulled automatically** — software agents (like ArgoCD) pull approved changes from Git into the cluster. (4) **Continuously reconciled** — agents continuously observe actual state and correct any drift back to the Git-declared state. ArgoCD is essentially the reference implementation of these four principles for Kubernetes.

Question 7

What is ArgoCD and how is it different from a traditional CI/CD pipeline?

Accepted Answer

ArgoCD is a Kubernetes-native, declarative GitOps continuous delivery tool. A traditional CI/CD pipeline (Jenkins, GitLab CI) pushes changes to the cluster — the pipeline holds kubectl credentials and runs `kubectl apply`. ArgoCD inverts that: the cluster pulls. You commit a manifest change to Git, ArgoCD's controller (running inside the cluster) notices the diff and applies it. Benefits: no long-lived cluster credentials in your CI system, drift is detected and corrected automatically, rollbacks are a `git revert`, and audit history matches your Git log. ArgoCD does CD only — your CI system still builds images and bumps tags in the GitOps repo.

Question 8

Describe ArgoCD's high-level architecture.

Accepted Answer

ArgoCD runs as a set of stateless pods inside a Kubernetes cluster (usually a dedicated 'argocd' namespace). The four core components are: (1) **API Server** — gRPC/REST endpoint that powers the UI, CLI, and webhooks; handles auth and RBAC. (2) **Repo Server** — clones Git repos and generates the final Kubernetes manifests (running `helm template`, `kustomize build`, or just reading YAML). It's stateless and horizontally scalable. (3) **Application Controller** — the reconciliation loop. It compares the desired state (manifests from repo-server) against the live state (from the K8s API) and applies diffs. Sharded by cluster for scale. (4) **Redis** — caches manifests and Application state so the repo-server doesn't re-template on every reconciliation. Optionally, an **ApplicationSet Controller** generates Application CRs from templates, and **Dex** handles SSO.

Question 9

What is the Application CRD and what does a minimal one look like?

Accepted Answer

The Application is ArgoCD's primary Custom Resource Definition. It tells ArgoCD: 'sync this Git path into this cluster + namespace, with these options'. The spec has three required sections — `source` (where the manifests live), `destination` (which cluster and namespace to deploy into), and `project` (which AppProject governs RBAC and allowed sources/destinations). It can be created via the UI, CLI (`argocd app create`), or directly as a YAML committed to Git — the last form is the GitOps-native way and enables app-of-apps.

Question 10

What does the ArgoCD UI show for each Application?

Accepted Answer

The UI renders each Application as a tree of Kubernetes resources rooted at the top-level objects in the manifest. For each node you see: **health status** (Healthy/Degraded/Progressing/Suspended/Missing), **sync status** (Synced/OutOfSync/Unknown), a live YAML diff between Git and cluster state, recent events, and pod logs. The tree-view is invaluable for debugging — you can click any resource to see exactly which container is failing or which field drifted. Production teams in India (Razorpay, Swiggy) often grant developers read-only UI access so they can self-serve debugging without cluster credentials.

Question 11

What's the difference between sync status (Synced/OutOfSync) and health status (Healthy/Degraded)?

Accepted Answer

These are two independent dimensions. **Sync status** answers 'does the cluster match Git?' OutOfSync means Git declared something the cluster doesn't have (or vice versa). **Health status** answers 'is the resource actually working?' A Deployment is Healthy when all replicas are ready; Degraded if not. You can be Synced + Degraded (Git matches cluster, but the pods are crashlooping) or OutOfSync + Healthy (someone made a kubectl change to the live state — Git hasn't caught up but the app still runs fine). The combination determines what action to take: OutOfSync triggers a sync; Degraded triggers an alert.

Question 12

What is an automated sync policy, and what do `prune` and `selfHeal` do?

Accepted Answer

An automated sync policy makes ArgoCD apply Git changes to the cluster without manual approval. Two flags fine-tune the behaviour: **prune: true** — delete cluster resources that have been removed from Git. Without it, ArgoCD never deletes anything, which gradually leaks orphaned resources. **selfHeal: true** — if someone makes a kubectl change to a managed resource, ArgoCD overwrites it back to the Git-declared state. Without it, ArgoCD only reacts to Git changes, not live-state drift. Most production setups enable both; non-production sometimes leaves `prune` off to avoid surprises.

Question 13

Which manifest formats does ArgoCD support out of the box?

Accepted Answer

Four native types, plus a plugin escape hatch: (1) **Plain YAML/JSON** — ArgoCD just `kubectl applies` the files in the path. (2) **Helm** — ArgoCD detects a `Chart.yaml` and runs `helm template` to generate manifests (it does NOT use `helm install` — Tiller is dead, and Helm releases are not tracked). (3) **Kustomize** — ArgoCD detects `kustomization.yaml` and runs `kustomize build`. (4) **Jsonnet** — supported via the repo-server. For anything else (cdk8s, Pulumi rendered to YAML, custom tooling), you write a **Config Management Plugin (CMP)** that ArgoCD invokes to produce manifests. In production, most teams in India use Helm for off-the-shelf charts and Kustomize for their own services.

Question 14

How do you point ArgoCD at a private Git repository?

Accepted Answer

Add a repository credential as a Kubernetes Secret in the argocd namespace with the label `argocd.argoproj.io/secret-type: repository`. Three credential types: SSH (private key), HTTPS (username + token), and GitHub App (installation ID + private key — preferred for GitHub because it has finer-grained permissions and no per-user token rotation). The UI and CLI also let you add repos, but for GitOps purity the secret itself should be managed declaratively (via Sealed Secrets or External Secrets — never plain Git).

Question 15

What's the difference between the ArgoCD UI, CLI (argocd), and kubectl?

Accepted Answer

Three ways to interact with ArgoCD: (1) **UI** — best for ad-hoc inspection, troubleshooting, viewing diffs and logs. (2) **argocd CLI** — talks to the API server over gRPC; needed for some operations like rotating SSO tokens and triggering syncs from scripts. (3) **kubectl** — talks directly to the K8s API to manipulate the Application/AppProject CRDs. This is the GitOps-native path: your repo contains Application YAMLs, and CI applies them with kubectl (or ArgoCD itself, in an app-of-apps). Rule of thumb: kubectl for declarative state, argocd CLI for imperative operations, UI for humans.

ArgoCD Interview Questions

What is GitOps and what are its four core principles?

What is ArgoCD and how is it different from a traditional CI/CD pipeline?

Describe ArgoCD's high-level architecture.

What is the Application CRD and what does a minimal one look like?

What does the ArgoCD UI show for each Application?

What's the difference between sync status (Synced/OutOfSync) and health status (Healthy/Degraded)?

What is an automated sync policy, and what do `prune` and `selfHeal` do?

Which manifest formats does ArgoCD support out of the box?

How do you point ArgoCD at a private Git repository?

What's the difference between the ArgoCD UI, CLI (argocd), and kubectl?

How do you trigger a manual sync of an Application?

What is ArgoCD's default polling interval, and how do you reduce it?

What is an AppProject and what problems does it solve?

Explain the app-of-apps pattern.

What is an ApplicationSet and when would you use it?

How do you order resources during a sync using waves and hooks?

How does ArgoCD determine resource health, and how do you customize it for a CRD?

How do you manage secrets safely with ArgoCD? You can't commit raw secrets to Git.

How does ArgoCD RBAC work, and how do you wire it to your IDP?

What are sync windows and how do they help in production?

How do you do blue/green and canary deployments with ArgoCD?

How do you scale ArgoCD when you have hundreds of clusters or thousands of Applications?

What's the difference between hard refresh, refresh, and sync?

How do you handle Helm chart values that vary per environment?

How do you tell ArgoCD to ignore certain fields that get mutated by admission controllers?

How would you design a multi-cluster GitOps platform for 50+ clusters across regions?

How do you implement a full progressive-delivery workflow: PR preview → canary → automated rollback?

ArgoCD shows 'Sync OK, Healthy' but your service is returning 500s in production. How do you debug?

How do you bootstrap ArgoCD itself with GitOps? The classic chicken-and-egg problem.

How do you handle compliance and audit requirements (SOC2, RBI) with ArgoCD?

Companies Hiring ArgoCD

Salary Insights

Frequently Asked Questions

Is ArgoCD better than Flux in 2026?

How much does an ArgoCD / Kubernetes platform engineer earn in India?

Do I need to know Helm and Kustomize before learning ArgoCD?

Can I use ArgoCD without a separate GitOps repo? Just point it at my application repo?

How does ArgoCD compare to Spinnaker or Jenkins X for CD?

Introduction