Application promotion in GitOps
summary
GitOps works fine for one repo and one cluster but single-cluster GitOps breaks at scale when promoting apps across dev/test/prod because teams must move container tags, Helm chart versions, overlays, values and infra files by hand. A Flux-based setup is used and a promotion automation is built that either runs a synchronous pipeline (deploy dev → test → prod) or triggers asynchronous image-driven promotion by updating Git; demos show the automation reduces missed manifest moves, and choice hinges on team culture and maturity.
AI-written summary · about
related talks
39mSoftware Rollout at Scale: Using GitOps to Scale Kubernetes Rollouts
26mGitOps Lifecycle Management
35mPanel: GitOps User Stories
22mPush to Prod: GitOps Workflows on k8s with FluxCD
37mDevelopers Love GitOps
32mGitOps and Multi-Environments: A Story of Promotion
47mDevOps:Config Mgmt for Kubernetes workloads with GitOps and Helm
45mFrom DevOps to GitOps: Supercharging Your Kubernetes Workload Deployments