Argo CD
GitOps continuous delivery controller and interface for deploying and reconciling applications in Kubernetes clusters.
7 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
Argo CD regexp2 dependency update
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.
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.
Primary source · Argo CD v3.5.8 backport · Argo CD v3.4.14 backport · Reviewed 2026-11-20
What lands where
Supplied by
Vendor or project
Install the official release Kubernetes manifests into a cluster; upstream releases provide standard and high-availability installation manifests.
Runs in
Documented customer environment
Customer-operated Kubernetes API service, repository server and application controller, using Git repositories as desired-state sources
- AWS: Customer cloud account
- AWS
Servers / containers
Operated by
Your team
Customer manages Kubernetes capacity, repository and cluster credentials, RBAC, identity integration, network exposure, application policies, backups and supported-version upgrades.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Self-managed Argo CD through AWS EKS Blueprints ↗ · Source checked 2026-11-12
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Install the official release Kubernetes manifests into a cluster; upstream releases provide standard and high-availability installation manifests. |
|---|---|
| Infrastructure | Servers / containers The official manifests deploy continuously running Argo CD services and controllers to a Kubernetes cluster. The upstream release page includes separate high-availability manifests. |
| Licensing model | Open Source / Open Core 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. |
| License | Apache License 2.0 for upstream Argo CD. Commercial management platforms and support offerings are separate. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
5 of 12 fields researched (42%) · 5 documented · 0 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
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.
Full Argo CD installation, not Core-only mode · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
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.
Upstream self-hosted deployment; not a provider support or production-readiness certification · Source ↗ · Deployment artifact ↗ (stable (moving branch; select a release tag)) · Reviewed 2026-11-14
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
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.
Upstream HA topology floor; component sizing requires measurement · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
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.
Upstream core licence; commercial features, support and hosting priced separately · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
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.
Upstream Argo CD application; chart and provider package versions may differ · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
Show all fields (7 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
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.
Community & 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.
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.
Compare within DevOps
- Azure DevOps ServerSource control, CI/CD, work tracking, testing and package management installed on Azure virtual machines you operate.
- Azure
- Bitbucket Data CenterCommercial self-managed Git collaboration and code-review platform for eligible existing Atlassian customers, with an announced Hybrid License transition.
- AWS
- Azure
- Google Cloud
- CircleCI ServerCommercial self-hosted CI/CD platform installed in a customer-operated Amazon EKS or Google GKE cluster.
- AWS
- Google Cloud
- CloudBees CI on Modern Cloud PlatformsEnterprise continuous-integration platform installed with Helm in a Kubernetes cluster you operate.
- AWS
- Azure
- Google Cloud
- GitHub Enterprise ServerCustomer-operated GitHub software-development platform deployed as a licensed virtual appliance.
- AWS
- Azure
- Google Cloud
- GitLab Self-ManagedSource control and CI/CD on infrastructure you operate.
- AWS
- Azure
- Google Cloud
- Oracle Cloud
- Alibaba Cloud
- HarborContainer and OCI artifact registry for managing software images within customer-operated infrastructure.
- Railway
- HashiCorp Consul EnterpriseCommercial service networking, discovery and service-mesh platform deployed into customer cloud infrastructure.
- AWS
- Azure
- Google Cloud
Showing 8 of 27 other listings in DevOps. These products address related workflows; read their category-fit notes before comparing scope. See all of DevOps →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Official installation and first application ↗argo-cd.readthedocs.io
- Argo CD component architecture ↗argo-cd.readthedocs.io
- Release manifests and maintenance ↗github.com
- Upstream Apache-2.0 license ↗github.com
- Argo CD v3.6.2 patch release ↗github.com
- Argo CD v3.5.8 backport ↗github.com
- Argo CD v3.4.14 backport ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Self-managed Argo CD through AWS EKS Blueprints ↗ · AWS
Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
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.
- Self-managed Argo CD through AWS EKS Blueprints ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked
- Community & maintenance evidenceChecked
- CNCF Argo maturity and governance context ↗www.cncf.io
- Recent upstream Argo CD releases ↗github.com
- Adobe enterprise Argo CD case study ↗www.cncf.io
- Argo CD adopter list ↗github.com