← All insightsBest Practices

Common Flux CD mistakes and how to avoid them

CodeWizard Academy · 2 June 2026 · 3 min read · Intermediate

Most Flux CD pain is self-inflicted and predictable. Here are the mistakes we see most, and the fix for each.

Mistake 1: Long reconcile intervals hiding how stale the cluster is

Fix: Set prune:true and sensible intervals per Kustomization. Make it the default in your templates and enforce it in review or CI so the mistake cannot come back.

Mistake 2: Forgetting prune:true, so deleted files stay live in the cluster

Fix: Use the notification controller to alert on reconcile failures. Make it the default in your templates and enforce it in review or CI so the mistake cannot come back.

Mistake 3: No notifications wired up, so failed reconciliations go unnoticed

Fix: Separate infrastructure and app Kustomizations with dependsOn. Make it the default in your templates and enforce it in review or CI so the mistake cannot come back.

A safer baseline

A GitRepository source plus a Kustomization that applies it.

yaml
apiVersion: source.toolkit.fluxcd.io/v1
kind: GitRepository
metadata: { name: apps, namespace: flux-system }
spec:
  interval: 1m
  url: https://github.com/acme/deploy
  ref: { branch: main }
---
apiVersion: kustomize.toolkit.fluxcd.io/v1
kind: Kustomization
metadata: { name: web, namespace: flux-system }
spec:
  interval: 5m
  path: ./apps/web
  prune: true
  sourceRef: { kind: GitRepository, name: apps }

Want senior help putting Flux CD to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.

Like where this is going?

Get hands-on help from the engineers who write these posts.

Book a free consult