A Terraform provider for installing and managing Helm charts in Kubernetes clusters using infrastructure-as-code.
Terraform Provider for Helm is an official HashiCorp provider that enables infrastructure-as-code management of Helm charts in Kubernetes clusters. It allows developers to define Helm releases as Terraform resources, integrating application deployment with infrastructure management in a single declarative workflow. This solves the problem of managing Kubernetes applications separately from other infrastructure components.
DevOps engineers, platform teams, and infrastructure developers who manage Kubernetes clusters with Terraform and want to incorporate Helm chart deployments into their infrastructure-as-code pipelines.
Developers choose this provider to maintain a single source of truth for both infrastructure and application deployments, leveraging Terraform's state management, plan/apply workflow, and dependency resolution for Helm releases. It eliminates the need for separate Helm deployment scripts and ensures consistent, reproducible deployments.
Terraform Helm provider
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Integrates Helm chart management into Terraform plans, enabling coordinated deployment of applications and infrastructure in a single apply, as highlighted in the README's example of managing releases alongside Kubernetes configs.
Tracks Helm release state and configuration drift through Terraform's state system, ensuring consistency and reproducibility across environments without separate tracking tools.
Automatically handles dependencies between Helm releases and other Terraform resources, such as waiting for a Kubernetes cluster to be provisioned before installing charts, leveraging Terraform's built-in resolution.
Uses Terraform variables, outputs, and modules to parameterize Helm chart values, as shown in the README with 'set' blocks, enabling version-controlled and reusable deployment configurations.
Requires expertise in both Terraform and Helm, adding layers to the deployment stack that can steepen the learning curve and introduce more failure points, especially for teams new to IaC.
Ties application deployments to Terraform's lifecycle and state management, limiting flexibility for teams using other tools or needing to manage Helm outside of Terraform's workflow.
May not support all advanced Helm features or chart repositories natively, as hinted in the README's need for specific OCI registry configurations, potentially requiring workarounds.
Requires maintaining and securing Terraform state files for Helm releases, adding operational overhead compared to stateless Helm deployments or simpler CI/CD pipelines.