The journey from manual FTP deployments to automated CI/CD systems like Jenkins highlights the increasing need for reliable and repeatable release processes.
GitOps uses Git as the single source of truth for both application code and infrastructure configuration, enabling auditable and easily reversible deployments.
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.
Progressive delivery minimizes production risk by separating deployment from release, allowing for gradual rollouts and validation before exposing new versions to all users.
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.
Argo Rollouts automates complex release strategies like canary and blue-green deployments by defining rollout steps and pauses directly in a declarative manifest.
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.
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.
Progressive delivery with stateful applications requires careful handling of database schema changes to ensure backward compatibility during rollouts and potential rollbacks.
27:52Carlos Sanchez
50:02Liviu Costea
29:49Lian Li
25:24Florian Trieloff
28:45Lian Li
50:28Zan Markan
36:09Chad Carlson
47:42Roberth Strand
.gif?w=240&auto=compress,format)
Jobs that call for the skills explored in this talk.
smartclip Europe GmbH
Hamburg, Germany
iits-consulting GmbH
München, Germany
SYSKRON GmbH
Regensburg, Germany
Atruvia AG
Berlin, Germany
CGI Group Inc.
Köln, Germany
Rocken AG