Implementing Preview Environments with GitOps in Kubernetes
Talkat GitOpsCon Europe 2022 · on Tuesday, 2022-05-17· at 12:45· Joaquin Rodrigo Room I | Mall Level | Central Forum·
summary
Shows how a per‑PR ephemeral environment is created by committing a YAML with the image tag to an ops repo and letting Argo CD reconcile into a new namespace, using Bitbucket Pipelines to build/push to Docker Hub, Helm charts stored in the app repo, and Sealed Secrets for safe creds. Flux manages cluster infra while Argo serves developer UX. Provisioning works in practice, builds take ~5 minutes, and namespaces auto‑delete on PR close.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:31About
- 1:27A standard Git Flow
- 4:43GitOps & Preview environments (PE)
- 7:06Some pitfalls during PE
- 8:50CI-Bitbucket Pipelines (docker)
- 9:42CI-Bitbucket Pipelines (CD)
- 11:20CD with ArgoCD
- 12:11Why ArgoCD?
- 14:13Storing secrets in ...G?
- 15:53HTTPS - Multi-tenant
- 16:55HTTPS management
- 17:53Bringing order with ArgoCD Hooks
- 18:49Cleaning up-Namespaces mess 3
- 19:41Improving DX (1/4)
- 22:54Renovabot
related talks
32mPreview Environments with ArgoCD
12mApplication Preview Environments in 5 Minutes
32mGitOps and Multi-Environments: A Story of Promotion
45mFrom DevOps to GitOps: Supercharging Your Kubernetes Workload Deployments
33mGitOps Pipelines: Everything Everywhere All at Once
33mA Journey To Ephemeral Test Environments With EKS and ArgoCD
56mNavigating the GitOps ecosystem: The principles and in-depth look at Argo and Flux
31mGitOps, the Final Frontier: Proposing, Promoting, and Reverting