Preview Environments with ArgoCD
summary
Shows a concrete GitOps pattern: Argo CD + ApplicationSet uses a pull-request generator that watches GitHub labels to create a namespace-per-PR, Helm values drive dynamic namespace and image tag, CI (example Codefresh) builds images and updates tags, and Argo sync phases/hooks (pre-sync/post-sync, waves) run validations, provision backing infra, run smoke tests and post PR comments with the URL. Preview environments automatically self-destruct on merge, support promotion to staging via image-tag substitution, and warn about DB, core-service and load-testing caveats.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:12Why should you care
- 3:36Use cases
- 5:38The bad
- 7:37The ugly
- 10:20Best practices
- 14:33Git Ops
- 15:33Sync
- 17:42Argo Application Sets
- 19:08Demo Overview
- 19:43PR Branch
- 20:56Repository
- 23:16App Set
- 25:42Preview Label
- 27:15Merge Pull Request
related talks
31mImplementing Preview Environments with GitOps in Kubernetes
12mApplication Preview Environments in 5 Minutes
33mA Journey To Ephemeral Test Environments With EKS and ArgoCD
59mPromotion Between Environme...
34mGitOps Patterns for managing cloud native applications
34mThe Full Stack Preview: Kubernetes, ArgoCD, and Ephemeral Databases
16mGitOps in Pratice
27mEphemeral Environment Practices - the Good, Bad, and Ugly