FluxCD FAQs: Bootstrap, Tenancy, Image Updates (2027)
30 Flux FAQs on controllers, bootstrap, Kustomization, HelmRelease, multi-tenancy, SOPS, image automation, notifications and troubleshooting.
Flux is a set of Kubernetes controllers that keep a cluster matching what is stored in Git, an OCI registry or a bucket. This FAQ answers 30 common Flux interview questions on bootstrap, sources, Kustomization and HelmRelease, multi-tenancy, SOPS, image automation, notifications and troubleshooting, using the Flux docs (v2.10.0 at the time of writing).
This page is the concept FAQ. For the interview question bank see top FluxCD GitOps interview questions, for field-level CLI and CRD details see most asked FluxCD questions, and for failure stories see scenario-based FluxCD questions. New to the idea? Start with what GitOps is.
Key takeaways
- Flux v2 is split into controllers: source, kustomize, helm, notification and image automation, each owning its own custom resources.
flux bootstrap githubdeploys the controllers, pushes their manifests to your repository, and configures Flux to update itself from Git.- By default Flux controllers run as cluster-admin. Tenant isolation comes from
serviceAccountNameimpersonation plus lockdown flags such as--no-cross-namespace-refs. - SOPS is the supported decryption provider for secrets stored in Git.
- Flux v2.10.0 promoted the Notification Event, Alert and Provider APIs to v1 and lets OCIRepository act as a chart source for HelmRelease.
Level 1: Core concepts
1. What is Flux and what does it reconcile?
Flux is a CNCF GitOps toolkit for Kubernetes. It continuously compares the cluster with a declared source and applies the difference. The source can be a Git repository, an OCI artifact, a Helm repository or a bucket, and the cluster is pulled toward it rather than pushed to by CI.
2. Which controllers make up Flux?
| Controller group | API kinds it manages |
|---|---|
| Source controllers | GitRepository, OCIRepository, HelmRepository, HelmChart, Bucket, ExternalArtifact, ArtifactGenerator |
| Kustomize controller | Kustomization |
| Helm controller | HelmRelease |
| Notification controller | Provider, Alert, Receiver |
| Image automation controllers | ImageRepository, ImagePolicy, ImageUpdateAutomation |
3. Why is pull-based delivery considered safer than push?
Credentials for the cluster stay inside the cluster. CI does not need a kubeconfig, so a compromised pipeline cannot deploy directly. Every change also passes through Git, which gives you review and an audit trail.
4. What is the difference between a GitRepository and a Kustomization?
A GitRepository fetches and stores a revision of the source. A Kustomization points at that source with sourceRef, builds the manifests under path and applies them. One source can feed many Kustomizations.
5. What does a Kustomization require?
A sourceRef, an interval (minimum 60 seconds) and prune. Common optional fields are path (blank means the root of the artifact), retryInterval (defaults to the interval), timeout, wait, healthChecks, dependsOn and targetNamespace.
6. What does prune: true do?
It garbage collects resources that were applied earlier but removed from the source. Turn it on for environments you want to match Git exactly, and review it before enabling on shared namespaces.
7. How does Flux tell whether a deployment is healthy?
Set wait: true to health check everything the Kustomization reconciled, or list specific resources in healthChecks. When wait is true, healthChecks is ignored. The Kustomization is Ready only when the checks pass within the timeout.
8. How do you order two Kustomizations?
Use dependsOn. The dependent Kustomization waits until the listed ones are Ready, and an entry can carry a readyExpr. Typical use is infrastructure first, apps second.
Level 2: Install, Helm and variables
9. What does flux bootstrap github do?
It deploys the Flux controllers, configures them to sync from your GitHub repository, pushes the Flux manifests to the repo, sets Flux to update itself from Git, and stores the token or deploy key as a Secret in the flux-system namespace. It needs cluster admin and repository access.
export GITHUB_TOKEN=<your-token>
flux bootstrap github \
--token-auth \
--owner=my-org \
--repository=fleet-infra \
--branch=main \
--path=clusters/my-cluster
10. Which token permissions does bootstrap need?
For a fine-grained token: Administration (read-only), Contents (read and write) and Metadata (read-only). Administration must be read and write if you use deploy keys with --token-auth=false. A classic token for a personal account needs the repo scope.
11. How do you configure a HelmRelease?
Use apiVersion helm.toolkit.fluxcd.io/v2, set spec.interval, and give either spec.chart or spec.chartRef, never both. Values go in spec.values or valuesFrom (a ConfigMap or Secret), and inline values override valuesFrom.
12. What are the HelmRelease defaults worth remembering?
| Field | Default |
|---|---|
| timeout | 5m0s |
| maxHistory | 5 |
| install and upgrade remediation retries | 0 (negative means infinite) |
| upgrade remediation strategy | rollback |
| crds policy | Create (others: Skip, CreateReplace) |
13. How do you detect and correct drift in a Helm release?
Set spec.driftDetection.mode to warn to report drift or enabled to detect and correct it. The docs do not state a default, so set it explicitly.
14. How do you substitute variables into manifests?
Use postBuild.substituteFrom with ConfigMaps or Secrets. Each entry is required unless you set optional: true, so a missing object fails reconciliation by default.
15. What is the difference between flux install and bootstrap?
flux install only installs the controllers. Bootstrap installs them and also wires the cluster to a Git repository, then commits its own manifests so Flux manages itself.
Level 3: Security and multi-tenancy
16. Why do Flux controllers have cluster-admin by default?
Because they must create arbitrary resources. In a shared cluster you restrict what a tenant can apply by setting .spec.serviceAccountName on a Kustomization or HelmRelease. Flux then impersonates that account and Kubernetes RBAC limits the tenant.
17. Which lockdown flags matter for multi-tenancy?
| Flag | Effect |
|---|---|
--no-cross-namespace-refs=true | A tenant cannot use another tenant's sources or events |
--no-remote-bases=true | Kustomize bases come only from local Flux sources |
--default-service-account=default | Resources without serviceAccountName run as the namespace's default account, which has no permissions |
18. Does the flux-system Kustomization stay privileged?
Yes. It runs with cluster-admin access so platform admins can manage namespaces, service accounts and RBAC, while tenants are held to their own accounts.
19. How do you keep secrets safe in Git?
Encrypt them with SOPS and enable decryption on the Kustomization with decryption.provider: sops, the only supported provider. Reference the key Secret, and never commit the private key.
20. How should Flux access private repositories?
Use a deploy key or token stored in a Secret referenced by the GitRepository. Keep the credential read-only unless image automation must push commits.
Level 4: Automation, notifications and troubleshooting
21. How does image automation work?
An ImageRepository scans a registry, an ImagePolicy picks a tag using semver, alphabetical or numerical rules, and an ImageUpdateAutomation writes the new tag into marked manifests and pushes a commit. Flux then applies that commit like any other change.
22. How do you mark which field to update?
Add a setter comment to the image field, such as image: ghcr.io/org/app:1.0.0 # {"$imagepolicy": "flux-system:app"}. Suffixes :tag, :name and :digest target part of the reference.
23. What happens when an ImageUpdateAutomation runs?
It processes every ImagePolicy in its namespace at its interval, checks out the configured branch, updates marked fields under spec.update.path, commits with your message template and pushes to spec.git.push.branch, which it creates if missing.
24. How do notifications reach Slack or other tools?
A Provider defines the target, and an Alert selects events and sends them through that Provider. A Receiver accepts incoming webhooks to trigger reconciliation. Flux v2.10.0 promoted Event, Alert and Provider to the v1 API.
25. First commands when something is not reconciling?
flux check
flux get all -A --status-selector ready=false
flux get sources all -A
flux logs --all-namespaces --level=error
kubectl get events -n flux-system --field-selector type=Warning
26. A HelmRelease says "install retries exhausted". Next step?
Run kubectl describe helmrelease <name> -n <namespace> to read the events and last Helm logs. To inspect failing resources, set spec.install.disableWait: true and spec.upgrade.disableWait: true temporarily.
27. "Request entity too large: limit is 3145728"?
The Helm release does not fit in a Secret. Exclude unneeded files with the chart's .helmignore and the source's .sourceignore, and shrink the chart.
28. "admission webhook does not support dry run"?
Set the webhook's sideEffects to None or NoneOnDryRun, since Flux applies with dry run first.
29. How do you pause reconciliation safely?
Set suspend: true on the object (or use flux suspend). Removing the field or setting it to false resumes it. Record why it was suspended so the pause is not forgotten.
30. How does Flux differ from Argo CD in design?
Flux is a toolkit of controllers you compose through custom resources, with the Kubernetes API as the interface. Argo CD centers on an Application resource and ships an API server, web UI and CLI along with SSO and RBAC. Many teams choose by operating style, not capability. See top GitOps tools for Kubernetes and GitOps deployment best practices.
Upgrade notes from Flux v2.10.0
Read the release notes before upgrading, because v2.10.0 lists breaking changes. The default RBAC no longer grants create on serviceaccounts/token, so check any tenant setup that depended on it. The conversion of Alert and Provider from v1beta3 to v1 drops several deprecated fields, so remove them from your manifests first. The release also retires the ObjectLevelWorkloadIdentity feature gate because object identity is generally available, adds SPIFFE mTLS for inter-controller communication, and adds update batching to ImageUpdateAutomation through .spec.policyChangeDelay. The multi-tenancy flag --default-service-account on the source-watcher controller needs v2.10.0 or later, and earlier versions fail with an unknown flag error. A safe routine is to upgrade a test cluster first, run flux check, then watch flux get all -A until everything is Ready before touching production.
Also read the ImageUpdateAutomation notes in the release: update batching delays commits while several policies change, retries cover rejected pushes, and the Flux artifact storage backend is now on by default for ImageRepository tags. Test these on a staging repository before you let automation push to a production branch.
Where to go next
Use the FluxCD interview preparation guide for a study plan and 70+ FluxCD interview questions for volume practice. GitOps labs are part of the DevOps course in Pune.
Frequently asked questions
What is the current Flux version?
Flux v2.10.0 is the latest release on the Flux GitHub releases page as of this review.
Can Flux deploy Helm charts from OCI?
Yes. HelmRelease can use an OCIRepository as the chart source, and Flux v2.10.0 highlights this.
What is the minimum Kustomization interval?
60 seconds.
Does Flux support secret decryption?
Yes, with SOPS. It is the only provider the Kustomization decryption field accepts.
Do I need a Git repository?
No. Sources can also be OCI artifacts, Helm repositories or buckets. Git is the most common.
Is a failed HelmRelease rolled back?
The default upgrade remediation strategy is rollback, but retries default to 0, so set retries to enable remediation.
How do tenants stay isolated?
Use serviceAccountName impersonation and the lockdown flags for cross-namespace references, remote bases and default service accounts.
How do I check controller health?
Run flux check, which verifies controller readiness and versions.
Official references
What's Your Reaction?
Like
0
Dislike
0
Love
0
Funny
0
Angry
0
Sad
0
Wow
0