> Markdown version of [/videos/1603-next-gen-ci-cd-with-gitops-and-progressive-delivery?t=514](https://www.wearedevelopers.com/videos/1603-next-gen-ci-cd-with-gitops-and-progressive-delivery?t=514). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Next-gen CI/CD with Gitops and Progressive Delivery

Deploying to production doesn't have to mean releasing to everyone. Discover how pairing GitOps with Argo Rollouts automates progressive delivery and eliminates deployment anxiety.

- **Speakers:** [Kevin Dubois](https://www.wearedevelopers.com/@kevin-dubois)
- **Event:** World Congress 2025
- **Published:** August 20, 2025
- **Duration:** 28:07
- **URL:** https://www.wearedevelopers.com/videos/1603-next-gen-ci-cd-with-gitops-and-progressive-delivery

## Summary

The evolution of software deployment has moved from the precarious days of manual scripts and big bang releases to sophisticated, automated delivery pipelines. Despite continuous integration operations maturing rapidly, the transition to production often remains a rigid, high-risk process. To minimize downtime and deployment anxiety, software teams are transitioning toward GitOps methodologies and progressive delivery paradigms to safely manage complex distributed systems.

GitOps establishes Git as the single source of truth for both application code and infrastructure configuration. By shifting operations toward pull requests and automated syncs, teams maintain tight audit trails and cluster drift detection. Central to this workflow is Argo CD, a declarative continuous delivery tool for Kubernetes that continuously reconciles the desired state in Git with the live cluster environment. However, since GitOps natively defaults to all-or-nothing cluster convergence, organizations increasingly layer progressive delivery practices on top of it. Because "deploying to production does not necessarily mean the same as releasing to production," engineers can leverage dark launches and traffic mirroring to validate code against live user behavior rather than relying exclusively on brittle pre-production end-to-end mocks.

Progressive delivery introduces intelligent traffic-shaping strategies such as blue-green environments and canary releases natively or through a service mesh like Istio. Taking this a step further, Argo Rollouts automates the pacing and evaluation of these incremental updates. Rather than manually supervising virtual service traffic shifts, engineering teams construct analysis templates that continuously evaluate success via Prometheus container metrics. If an application failure threshold—like an unexpected spike in HTTP 500 errors—is temporarily exceeded during a canary proportion step, Argo Rollouts automatically aborts the update and routes traffic back to the stable baseline, creating a hands-off, risk-averse deployment lifecycle.

**Keywords:** progressive delivery techniques, gitops deployment architecture, argo CD kubernetes, argo rollouts automation, automated deployment rollbacks, prometheus metrics analysis, canary release routing, cluster state drift detection, istio service mesh, dark launching applications, testing in production, blue-green deployment strategies, continuous delivery pipelines, traffic mirroring patterns, declarative infrastructure management

## Chapters

1. **Evolution from manual deployments to continuous integration** (00:00) — How application delivery practices evolved from manual file transfers to automated build pipelines.
1. **Continuous delivery versus continuous deployment models** (01:38) — Why moving to distributed microservices requires automated production delivery models beyond basic integration.
1. **Treating Git as the source of truth for operations** (04:04) — How GitOps methodologies use version control to enforce desired state and detect environment drift.
1. **Managing declarative configuration changes with Argo CD** (06:42) — How automatic synchronization tools can present operational risks via default big-bang release models.
1. **Reducing release risk with progressive delivery techniques** (08:34) — How gradually rolling out software builds deployment confidence and limits potential downtime impact.
1. **Comparing blue-green, canary, and dark launch deployments** (10:44) — How different distribution methods manage production traffic to securely validate incoming version upgrades.
1. **Routing traffic natively with Kubernetes and service meshes** (13:11) — How using tools like Istio facilitates precise load balancing logic for progressive version changes.
1. **Automating progressive rollouts and metric success analysis** (16:17) — How declarative strategies let systems automatically pause deployments and evaluate telemetry before continuing rollouts.
1. **Demonstrating automated canary releases and infrastructure rollbacks** (19:16) — Testing a progressive deployment strategy that successfully intercepts server errors and restores stable prior states.
1. **Handling stateful application schemas during progressive deployment** (26:19) — Why using progressive delivery alongside relational databases may require specialized external state capture systems.

## Related Moments

- [Introduction to GitOps and the Argo CD presentation](https://www.wearedevelopers.com/videos/108-get-ready-for-operations-by-pull-requests) (from "Get ready for operations by pull requests")
- [Automating canary deployments with Argo Rollouts](https://www.wearedevelopers.com/videos/100233-when-human-meets-canary) (from "When human meets canary")
- [Evolution of software delivery and the devops pipeline](https://www.wearedevelopers.com/videos/853-navigating-the-ai-wave-in-devops) (from "Navigating the AI Wave in DevOps")
- [Defining progressive delivery and core deployment safety](https://www.wearedevelopers.com/videos/949-progressive-delivery-in-kubernetes) (from "Progressive Delivery in Kubernetes")
- [Demonstrating automated deployment sequences via Git repositories](https://www.wearedevelopers.com/videos/372-a-practitioners-guide-to-gitops-introduction-principles-and-implementation) (from "A Practitioners Guide to GitOps - Introduction, Principles and Implementation")
- [Differentiating continuous delivery against continuous deployment models](https://www.wearedevelopers.com/videos/544-plan-ci-cd-on-the-enterprise-level) (from "Plan CI/CD on the Enterprise level!")

## Related Articles

- [Now is the time for industrialized software development](https://www.wearedevelopers.com/magazine/601-now-is-the-time-for-industrialized-software-development)
- [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift)
- [Exploring AI: Opportunities and Risks for Developers](https://www.wearedevelopers.com/magazine/522-exploring-ai-opportunities-and-risks-for-developers)
- [What is Software Engineering in the Age of AI?](https://www.wearedevelopers.com/magazine/640-what-is-software-engineering-in-the-age-of-ai)

## Related Jobs

- [Devops Engineer](https://www.wearedevelopers.com/jobs/ext/1940926-devops-engineer) at **Bitpanda**
- [Senior Software Engineer, Enterprise Products](https://www.wearedevelopers.com/jobs/ext/1841248-senior-software-engineer-enterprise-products) at **GitHub**
- [Platform Engineer (DevOps)](https://www.wearedevelopers.com/jobs/48264-platform-engineer-devops) at **WDW Consulting GmbH**
- [Principal Product Manager, Agent Platform](https://www.wearedevelopers.com/jobs/ext/277541-principal-product-manager-agent-platform) at **GitHub**
- [Lead Cloud DevSecOps Engineer - Kubernetes](https://www.wearedevelopers.com/jobs/ext/1659167-lead-cloud-devsecops-engineer-kubernetes) at **BWI GmbH**
- [Staff Software Engineer, Copilot Experiences](https://www.wearedevelopers.com/jobs/ext/164361-staff-software-engineer-copilot-experiences) at **GitHub**