Managing Kubernetes the GitOps way with Flux
summary
Shows a battle‑tested GitOps setup that ties Flux to Kustomize and Helm, with a concrete repo layout (apps, cluster-services, clusters) used across multiple clients and clouds. Demonstrates passing Helm overrides via valuesFrom configMap and overlay patches, using Flux’s image automation commits to git to update image tags, wiring a webhook-triggered sync for instant reconciliation, and bootstrapping clusters with the bootstrap CLI; repo available at github.com/moonswitch-workshops/terraform-eks-flux.
AI-written summary · about
chapters (10)
- 0:00GitOps with Flux introduction
- 4:18GitOps foundations for Kubernetes
- 16:26Helm for Kubernetes packages
- 24:46What is GitOps?
- 31:30Introducing Flux toolkit
- 41:05Flux controllers explained
- 44:18Flux deployment structure
- 50:26Demo: Cluster services with Flux
- 55:04Q&A: Flux, Helm, GitOps
- 1:00:06Closing remarks
related talks
39mEnhance Your Kubernetes Experience with GitOps & Flux
49mGitOps, a somewhat realistic scenario on Kubernetes with Flux
42mIntro: Flux
47mDevOps:Config Mgmt for Kubernetes workloads with GitOps and Helm
20mGitOps Modern Operations for EKS
47mOne Repo to Rule Them All: Kubernetes Cluster Tenancy with Flux v2
23mGitOps: yea or nay?
22mPush to Prod: GitOps Workflows on k8s with FluxCD
