Your cart is empty.
Keep shopping
Flux CD Mastery: GitOps for Kubernetes (Flux v2)
4,797 students
Flux CD Mastery: GitOps for Kubernetes (Flux v2)
Bootstrap Flux v2, run Helm and Kustomize the GitOps way, encrypt secrets, and automate image updates on real clusters
Created byAhmed Elfakharany
Last updated 10/2026
English
German [Auto],English
What you'll learn
- Bootstrap Flux v2 onto a cluster from a Git repository, and understand exactly what the bootstrap commit writes
- Deploy and upgrade applications with HelmRelease from Git, HTTP, OCI and Amazon ECR chart sources
- Structure a GitOps repository properly: monorepo, per-environment and multi-tenant layouts with Kustomize overlays
- Keep secrets in Git safely with Sealed Secrets, SOPS, GPG, Age and HashiCorp Vault, and verify charts with Cosign
- Automate container image updates end to end, so a new tag lands in Git and reaches the cluster without you touching it
- Wire Flux into Slack notifications and Git webhooks for instant reconciliation instead of waiting on an interval
Explore related topics
Coding Exercises
This course includes our updated coding exercises so you can practice your skills as you learn.
See a demo
Course content
7 sections • 44 lectures • 5h 58m total length
Requirements
- Comfortable with core Kubernetes objects: pods, deployments and services
- Basic Git: commit, branch and merge, plus a GitHub or GitLab account you can create an access token on
- Comfortable working in a terminal, and able to read and write YAML
- A cluster to practise on. The course uses a local KinD cluster, so a laptop is enough; two lectures optionally use AWS EKS and ECR
Description
This course contains the use of artificial intelligence.
Flux CD, taught on real clusters.
Flux v2 has removed its beta APIs. Manifests written against the old v2beta1 and v1beta2 API versions no longer reconcile, and your cluster tells you very little when it happens. This course includes a dedicated lecture on migrating manifests off the removed APIs, so you are not left guessing why a HelmRelease stopped working.
What you will actually do
You start by bootstrapping Flux v2 onto a KinD cluster from your own Git repository, and then look at what the bootstrap commit put there, because everything afterwards is just files in that repo. From there you deploy applications with Helm, pulling charts from Git, from HTTP repositories, from OCI registries, and from Amazon ECR using IRSA so that no credentials ever sit in your repository.
Then the course turns to the part most GitOps material skips: how to lay the repository out once it is no longer a demo. You restructure it into a monorepo with Kustomize base and overlay directories, apply per-environment patches so that staging and production differ without duplicating manifests, and then split it again for multi-tenancy, onboarding a dev team and an admin team with their own namespaces, service accounts and RBAC, so a tenant can deploy without being able to reach anything that is not theirs.
Secrets get a full section, because "commit your manifests to Git" and "never commit secrets" have to be reconciled somehow. You encrypt with Bitnami Sealed Secrets, with SOPS using GPG and with Age, and with HashiCorp Vault's transit engine. You also verify Helm chart signatures with Cosign, so you know a chart is the one its author actually published.
The final sections automate the loop. Flux watches your container registry, selects new tags by semantic version, writes them back to Git and reconciles them onto the cluster, for public registries and for private ones, where the two-Secret problem catches almost everyone. Then you wire Flux into Slack so it tells you what it did, and into Git webhooks so that a push reconciles immediately instead of waiting for the next interval.
Every lecture has a written companion. Alongside the videos there is a handout for each lecture: the concepts, and every command and manifest in copyable form, with links to the official documentation. They live in a public repository, so they stay current and you can read them without scrubbing through a video to find a flag.
Who this is for
Engineers who already run Kubernetes and want deployments to stop being something a person does by hand. If you have used kubectl apply in anger and thought there must be a better way to get changes into a cluster, this is that way.
Who this course is for:
- DevOps professionals who want to enhance their skills in managing Kubernetes deployments and leverage Flux CD as a powerful automation tool
- Administrators responsible for maintaining and managing Kubernetes clusters, aiming to streamline deployments and enforce GitOps workflows using Flux CD.
- Developers looking to improve their collaboration with DevOps teams and gain expertise in deploying applications using Flux CD and GitOps principles
- Professionals transitioning to Kubernetes from traditional IT roles, such as system administrators or network engineers, seeking to learn Flux CD and GitOps automation for efficient deployment management