GitOps, Continuous Delivery and Environments: How to Avoid Hell?!
summary
Covers managing environments when implementing Continuous Delivery and GitOps for applications, especially as Blue-Green and Canary Deployments plus microservices increase the number of environments and configuration parameters. Explains problems such as rollbacks, operational intervention at night, and environment stability, then presents practical best practices and tips to avoid those operational headaches.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:06GitOps config problems
- 7:46Simplify architecture
- 10:52Lifecycle thinking
- 13:39Avoid extra params
- 16:06Top config manager approach
- 22:43Config manager risks & best practices
- 23:46Conclusion
related talks
35mGitOps Approaches and Trade-offs
29mPutting the Ops in GitOps - New Challenges in Managing Cloud Native Environments
55mGitOps, Fostering Next-Generation Operations Teams
36mGitOps: The Single source of truth
10mGitOps and the CD Pipeline - Friend or Foe?
35mApproach to GitOps — Achievements, Mistakes and Lessons Learned
23mContinuous Deployment - The Last Frontier for Continuous Delivery
47mGitOps - Using Git as your source of truth for build, deploy and observability