| Feature | Description |
|---|---|
| Validation | Checks your manifests against the Kubernetes API before applying changes. |
| Apply / Update | Creates or updates resources based on the desired state. |
| Health Assessment | Monitors workloads to ensure they remain healthy after deployment. |
| Pruning (Garbage Collection) | Optionally removes resources that no longer exist in your source manifests. |
Make sure you have installed Flux and configured a
GitRepository or other supported source.1. Creating a Kustomization
Use theflux create kustomization command to link your source to a path containing Kustomize overlays. You can also enable garbage collection:
--export flag prints the Kustomization resource manifest:
2. Automatic Build Behavior
If there’s nokustomization.yaml file under ./solar-system, Flux will auto-generate one for you:
kustomization.yaml with all discovered resources:
You don’t need to run the above command yourself—Flux performs it automatically when needed.
3. Providing Your Own Overlays
If you include a customkustomization.yaml (or Kustomization overlay) in the specified path, the controller will skip auto-generation and apply your overlays directly. This allows you to:
- Add labels or annotations
- Patch existing resources
- Customize namespace or image tags
4. Checking Status
To inspect all activeKustomization resources and their reconciliation state: