fluxcd/helm-controller
Helm Controller
The project is a declarative GitOps controller and package manager designed to automate the deployment and lifecycle management of Helm charts within a cluster. It continuously watches custom resources and external artifact sources, comparing the actual cluster state against desired declarations to drive reconciliation. Artifacts and manifests are retrieved from standard package repositories, Git sources, OCI registries, and object storage buckets.
The system handles complex application delivery through dependency sequencing, automated failure remediation, and drift detection. It supports cross-resource dependency ordering, conditional rollbacks, automated testing, and uninstalls when execution errors occur. The workflow engine also watches referenced secrets and configuration maps for changes, initiating automated upgrades when configurations are modified, and supports multi-tenant isolation through scoped service accounts and role-based access control.
Additional capabilities include post-render manifest patching, custom health check evaluations, progressive delivery orchestration, and remote cluster resource management using static credentials or dynamic workload identity. The framework integrates notification engines and event-annotated metrics dashboards to broadcast deployment statuses and operational events to external endpoints.
Features
- Declarative Release Managers - Enables declarative deployment and management of Helm chart releases synchronized with external artifact sources.
- Continuous Delivery Engines - Manages the continuous deployment of applications and infrastructure to a cluster by synchronizing state directly from version control.
- Reconciliation Loops - Continuously watches custom resources and external artifacts, comparing cluster state against desired declarations to drive automated reconciliation.
- Package Dependency Managers - Coordinates package installations, upgrades, rollbacks, and dependency sequencing for containerized workloads in a cluster.
- Custom Resource Definition Lifecycles - Controls whether resource definitions install, skip, or replace during chart deployments to handle schema evolution.
- Custom Resource Definitions - Defines declarative cluster-level schemas that allow users to specify external artifact sources, release configurations, and lifecycle rules.
- Continuous Delivery Operators - Continually synchronizes remote application configurations and package definitions with a target cluster state.
- Helm Chart Management - Deploys and manages Helm chart releases declaratively in a cluster with automated upgrades, rollbacks, and release sequencing.
- Chart Repositories - Retrieves Helm charts from standard repositories, Git sources, OCI registries, and object storage buckets on a configured polling interval.
- Automated Release Upgrades - Watches referenced secrets and configuration maps for modifications and automatically initiates release upgrades when changes occur.
- Drift Detection - Identifies manual modifications made directly in the cluster and automatically reconciles them back to match declared states.
- Automated Release Remediation - Triggers conditional rollbacks, automated testing, uninstalls, and retries when installation or upgrade operations encounter execution errors.
- Encrypted Secret Management - Integrates with encryption tools to supply secure values to releases and trigger automated updates when secrets change.
- Multi-Tenancy Security - Isolates tenants using native role-based access control and impersonation across multiple source repositories and target clusters.
- Cluster Manifest Synchronizers - Continuously applies manifests from a remote repository to a cluster, automatically adding, updating, or removing resources.
- Global Chart Defaults - Overrides default chart configuration files with alternative internal files and optionally ignores missing files to prevent failures.
- Bucket Sources - Connects standard Git repositories, object storage buckets, and container registries to fetch manifests and artifacts.
- Release History - Maintains chronological records of previous release revisions and applied resource objects for auditing and troubleshooting.
- Cross-Resource Orchestrators - Orchestrates deployment ordering and verifies prerequisite readiness across multiple interdependent release resources before executing installations.
- Automated Image Updates - Scans container registries for new images and patches source repositories automatically when updates are discovered.
- Progressive Delivery Operators - Executes canary deployments, feature flags, and rollouts alongside standard application updates.
- GitOps Cluster Deployment - Deploys core management components to a cluster and links them to a remote repository for declarative synchronization.
- Post-Rendering Patches - Transforms generated chart templates using strategic merge, JSON patches, and image modifications before sending them to deployment engines.
- Release Dependency Management - Ensures a release proceeds only after referenced prerequisite resources or dependent releases reach a ready state.
- Multi-Cluster Deployment Managers - Applies and manages package releases on remote target clusters using secure static credentials or dynamic workload identity.
- Manifest Rendering - Applies custom patches, strategic merge transforms, and image updates to rendered chart manifests before deployment.
- Release Orchestrators - Manages complex application delivery lifecycles through declarative configurations, dependency ordering, and automated failure remediation.
- Pre-Deployment Chart Patching - Applies modifications directly to external deployment definitions during synchronization to adjust configurations without forking sources.
- Multi-Tenant - Isolates different users and tenants by executing operations using scoped service accounts and native role-based access control permissions.
- Release Sequence Definitions - Executes installation and upgrade tasks in a specific order by honoring explicit dependency relationships between defined releases.
- Out-of-Band Management - Compares deployed cluster states against desired release manifests using dry-runs to identify unexpected modifications.
