Kustomize Controller Fundamentals
You'll learn: How the Kustomize Controller in Flux applies Kubernetes manifests with built-in validation, health monitoring, and dependency management.
What is the Kustomize Controller?
The Kustomize Controller is a Flux component that reads manifests from your Git repositories and applies them to your Kubernetes cluster. Think of it as an intelligent deployment engine that doesn't just blindly apply YAML—it validates resources, checks their health, and respects dependencies between applications.
While the Source Controller (from the previous lesson) fetches your Git repositories, the Kustomize Controller actually does something with those files: it transforms them using Kustomize and applies them to your cluster.
How Kustomization Resources Work
You define a Kustomization resource (not to be confused with Kustomize's kustomization.yaml file) that tells Flux:
- Where to find manifests (which Source to use)
- How to apply them (with validation checks)
- What to monitor (health status of deployed resources)
- What depends on what (ensure database deploys before application)
The controller continuously reconciles: it compares what's in Git with what's running in your cluster and corrects any drift.
Key Features
Validation: The controller checks your manifests for errors before applying them, preventing broken deployments.
Health Checks: It monitors deployed resources and reports their status—did that Deployment roll out successfully? Are all pods ready?
Dependencies: You can specify that one Kustomization must succeed before another starts, ensuring proper ordering (like infrastructure before applications).
Key Takeaway: The Kustomize Controller is Flux's deployment engine that safely applies manifests with validation, health tracking, and ordered dependencies—transforming Git commits into reconciled cluster state.