Preparing for a DevOps interview that covers Flux CD? These questions come up again and again - here are strong, concrete answers.
Q: What is Flux CD and why use it?
Flux is a set of Kubernetes controllers that keep clusters in sync with sources like Git, Helm repositories and OCI artifacts, with first-class Kustomize and Helm support.
- Composable controllers (source, kustomize, helm, notification)
- Native Helm and Kustomize reconciliation from Git or OCI
- Strong multi-tenant and progressive-delivery support (Flagger)
Q: What are the best practices you follow?
- Set prune:true and sensible intervals per Kustomization
- Use the notification controller to alert on reconcile failures
- Separate infrastructure and app Kustomizations with dependsOn
Q: What mistakes have you seen?
- Long reconcile intervals hiding how stale the cluster is
- Forgetting prune:true, so deleted files stay live in the cluster
- No notifications wired up, so failed reconciliations go unnoticed
Q: Show a basic configuration
A GitRepository source plus a Kustomization that applies it.
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.