Argo CD v2.12.0stable Released Aug 05, 2024
Impact Score: 5/10

Argo CD v2.12.0 โ€” Release Notes & Engineering Impact

Source available โ€” automated, not human-reviewed

Component: argocd ยท Channel: stable. Automated analysis, not a compatibility certification. How this works.

Analysis updated: 2026-11-01.

Compatibility not verified โ€” check source notes
๐Ÿ“„ .MD
โšก Executive Summary (TL;DR)

Argo CD v2.12.0. Source highlight: kubectl create namespace argocd

Who Does This Impact? (Role-Based Analysis)

๐Ÿ’ป Software Engineers & Devs

Check the source notes against the package and APIs you use before upgrading.

๐Ÿ“Š Product & Engineering Leads

Use the documented changes to assess relevance to your product; release frequency alone is not a quality measure.

โš™๏ธ DevOps & Security

Verify the target version, runtime requirements and rollback procedure in the official documentation.

โœจ New Features & Capabilities (1)

  • 57e61b2d8a7c33bd5dd12f305a255d1185d782fb: feat: Add custom health check for cluster-api AWSManagedControlPlane (#19304) (#19360) (@gcp-cherry-pick-bot[bot])
๐Ÿ“„ View Raw Release Notes (Original Developer Log)
## Quick Start ### Non-HA: ```shell kubectl create namespace argocd kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/v2.12.0/manifests/install.yaml ``` ### HA: ```shell kubectl create namespace argocd kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/v2.12.0/manifests/ha/install.yaml ``` ## Release Signatures and Provenance All Argo CD container images are signed by cosign. A Provenance is generated for container images and CLI binaries which meet the SLSA Level 3 specifications. See the [documentation](https://argo-cd.readthedocs.io/en/stable/operator-manual/signed-release-assets) on how to verify. ## Upgrading If upgrading from a different minor version, be sure to read the [upgrading](https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/overview/) documentation. ## Known Issues ApplicationSets with git generators and a templated `spec.template.spec.project` field will fail to reconcile due to a [bug in the new git signature verification feature](https://github.com/argoproj/argo-cd/issues/19423). The problem is fixed in 2.12.2. ## Changelog ### Features * 57e61b2d8a7c33bd5dd12f305a255d1185d782fb: feat: Add custom health check for cluster-api AWSManagedControlPlane (#19304) (#19360) (@gcp-cherry-pick-bot[bot]) **Full Changelog**: https://github.com/argoproj/argo-cd/compare/v2.12.0-rc5...v2.12.0 <a href="https://argoproj.github.io/cd/"><img src="https://raw.githubusercontent.com/argoproj/argo-site/master/content/pages/cd/gitops-cd.png" width="25%" ></a>