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

Flux Controller Architecture

Understanding the GitOps Toolkit controllers that make up Flux and their responsibilities in the reconciliation loop.

Flux Controller Architecture

What you'll learn: How Flux's modular controller design orchestrates continuous reconciliation of your Git-based infrastructure.

The Controller Symphony

Flux isn't a single monolithic application—it's a collection of specialized controllers working in concert. Each controller has a focused responsibility in the GitOps reconciliation loop, communicating through Kubernetes Custom Resources (CRs).

Think of it like an orchestra: each instrument (controller) plays its part independently, but together they create harmonious infrastructure automation.

The Core Controllers

Source Controller

The Source Controller is the librarian. It continuously fetches and validates content from external sources (Git repositories, Helm repositories, S3 buckets) and makes artifacts available to other controllers. It produces GitRepository, HelmRepository, and Bucket resources.

Kustomize Controller

The Kustomize Controller is the applier for Kustomize overlays. It watches Kustomization resources, retrieves artifacts from the Source Controller, builds manifests, and applies them to the cluster. It handles health checks, pruning, and dependency ordering.

Helm Controller

The Helm Controller manages Helm releases via HelmRelease resources. It installs, upgrades, tests, and rolls back Helm charts, pulling chart data from the Source Controller.

Notification Controller

The Notification Controller handles events and alerts. It receives events from other controllers and dispatches notifications to external systems (Slack, Microsoft Teams, webhooks). It also exposes webhook receivers for triggering reconciliations.

Image Reflector and Automation Controllers

These specialized controllers scan container registries and automatically update Git repositories with new image tags, enabling true continuous deployment.

How They Work Together

Each controller runs its own reconciliation loop, watching its Custom Resources and maintaining desired state. Controllers don't call each other directly—they communicate through Kubernetes resources, creating a loosely coupled, resilient architecture.

Key Takeaway: Flux's controller architecture is modular and composable—each controller has a single responsibility, enabling flexible GitOps workflows while maintaining clear separation of concerns in the reconciliation process.