Argo CD v0.9.0stable Released Sep 24, 2018
Impact Score: 5/10

Argo CD v0.9.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 v0.9.0. Source highlight: Notes about upgrading from v0.8

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.

๐Ÿ”ง Bug Fixes & Patches (3)

  • Fix issue where changes were not pulled when tracking a branch (issue #567)
  • Fix controller hot loop when app source contains bad manifests (issue #568)
  • [UI] Fix issue where projects filter does not work when application got changed
๐Ÿ“„ View Raw Release Notes (Original Developer Log)
### Notes about upgrading from v0.8 * The `server.crt` and `server.key` fields of `argocd-secret` had been renamed to `tls.crt` and `tls.key` for better integration with cert manager(issue #617). Existing `argocd-secret` should be updated accordingly to preserve existing TLS certificate. * Cluster wide resources should be allowed in default project (due to issue #330): ``` argocd project allow-cluster-resource default '*' '*' ``` ### Changes since v0.8: + Auto-sync option in application CRD instance (issue #79) + Support raw jsonnet as an application source (issue #540) + Reorder K8s resources to correct creation order (issue #102) + Redact K8s secrets from API server payloads (issue #470) + Support --in-cluster authentication without providing a kubeconfig (issue #527) + Special handling of CustomResourceDefinitions (issue #613) + ArgoCD should download helm chart dependencies (issue #582) + Export ArgoCD stats as prometheus style metrics (issue #513) + Support restricting TLS version (issue #609) + Use 'kubectl auth reconcile' before 'kubectl apply' (issue #523) + Projects need controls on cluster-scoped resources (issue #330) + Support IAM Authentication for managing external K8s clusters (issue #482) + Compatibility with cert manager (issue #617) * Enable TLS for repo server (issue #553) * Split out dex into it's own deployment (instead of sidecar) (issue #555) + [UI] Support selection of helm values files in App creation wizard (issue #499) + [UI] Support specifying source revision in App creation wizard allow (issue #503) + [UI] Improve resource diff rendering (issue #457) + [UI] Indicate number of ready containers in pod (issue #539) + [UI] Indicate when app is overriding parameters (issue #503) + [UI] Provide a YAML view of resources (issue #396) + [UI] Project Role/Token management from UI (issue #548) + [UI] App creation wizard should allow specifying source revision (issue #562) + [UI] Ability to modify application from UI (issue #615) + [UI] indicate when operation is in progress or has failed (issue #566) - Fix issue where changes were not pulled when tracking a branch (issue #567) - Lazy enforcement of unknown cluster/namespace restricted resources (issue #599) - Fix controller hot loop when app source contains bad manifests (issue #568) - [UI] Fix issue where projects filter does not work when application got changed - [UI] Creating apps from directories is not obvious (issue #565) - Helm hooks are being deployed as resources (issue #605) - Disagreement in three way diff calculation (issue #597) - SIGSEGV in kube.GetResourcesWithLabel (issue #587) - ArgoCD fails to deploy resources list (issue #584) - Branch tracking not working properly (issue #567) - Controller hot loop when application source has bad manifests (issue #568)