
# Argo CD

GitOps continuous delivery controller and interface for deploying and reconciling applications in Kubernetes clusters.

Canonical page: https://launchinyourcloud.com/directory/argo-cd/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## Argo CD

GitOps continuous delivery controller and interface for deploying and reconciling applications in Kubernetes clusters.

- Listing: https://launchinyourcloud.com/directory/argo-cd/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream Argo CD. Commercial management platforms and support offerings are separate.
- Licensing model: open-source
- Installation: Install the official release Kubernetes manifests into a cluster; upstream releases provide standard and high-availability installation manifests.
- Architecture: Customer-operated Kubernetes API service, repository server and application controller, using Git repositories as desired-state sources
- Operations: Customer manages Kubernetes capacity, repository and cluster credentials, RBAC, identity integration, network exposure, application policies, backups and supported-version upgrades.
- Product website: https://argo-cd.readthedocs.io/
- Source review: 2026-11-20; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Argo CD runs in Kubernetes and needs credentials for the clusters and repositories it manages. Git hosting, identity providers, image registries and target applications may reside outside the account. The listing covers upstream Argo CD rather than commercial management services or the separate Argo Workflows product. Argo CD patches v3.6.2, v3.5.8, and v3.4.14 update the bundled regexp2 library for CVE-2026-77299. Apply the patch for the deployed minor line and check the application version bundled in any Helm chart or provider package.

The reviewed upstream project uses Apache License 2.0. This classification covers the upstream software; third-party components and separately operated services retain their own terms.

The official manifests deploy continuously running Argo CD services and controllers to a Kubernetes cluster. The upstream release page includes separate high-availability manifests.


### Category fit

- devops: Declarative continuous delivery for Kubernetes: compares deployed application state with Git-defined desired state and supports synchronization, health visibility and rollback operations.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/awslabs/cdk-eks-blueprints/blob/main/docs/addons/argo-cd.md (checked 2026-11-12). 


### Cloud deployment evidence

- Self-managed Argo CD through AWS EKS Blueprints (aws): https://github.com/awslabs/cdk-eks-blueprints/blob/main/docs/addons/argo-cd.md
  AWS EKS Blueprints installs the Argo CD Helm chart and its components in the customer EKS cluster. This is distinct from the managed Amazon EKS capability. Configure administrator credentials, repository secrets, upgrades and application cleanup before cluster deletion.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Argo is a CNCF Graduated project. The upstream Argo CD release page records version 3.6.1 on 4 November 2026 and supported-series maintenance releases. A 2026 CNCF Adobe case study specifically describes operationalizing Argo CD within its enterprise delivery platform; the Argo CD repository also maintains named adopters.

Reviewed 2026-11-10.

- CNCF Argo maturity and governance context: https://www.cncf.io/projects/argo/

- Recent upstream Argo CD releases: https://github.com/argoproj/argo-cd/releases

- Adobe enterprise Argo CD case study: https://www.cncf.io/case-studies/adobe/

- Argo CD adopter list: https://github.com/argoproj/argo-cd/blob/master/USERS.md

### Sources

- Official installation and first application: https://argo-cd.readthedocs.io/en/stable/getting_started/

- Argo CD component architecture: https://argo-cd.readthedocs.io/en/stable/operator-manual/architecture/

- Release manifests and maintenance: https://github.com/argoproj/argo-cd/releases

- Upstream Apache-2.0 license: https://github.com/argoproj/argo-cd/blob/master/LICENSE

- Argo CD v3.6.2 patch release: https://github.com/argoproj/argo-cd/releases/tag/v3.6.2

- Argo CD v3.5.8 backport: https://github.com/argoproj/argo-cd/releases/tag/v3.5.8

- Argo CD v3.4.14 backport: https://github.com/argoproj/argo-cd/releases/tag/v3.4.14

### Licensing sources

- https://github.com/argoproj/argo-cd/blob/master/LICENSE

### Infrastructure sources

- https://argo-cd.readthedocs.io/en/stable/getting_started/

- https://github.com/argoproj/argo-cd/releases


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Argo CD documents bundled Dex connectors or an existing OIDC provider for UI/CLI sign-in. Identity-provider claims and Argo CD RBAC require explicit configuration; Core-only installs omit the UI/SSO components. Scope: Full Argo CD installation, not Core-only mode. Source: https://argo-cd.readthedocs.io/en/stable/operator-manual/user-management/ (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official getting-started guide installs upstream Kubernetes manifests. The stable branch reference moves; pin a release for controlled deployment and configure certificates, identity and RBAC. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://argo-cd.readthedocs.io/en/stable/getting_started/ (reviewed 2026-11-14). Deployment artifact: https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml. Artifact reference: stable (moving branch; select a release tag).

- Minimum footprint / sizing: Documented. The official HA manifests require at least three distinct Kubernetes nodes because of anti-affinity and deploy additional components including HA Redis. CPU/memory depend on managed applications, repositories, rendering and reconciliation concurrency; this topology floor is not a fixed workload capacity guarantee. Scope: Upstream HA topology floor; component sizing requires measurement. Source: https://argo-cd.readthedocs.io/en/stable/operator-manual/high_availability/ (reviewed 2026-11-20).

- License pricing: Documented. The reviewed upstream core is Apache-2.0 licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/argoproj/argo-cd/master/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Argo CD v3.6.2 updates regexp2 for CVE-2026-77299. The v3.5.8 and v3.4.14 release notes document the corresponding backports. Scope: Upstream Argo CD application; chart and provider package versions may differ. Source: https://github.com/argoproj/argo-cd/releases/tag/v3.6.2 (reviewed 2026-11-20).




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- Argo CD regexp2 dependency update (security-advisory): Argo CD updated regexp2 to address CVE-2026-77299. Scope: Upstream Argo CD releases v3.6.2, v3.5.8, and v3.4.14 contain the documented fix. Conditions: The cited release notes establish a regexp2 dependency fix, not an Argo-specific exploit path or complete affected-version range. Helm charts and provider packages have separate versions; inspect their underlying Argo CD application version. Action: Apply the patched release for the deployed minor branch and follow the upstream upgrade guidance for cross-minor changes. Source: https://github.com/argoproj/argo-cd/releases/tag/v3.6.2; reviewed 2026-11-20. Supporting source: Argo CD v3.5.8 backport — https://github.com/argoproj/argo-cd/releases/tag/v3.5.8. Supporting source: Argo CD v3.4.14 backport — https://github.com/argoproj/argo-cd/releases/tag/v3.4.14.



