Course contentsShow
← Cloud and Infrastructure
Lesson 1920 of 2,98941. FluxFree lesson

Flux Architecture and Components Overview

Learn the core Flux components: source-controller, kustomize-controller, helm-controller, and notification-controller.

Flux Architecture and Components Overview

What you'll learn: How Flux's modular component architecture orchestrates GitOps deployments on Kubernetes.

The Flux Component Model

Flux operates as a collection of specialized controllers, each handling a distinct part of the GitOps workflow. Unlike monolithic tools, Flux's architecture separates concerns into four core components that work together seamlessly. Think of it like an assembly line: each station has one job, and together they transform Git commits into running infrastructure.

The Four Core Controllers

source-controller

This component watches Git repositories, Helm repositories, and S3 buckets for changes. It fetches source code and artifacts, then exposes them to other controllers. It's the "intake department" — everything starts here.

kustomize-controller

Handles Kustomize-based deployments. It takes sources from the source-controller, applies Kustomize transformations, and reconciles the manifests against your cluster. If you're using plain YAML or Kustomize overlays, this is your engine.

helm-controller

Manages Helm chart installations and upgrades. It pulls charts from sources and performs Helm releases, handling values, dependencies, and rollbacks. This lets you use Flux with the Helm ecosystem.

notification-controller

Provides event forwarding and webhooks. It receives events from other controllers (sync success, failures) and can send alerts to Slack, Microsoft Teams, or trigger GitHub commit statuses. It's also how external systems notify Flux of changes.

How They Work Together

When you commit a change to Git, the source-controller detects it, the kustomize or helm-controller applies it to your cluster, and the notification-controller tells your team. Each component runs independently, communicating through Kubernetes custom resources, making the system resilient and scalable.

Key Takeaway: Flux's architecture splits GitOps into four specialized controllers—source, kustomize, helm, and notification—creating a modular, extensible reconciliation system.