DEVELOPMENT TECHNOLOGIES

GitOps and Argo CD: Architecture, Use Cases, and Argo CD vs Flux

How GitOps uses Git as the source of truth and how Argo CD reconciles Kubernetes clusters against it, what teams use it for, and how it compares with Flux and Jenkins.
Argo logo

What Is GitOps and Argo CD?

GitOps is an operational model that uses Git repositories as the single source of truth for infrastructure and application deployments. Argo CD is a CNCF-graduated, declarative continuous delivery tool for Kubernetes built for this pull-based workflow. Teams comparing Argo CD vs Flux use the model to replace imperative deployment scripts with automated in-cluster reconciliation.

Weaveworks coined the term GitOps in 2017. The OpenGitOps project, a CNCF Sandbox project since 2021, defines four principles: desired state is declarative, it is stored immutably and versioned, software agents pull it automatically, and agents continuously reconcile the actual state toward it.

Argo was created in 2017 by Applatix, later acquired by Intuit, and the project now includes Argo Workflows, Argo Events, Argo CD, and Argo Rollouts. It graduated in the CNCF in December 2022 and is licensed under Apache 2.0.

Argo CD 3.x is the current major line. Official images are signed with cosign and ship SLSA Level 3 provenance, and teams should stay on supported patch versions.

How GitOps and Argo CD Work

Argo CD runs inside a Kubernetes cluster as a set of controllers that continuously compare the desired state in Git with the live cluster state and reconcile any drift, automatically or on demand. Instead of a CI server pushing changes, the cluster pulls updates from your repositories. Its three core services are listed in the table below.

For complex Helm or Kustomize sources, Argo CD includes the Source Hydrator, an optional feature that is off by default. It renders templates into plain Kubernetes manifests and pushes them back to a target Git branch, so reviewers see the exact YAML that will be applied. Its push credentials live in a separate namespace from the main control plane.

Authentication to the API server uses JSON Web Tokens, issued either for local accounts or by an OIDC identity provider such as the bundled Dex. By default, Argo CD polls Git every three minutes. Webhooks speed this up, but Argo CD treats webhook payloads as untrusted and only uses them to decide which repository to refresh.

Argo CD installs with cluster-admin rights by default, because it needs cluster-wide read access to observe live state. Operators can restrict its write permissions to specific namespaces and resources by narrowing its ClusterRoles. When installing from the standard manifests, use server-side apply to avoid CRD size limits.

ComponentPrimary responsibilityKey runtime behavior
API ServerServes the gRPC and REST API used by the web UI, CLI, and CI systems.Enforces RBAC, handles SSO with JWTs, and receives Git webhooks.
Repository ServerKeeps a local cache of the Git repositories that hold desired state.Renders manifests from Kustomize, Helm, Jsonnet, plain YAML, or plugins.
Application ControllerCompares live application state with the cached target state.Detects OutOfSync resources, applies changes, and runs sync waves and hooks.
Engineer's Take

Argo CD is most valuable when an organization runs several Kubernetes clusters and wants a shared, visual control plane where developers see deployment health and sync status without cluster credentials. Production problems rarely come from the reconciliation loop itself. A classic one is enabling self-heal on a Deployment scaled by a Horizontal Pod Autoscaler without ignoring the replica field, so Argo CD and the HPA fight over pod counts. Another is Helm: Argo CD renders charts with helm template, so lookup fails and non-idempotent hooks run on every sync. We keep secrets out of Git with the External Secrets Operator.

Diatom Enterprises favicon
Diatom engineering team
Argo CD at a Glance
Type

GitOps continuous delivery for Kubernetes

Model

Pull-based reconciliation from Git

License

Apache 2.0, CNCF graduated

Strengths

Multi-cluster control plane, web UI, built-in RBAC and SSO

Compared with
Need a reliable tech partner?
20+

Years in business

80+

Senior engineers

200+

Projects delivered

What GitOps and Argo CD Are Used For

Engineering organizations use GitOps and Argo CD to standardize multi-cluster deployments, keep audit trails for compliance, correct configuration drift, and run progressive delivery.

Fleet-Wide Multi-Cluster Delivery

Platform teams use ApplicationSets to generate and manage hundreds of applications across development, staging, and production clusters from one control plane. Only cluster administrators should be allowed to create or change ApplicationSets.

Developer Self-Service

Product teams sign in through SSO (OIDC, SAML, LDAP, GitHub, GitLab, or Microsoft) and get visual access to their own applications: live logs, sync status, and rollouts, while the platform team controls write permissions per project.

Drift Detection and Remediation

In regulated environments, manual kubectl edits are untracked risk. Argo CD compares live objects with Git commits, flags OutOfSync resources within minutes or immediately via webhook, and can revert unauthorized changes with self-heal.

Progressive Delivery and Ordered Rollouts

Database migrations and startup order use PreSync, Sync, and PostSync hooks. For canary and blue-green releases, teams add Argo Rollouts, which replaces the standard Deployment with a Rollout resource that shifts traffic gradually.

Argo CD vs Flux and Jenkins

Comparing Argo CD vs Flux, Argo CD offers a centralized, visual control plane while Flux is a lightweight toolkit of in-cluster controllers. Comparing Argo CD with Jenkins is really pull-based delivery versus push-based CI, and most teams use both.

Criteriontech logo argoArgo CDtech logoFluxtech logo jenkinsJenkins
Delivery modelPull-based declarative GitOps for Kubernetes.Pull-based declarative GitOps toolkit for Kubernetes.Push-based automation server, mainly for CI.
ArchitectureCentralized application that can manage many clusters from one control plane.Set of controllers (source, Kustomize, Helm, notifications, images) inside each cluster.Central controller and agents running pipeline scripts.
User interfaceRich web UI, CLI, and REST/gRPC API out of the box.CLI and YAML; no built-in web UI.Web dashboard focused on build logs and job history.
Access controlOwn RBAC engine, AppProject boundaries, and built-in SSO.Native Kubernetes RBAC through service-account impersonation.Plugin-based roles; needs cluster credentials to push deployments.
Drift handlingAutomated sync, self-heal, and pruning are opt-in; polls about every 3 minutes.Reconciliation on by default; drift correction on by default for Kustomizations.Does not watch live state, so manual drift goes unnoticed.
Progressive deliveryArgo Rollouts with a Rollout custom resource.Flagger, which wraps standard Deployments.Custom pipeline scripts or plugins.
Swipe the table to compare →

When to Choose Argo CD

Choose Argo CD if you want one control plane for multiple Kubernetes clusters and a web interface where developers can see deployment topologies, inspect diffs, and trigger syncs through corporate SSO without touching kubectl. It is also practical when you want opt-in control over automated syncing and pruning while moving existing workloads into GitOps.

When Argo CD Is Not the Right Fit

Flux is a better fit if your platform team prefers a lightweight CLI- and YAML-only setup on native Kubernetes RBAC with per-resource reconciliation intervals and no central UI to operate. Neither tool replaces continuous integration: building and testing code still needs a CI system such as Jenkins or GitHub Actions.

How We Approach Argo CD Projects

Production GitOps setups separate CI from CD, set clear repository boundaries, and configure RBAC, secrets, and diffing rules before workloads are onboarded, following the same principles as our Kubernetes and Docker deployments.

CI and CD Kept Separate

CI pipelines build and sign images and commit version bumps to a dedicated configuration repository, so CI never holds cluster credentials. For complex Helm or Kustomize overlays, the optional Source Hydrator can render plain YAML into Git for review.

Hardened Control Plane

We scope the controller and server ClusterRoles to the namespaces and resources each installation needs, restrict ApplicationSet changes to administrators, and keep Argo CD on patched releases as security fixes ship.

Diffing Rules and External Secrets

Before enabling self-heal, we add ignoreDifferences for HPA-managed replicas and diffing rules for normalized resource limits. Helm hooks are made idempotent, and credentials come from the External Secrets Operator instead of sidecar plugins.

Sound like the right partner?

Tell us about your project. We'll get back to you within 1 business day.

Frequently Asked Questions

Direct answers to common architectural and operational questions when adopting GitOps and Argo CD.

Can you use Jenkins and Argo CD together?

Yes, it is a standard pattern. Jenkins builds the code, runs tests, packages container images, and updates the image tag in the Git manifest repository. Argo CD detects the commit from inside the cluster and syncs the new manifests, which keeps cluster credentials out of Jenkins and adds continuous drift detection.

Is Flux harder to use than Argo CD because it has no web UI?

Not for infrastructure engineers comfortable with kubectl and YAML, since Flux is a modular set of controllers that use native Kubernetes RBAC. For application developers who want to inspect pod hierarchies, read logs, and trigger syncs through SSO, Argo CD has a much lower barrier because its web UI, CLI, and RBAC engine are built in.

How should you manage Kubernetes secrets with Argo CD?

Use an in-cluster operator such as the External Secrets Operator rather than storing secrets in Git or running sidecar plugins on the repo server. Git holds ExternalSecret resources, and the operator fetches the actual values from an external vault into the cluster. Community practice favors this over the Argo CD Vault Plugin, which struggles with Helm sub-charts.

Why does Argo CD show my application as OutOfSync when using an HPA or Helm?

Argo CD compares live state with the literal manifests from Git. A Horizontal Pod Autoscaler changes replica counts, and Kubernetes normalizes values such as 1000m to 1, so configure ignoreDifferences and diffing customizations for those fields. Because Argo CD renders Helm with helm template, charts using lookup or non-idempotent hooks also behave unexpectedly.

Can Argo CD and Flux run on the same Kubernetes cluster?

Yes, as long as they never manage the same resources. If both watch the same Deployment or namespace, Flux’s default drift correction and Argo CD’s sync loop will keep overwriting each other’s changes.

The People Behind

A team of skilled engineers, architects, and delivery managers, dedicated to making every engagement a success.

Let's discuss your project