Vanilla Argo CD lacks a formal release model, making environment promotion error-prone and hard to audit. By connecting Argo CD to Octopus Deploy via an outbound gateway, teams can create immutable release snapshots that move through environments (Development → Production) under governance. The setup uses Kustomize overlays annotated to map Argo CD Applications to Octopus projects and environments. Octopus handles image tag updates, commits to Git, and triggers Argo CD syncs. A Manual Intervention step scoped to Production acts as an approval gate. The result is a full audit trail showing who promoted what and when, with a single dashboard view across all environments and clusters.
Table of contents
Why “promotion” is hard in vanilla Argo CDPrerequisitesThe architecture setupBuilding the Octopus project with a Dev to Production lifecycleCreate a release and deploy to DevelopmentPromote the same release to ProductionThe governance you got for freeGoing from overlay edits to audited releasesTags:2.1K Impressions