Most Asked FluxCD Questions: CLI and CRD Fields (2027)
36 most asked FluxCD interview questions on the flux CLI and Kustomization, HelmRelease and source fields, checked against Flux v2.10.0 docs.
Many FluxCD interviews include a hands-on round: you are given a cluster or a YAML file and asked which flux command to run, or what a field such as prune, dependsOn, wait or driftDetection does. This page collects 36 of the most asked questions on the Flux CLI and the Kustomization, HelmRelease and source APIs, checked against Flux v2.10.0. Questions are grouped by level, and a scenario section shows how to diagnose common failures with the CLI.
It is a hands-on companion to our top FluxCD GitOps interview questions, which cover GitOps concepts and architecture. Here the focus is commands and fields you type or read during a live exercise. Facts come from the Flux documentation and the Flux v2.10.0 release notes (26 October 2026).
Key takeaways
- Flux v2.10.0 is current. Source and Kustomization APIs are at v1, HelmRelease is at
helm.toolkit.fluxcd.io/v2, and v2.10.0 promoted the notification Event, Alert and Provider APIs to v1. flux reconcile kustomization NAME --with-sourceforces a fetch of the source and then a reconcile.flux get,flux events,flux logsandflux debugare the first commands to run when something is not ready.- In a Kustomization,
.spec.wait: truehealth-checks every applied object and makes.spec.healthChecksignored. .spec.deletionPolicydefaults toMirrorPrune, so deleting a Kustomization deletes its objects only whenpruneis true.- HelmRelease
driftDetection.modecan beenabledorwarn, and specific paths such as/spec/replicascan be ignored.
Flux commands you should know
| Task | Command |
|---|---|
| Check prerequisites and controllers | flux check --pre then flux check |
| Bootstrap on GitHub | flux bootstrap github --owner=ORG --repository=fleet --path=clusters/prod |
| List all Flux objects and status | flux get all -A |
| Force a sync now | flux reconcile kustomization apps --with-source |
| Pause and resume | flux suspend kustomization apps / flux resume kustomization apps |
| Preview changes | flux diff kustomization apps --path ./apps/prod |
| Read events | flux events --for Kustomization/apps |
| Read controller logs | flux logs --level=error |
| Inspect a failing release | flux debug helmrelease podinfo |
FluxCD CLI questions for freshers
1. What does flux check do?
It verifies that the Kubernetes version is supported and that the Flux controllers are installed and healthy. flux check --pre runs only the prerequisite checks before installation.
2. What does flux bootstrap do?
It installs the Flux controllers, commits their manifests to a Git repository, and creates a GitRepository and Kustomization that point back at that repository, so Flux then manages itself from Git. There are variants for GitHub, GitLab, Gitea, Bitbucket Server and generic Git.
3. What is the difference between flux install and flux bootstrap?
flux install applies the controllers to the cluster only. Nothing is written to Git, so Flux does not manage its own upgrades. Bootstrap adds the Git side, which is the usual production choice.
4. How do you list everything Flux manages?
flux get all -A shows sources, Kustomizations and HelmReleases in every namespace with their ready status and the revision applied. flux get kustomizations or flux get sources git narrows it down.
5. How do you force Flux to sync right now?
flux reconcile kustomization apps --with-source. Without --with-source, the Kustomization re-applies the artifact it already has and does not fetch the latest commit.
6. How do you pause reconciliation during an incident?
flux suspend kustomization apps sets .spec.suspend: true, so Flux stops applying changes and stops correcting drift for that object. Run flux resume kustomization apps afterwards. Write down every suspend, because a forgotten suspend silently stops GitOps for that object.
7. How do you create a GitRepository source from the CLI?
flux create source git podinfo \
--url=https://github.com/stefanprodan/podinfo \
--branch=master \
--interval=1m \
--export > podinfo-source.yaml
--export prints YAML instead of applying it, so you can commit the file to Git.
8. What is a Kustomization in Flux?
A kustomize.toolkit.fluxcd.io/v1 object that takes an artifact from a source, builds the manifests at .spec.path with Kustomize, and applies them with server-side apply on an interval. It is not the same as a Kustomize kustomization.yaml file, although it uses one if present.
9. What does .spec.interval mean on a Kustomization?
How often Flux reconciles the object. On each run it does a server-side apply dry run to detect and correct drift, even when the Git revision has not changed.
10. What does .spec.prune do?
When true, objects that were applied before but are missing from the current revision are deleted from the cluster. Without prune, removing a file from Git leaves the object running.
11. What sources can Flux pull from?
GitRepository, OCIRepository, Bucket, HelmRepository and HelmChart, plus ExternalArtifact for artifacts produced by other controllers. All are in the source.toolkit.fluxcd.io/v1 API.
12. Which command shows why a resource is not ready?
flux events --for Kustomization/apps shows the events for that object, and flux get kustomization apps shows the Ready message. kubectl describe works too, because these are ordinary Kubernetes resources.
Kustomization and HelmRelease field questions (2 to 5 years)
13. What does .spec.dependsOn do?
It lists other Kustomizations that must have Ready=True before this one is applied. A common use is applying CRDs and controllers before the custom resources that need them.
14. What is the difference between .spec.wait and .spec.healthChecks?
wait: true health-checks every object the Kustomization applied. healthChecks lists specific objects to check. If wait is true, healthChecks is ignored. Pair either with .spec.timeout so a stuck rollout fails instead of hanging.
15. What does .spec.timeout cover?
It is the time limit for operations such as building, applying and health checking. When it runs out, the Kustomization is marked not ready with a timeout reason, and dependents stay blocked.
16. What does .spec.targetNamespace do?
It sets or overrides the namespace of every namespaced object the Kustomization applies, which lets one set of manifests deploy to several namespaces.
17. How do you substitute variables in manifests?
Use .spec.postBuild.substitute for inline values and .spec.postBuild.substituteFrom to read them from ConfigMaps or Secrets. Flux replaces ${var} placeholders after the Kustomize build. Mark a source as optional if it may not exist.
apiVersion: kustomize.toolkit.fluxcd.io/v1
kind: Kustomization
metadata:
name: apps
namespace: flux-system
spec:
interval: 10m
path: ./apps/prod
prune: true
wait: true
timeout: 5m
sourceRef:
kind: GitRepository
name: fleet
dependsOn:
- name: infra-controllers
postBuild:
substitute:
cluster_env: prod
18. How does Flux decrypt secrets stored in Git?
Set .spec.decryption with provider: sops and a secretRef that holds the private key (age or PGP), or use cloud KMS through workload identity. Flux decrypts during the build, so only encrypted files live in Git.
19. What does .spec.deletionPolicy control?
What happens to applied objects when the Kustomization itself is deleted. MirrorPrune (the default) follows prune, Delete always removes them, WaitForTermination deletes them and waits until they are gone, and Orphan leaves them running.
20. What does .spec.force do?
It lets Flux recreate objects when an immutable field change makes a patch fail, for example a Job's pod template. Use it with care, because recreating can cause brief downtime.
21. What is the HelmRelease API version and what does it do?
helm.toolkit.fluxcd.io/v2. A HelmRelease points at a chart, through .spec.chart or .spec.chartRef, plus values. The helm-controller installs or upgrades it with the Helm SDK. In v2.10.0, OCIRepository is also supported as a chart source for HelmRelease.
22. What are install and upgrade remediation retries?
.spec.install.remediation.retries and .spec.upgrade.remediation.retries set how many times the controller retries after a failed install or upgrade. Failed upgrades can be rolled back automatically, depending on the remediation strategy.
apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
metadata:
name: podinfo
namespace: apps
spec:
interval: 10m
chartRef:
kind: OCIRepository
name: podinfo
install:
remediation:
retries: 3
upgrade:
remediation:
retries: 3
driftDetection:
mode: enabled
ignore:
- paths: ["/spec/replicas"]
target:
kind: Deployment
values:
replicaCount: 2
23. What does HelmRelease driftDetection do?
With mode: enabled, the controller compares cluster objects with the manifest stored in the Helm release and corrects differences. mode: warn only reports them. Ignore rules exclude fields that something else changes on purpose, such as replicas managed by an HPA.
24. What does valuesFrom do?
It merges values from ConfigMaps or Secrets into the release, so environment-specific or sensitive values do not have to be inline in the HelmRelease.
25. What does .spec.test.enable do?
It runs the chart's Helm tests after install or upgrade. You can filter which tests run and choose to ignore failures, though ignoring them reduces their value.
26. What does flux diff kustomization show?
It builds the manifests from a local path and shows how they differ from what is in the cluster, without applying. It is useful in pull request checks and before risky merges.
27. What does flux build kustomization do?
It renders the manifests locally the way the kustomize-controller would, including post-build substitutions, so you can check the output before committing.
Senior-level questions
28. How do you structure a multi-cluster Flux repository?
The common pattern is clusters/<name> folders that each hold the Flux system Kustomization and point to shared infrastructure and apps bases with per-cluster overlays. Use dependsOn so controllers come before workloads.
29. How do you limit what a tenant's Kustomization can do?
Set .spec.serviceAccountName so the controller impersonates a namespaced service account with limited RBAC, and run controllers with flags that stop cross-namespace references. flux create tenant scaffolds the namespace, service account and role binding.
30. How do you speed up deployments without lowering intervals everywhere?
Use a notification Receiver so Git provider webhooks trigger reconciliation as soon as a commit lands. Keep longer intervals as a safety net for drift correction.
31. How does Flux send alerts?
Create a Provider (for example Slack, Microsoft Teams or a generic webhook) and an Alert that selects event sources and severity. v2.10.0 added Zoom, incident.io and Mastodon providers and promoted these APIs to v1.
32. How does image update automation work?
ImageRepository scans a registry, ImagePolicy picks the newest tag by a rule such as semver, and ImageUpdateAutomation commits the new tag back to Git where a marker comment sits in the YAML. Git stays the source of truth.
Scenario questions
33. A merged commit is not deployed after 15 minutes.
Run flux get sources git to see whether the source fetched the new revision. If not, check credentials and the branch. If it did, run flux get kustomizations and flux events for build or apply errors, and check whether the object is suspended.
34. A HelmRelease is stuck with "upgrade retries exhausted".
Run flux debug helmrelease NAME and flux logs --kind=HelmRelease --name=NAME to find the failing step. Fix the chart or values in Git. Then run flux reconcile helmrelease NAME --reset to reset the failure count, or --force for a one-off install or upgrade.
35. Deleting a folder from Git did not delete the workloads.
.spec.prune is false on the Kustomization that applied them. Enable prune, and review the inventory with flux tree kustomization NAME before the next reconcile so you know what will be removed.
36. An HPA scales a Deployment and Flux keeps scaling it back.
Remove replicas from the manifest, or for a HelmRelease add a drift detection ignore rule for /spec/replicas on the Deployment.
How to practise
Bootstrap Flux into a kind cluster against a personal Git repository, add a Kustomization and a HelmRelease, then break each one on purpose and fix it using only the flux CLI. The 70+ FluxCD interview questions cover fundamentals, the FluxCD study plan gives a schedule, and the scenario-based FluxCD questions go deeper on incidents. For GitOps background see what GitOps is and how ArgoCD and Flux enable declarative deployments.
Flux work assumes solid Kubernetes skills. The CKA training runs in our Kharadi, Pune classroom and live online.
Frequently asked questions
How do I force Flux to reconcile immediately?
Run flux reconcile kustomization NAME --with-source so the source is fetched before the apply.
What is the latest Flux version?
Flux v2.10.0, released on 26 October 2026.
What does prune do in a Flux Kustomization?
It deletes objects that were applied before but no longer exist in the source revision.
Which API version does HelmRelease use?
helm.toolkit.fluxcd.io/v2.
How do I stop Flux while I fix something by hand?
Run flux suspend on the object, fix the issue, commit the fix to Git and then run flux resume.
Can Flux ignore replica changes made by an HPA?
Yes. Leave replicas out of the manifest, or add a drift detection ignore rule for /spec/replicas in the HelmRelease.
References
What's Your Reaction?
Like
0
Dislike
0
Love
0
Funny
0
Angry
0
Sad
0
Wow
0