Flux Kustomization Quick Fix - Kustomize Reconciliation

Flux Kustomization applies Kubernetes manifests from git/OCI/bucket sources using kustomize. Misconfigured kustomization paths or missing dependencies cause reconciliation failures. This guide covers the fix.

Quick Fix

Wrong

apiVersion: kustomize.toolkit.fluxcd.io/v1beta2
kind: Kustomization
metadata:
  name: apps
spec:
  interval: 10m
  sourceRef:
    kind: GitRepository
    name: flux-system

The issue: no path specified, so Flux tries to apply the root of the repository which may not have a kustomization.yaml. Also missing prune: true for garbage collection.

Right

apiVersion: kustomize.toolkit.fluxcd.io/v1beta2
kind: Kustomization
metadata:
  name: apps
spec:
  interval: 10m
  path: ./apps/production
  prune: true
  sourceRef:
    kind: GitRepository
    name: flux-system
  healthChecks:
  - apiVersion: apps/v1
    kind: Deployment
    name: my-app
    namespace: apps

# Expected output after applying the fix
# Kustomization applied from ./apps/production
# Prune enabled: removed resources are deleted from cluster
# Health checks verify Deployment my-app is ready
# Status: True (Ready)

Prevention

• Always specify path pointing to a directory with kustomization.yaml
• Set prune: true to automatically remove resources no longer in manifests
• Add healthChecks for deployment verification
• Use dependsOn for cross-kustomization ordering
• Validate kustomize output with kustomize build <path> before committing

DodaTech Tools

Doda Browser's kustomization dashboard shows sync status and drift detection. DodaZIP archives kustomization configurations. Durga Antivirus Pro validates kustomize transforms.

FAQ