DevOps:Config Mgmt for Kubernetes workloads with GitOps and Helm
summary
Demo shows a GitOps flow where a git repo is the single source of truth, Flux watches master/manifests and flux pulls every 15s to apply changes, and the Helm operator reads a HelmRelease CRD to install charts. The demo app uses four YAMLs (namespace, configmap, deployment, service) and a simple Helm chart with five templates; pushing commits updates images (1.10→1.11→1.13) and scaling (green replica count 1→2) and a manually deleted namespace is restored in seconds, with rollbacks done by checking out git.
AI-written summary · about
chapters (15)
- 0:00Introduction to speaker
- 0:55What is config management
- 5:18Kubernetes and declarative APIs
- 7:44Why GitOps is needed
- 9:34Flux as GitHub operator
- 11:43Basic Flux demonstration
- 23:33Flux workflow summary
- 24:20Introduction to Helm
- 25:48Helm templating demo
- 31:12Connecting Flux and Helm
- 34:01Flux Helm operator demo
- 40:33Benefits of GitOps workflow
- 42:21GitOps pattern summary
- 43:25Comparing old and new practices
- 46:41Talk conclusion and resources
related talks
01h 01mManaging Kubernetes the GitOps way with Flux
22mPush to Prod: GitOps Workflows on k8s with FluxCD
49mGitOps, a somewhat realistic scenario on Kubernetes with Flux
27mLightning Talk: GitOps, A Slightly Realistic Situation on Kubernetes with Flux
15mPlatform Engineering Done Right: Safe, Secure, & Scalable Multi-Tenant GitOps
45mFrom DevOps to GitOps: Supercharging Your Kubernetes Workload Deployments
32mIntroducing Flux Helm Operator, a GitOps Approach to Helm Operations
23mGitOps: yea or nay?