fluxcd-helm-controller
This application acts as an automated assistant for your digital infrastructure.
Platform availability
Available on 0 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
77/100 Good
- Maintained
- 100last commit 4 days ago
- Popular
- 54515 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- 10064 MB minimum RAM
- Security check
- 95no serious findings, CI, tests, OpenSSF Scorecard 8.7/10
- GitHub stars
- 515
- Open issues
- 81
- Last commit
- 2026-11-17
- Latest release
- v1.7.1
- License
- Apache-2.0
- Activity
- declining
Checked 2 days ago - source: GitHub (fluxcd/helm-controller)
Resources & Compatibility
Minimum requirements: 64 MB RAM.
Checked 23 days ago - source: Docker Hub image tags and published docs
First-install notes
- Create a chart source and HelmRelease Create a chart source, such as a HelmRepository or OCIRepository, with the chart URL and version, then create a HelmRelease that points to it. Without a valid chart source, the controller has no app package to install. source
- Give installs enough time and retries Set install.timeout and install.remediation.retries on your HelmRelease so slow startup steps and temporary failures can finish instead of aborting. Without enough time or retries, a normal install may be marked failed. source
- Choose a clear chart version Choose a chart version, like 6.x or >= 6.0.0, in the chart source so you control which app release gets deployed. If the version is missing or wrong, the controller may install the wrong chart or fail to find one. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
What controller does fluxcd-helm-controller need to fetch charts?
It depends on source-controller to acquire Helm charts from Helm repositories.
Which Kubernetes resources do I create to deploy a Helm chart?
Create a chart source such as a HelmRepository or OCIRepository, then create a HelmRelease that points to it. Without a valid chart source, the controller has no package to install.
Why can a slow Helm install be marked as failed?
Set install.timeout and install.remediation.retries on the HelmRelease so slow startup steps and temporary failures can finish. Without enough time or retries, a normal install may be marked failed.
Can I recover a previous deployment state?
Changes are controlled through Git, and the Git history provides a sequence of transactions. This allows you to recover state from any snapshot.
How can I get more information when Flux controllers misbehave?
Use the Flux troubleshooting cheatsheet to get more information out of the Flux controllers and debug potential problems.
Answers sourced from fluxcd.io, fluxcd.io, github.com, github.com, github.com
Community
Collected 48 days ago - public community threads