Keeping Progressive Delivery in Concert Across Multiple Microservices using Argo Rollouts
summary
Demo shows a working, GitOps-friendly pattern to update front end and back end together without a service mesh by using Argo Rollouts plus a configMap generator (kustomize) to bake the backend URL into each preview release so both services can be tested integrated. A Codefresh pipeline automates the promote steps. Caveat: set pruneLast=true in Argo CD so old configmaps don’t disappear on rollback. The approach is implemented and successfully switches traffic in the demo.
AI-written summary · about
chapters (14)
- 0:00Progressive Delivery intro
- 1:32Argo Rollouts overview
- 2:57Blue Green with Argo Rollouts
- 4:22Multi-service deployment challenges
- 6:07Modern vs legacy apps
- 9:36Legacy deployment strategy
- 10:41ConfigMaps for rollouts
- 12:50Live demo setup
- 13:33Backend config update 2.0
- 14:37Frontend with preview backend
- 15:42Promoting rollouts
- 17:33GitOps and CI/CD automation
- 18:58Caveats and best practices
- 19:41Summary
related talks
29mProgressive Delivery for Micro-Services Using Argo Rollouts and the Downward API
20mIntuitive Progressive Delivery Across Microservices in a Depe...
30mArgo Rollouts at Scale: How We Brought Automated Rollback to 2100+ Micro-serv...
35mCanary and Blue-Green Argo Rollouts made possible in a multi-cluster environment
22mThe Ortelius Journey with GitOps and Event Driven CI/CD
27mCrafting Resilient and Scalable Systems with Orchestration and Choreography Patterns on Kubernetes
10mGitOps and the CD Pipeline - Friend or Foe?
43mDynamic configuration management in microservice architecture with Spring Cloud