Argo CD v3.6.0 released on 03-11-2026
Argo CD v3.6.0 is out now. It provides an easy quick‑start install (non‑HA and HA manifests) and a stronger supply‑chain story: container images are signed with cosign and images/CLI binaries have SLSA Level 3 provenance where applicable, which will interest operators and security‑minded teams.
Check the GitHub release, the official docs for verifying signatures and provenance, and the upgrade guide for practical details before you move between minor versions.
What’s in this release
- Quick start manifests for non‑HA and HA installs (kubectl apply examples) plus signed release assets: all container images signed with cosign and provenance generated for images and binaries that meet SLSA Level 3.
- ApplicationSet and progressive sync improvements: new progressive sync metrics, annotations on generated apps to force reconciliation ordering, condition reasons/messages for progressive sync scenarios, metrics for AppSet‑triggered refreshes, exposed workqueue rate limiter flags, fixes to stop tight reconcile loops and avoid reserved annotation leaks, and new/updated generators with webhook support (OCI generator improvements, Bitbucket Server manifest‑generate‑paths, Harbor and DockerHub webhooks).
- Large expansion of built‑in health checks and resource coverage (Kyverno, TLSRoute, CloudNativePG DB/Backup, Prometheus Operator Alertmanager/ThanosRuler, cert‑manager types including CertificateRequest and ACME Order/Challenge, Tekton PipelineRun/TaskRun, Velero Backup/Restore/Schedule, KServe LLMInferenceService, Pulumi Stack and more), plus UI, performance and CLI/server updates (virtual scrolling and lazy loading for apps list, resources explorer, cached manifest serialization/compression, partial JSON unmarshalling, and CLI/server fixes for proxy, client cert persistence and admin export behaviour).
Upgrade notes
- If you are upgrading between minor versions, read the official upgrading documentation for guidance: https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/overview/
- There is a deprecation warning introduced for the –signature-keys option (see release notes); use the SOURCE-INTEGRITY replacement where applicable and consult the changelog for specifics.
Try the release and let the project know how it behaves in your environment — share any feedback or issues you encounter so the maintainers can follow up.
