CD and GitOps with flux @AdoreMe
summary
AdoreMe runs Flux on eight GKE clusters managing about 42,000 Helm releases and doing roughly 5,900 production deploys per year while total deploys hit the tens of thousands. Flux uses the Helm API so Helm hooks run as with helm CLI, and the image automation scans Quay and the Google artifact registry then commits updated image tags back to git to trigger deployments. The setup uses base/overlay repos for prod and UAT, helps sync 30–40 dev environments, and costs extra CRD operational work and careful repo partitioning.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:28AdorMe’s Kubernetes and Flux setup
- 3:57GitOps and advantages
- 9:44Flux CD components
- 11:33Typical workflow with Flux
- 16:32Pros and cons of Flux
- 19:21Repository structure
- 27:03Image automation
- 28:30Q&A
related talks
42mIntro: Flux
07mFluxCD - Gitops For All Sizes
21mIntroduction to FluxCD
24mHosting Applications in the Real World
01h 01mManaging Kubernetes the GitOps way with Flux
22mPush to Prod: GitOps Workflows on k8s with FluxCD
39mEnhance Your Kubernetes Experience with GitOps & Flux
47mDevOps:Config Mgmt for Kubernetes workloads with GitOps and Helm