Next-gen CI/CD with Gitops and Progressive Delivery

Deploying to production is not the same as releasing to users. Learn how GitOps and progressive delivery de-risk your pipeline and enable safer, frequent updates.

#1about 4 minutes

The evolution of CI/CD from manual to automated

The journey from manual FTP deployments to automated CI/CD systems like Jenkins highlights the increasing need for reliable and repeatable release processes.

#2about 1 minute

Understanding GitOps for declarative application delivery

GitOps uses Git as the single source of truth for both application code and infrastructure configuration, enabling auditable and easily reversible deployments.

#3about 4 minutes

How GitOps complements traditional CI/CD workflows

While CI/CD is a one-way push for building artifacts, GitOps creates a continuous reconciliation loop to ensure the live cluster state always matches the desired state in Git.

#4about 4 minutes

Reducing release risk with progressive delivery techniques

Progressive delivery minimizes production risk by separating deployment from release, allowing for gradual rollouts and validation before exposing new versions to all users.

#5about 3 minutes

Implementing delivery patterns with Kubernetes and Istio

Native Kubernetes can handle basic blue-green and canary releases, but a service mesh like Istio provides more advanced traffic shaping capabilities for precise control.

#6about 2 minutes

Automating progressive delivery with Argo Rollouts

Argo Rollouts automates complex release strategies like canary and blue-green deployments by defining rollout steps and pauses directly in a declarative manifest.

#7about 1 minute

Using metrics for automated analysis and rollbacks

Argo Rollouts can integrate with monitoring tools like Prometheus to create analysis templates that automatically abort a release and roll back if key metrics like error rates degrade.

#8about 7 minutes

Demo of a successful and failed automated rollout

A live demonstration shows Argo Rollouts successfully completing a canary release, followed by another release that is automatically aborted and rolled back due to injected errors.

#9about 2 minutes

Addressing challenges with stateful applications

Progressive delivery with stateful applications requires careful handling of database schema changes to ensure backward compatibility during rollouts and potential rollbacks.