Helm Release Resource Configuration¶
The helm_release resource in Terraform is used to deploy Helm charts into a Kubernetes cluster.^[400-devops__06-Kubernetes__devops-helm__terraform-helm__README.md] This resource allows for the programmatic configuration and lifecycle management of Helm releases.
Core Configuration¶
When defining a helm_release resource, the name and chart arguments are required to identify the release^[400-devops__06-Kubernetes__devops-helm__terraform-helm__README.md]. The repository argument specifies the URL of the Helm chart repository^[400-devops__06-Kubernetes__devops-helm__terraform-helm__README.md].
By default, the resource installs the chart into the default namespace, though this can be overridden^[400-devops__06-Kubernetes__devops-helm__terraform-helm__README.md]. The chart version is typically discovered automatically if not explicitly specified^[400-devops__06-Kubernetes__devops-helm__terraform-helm__README.md].
Customization via set Blocks¶
Configuration values within the chart can be overridden using set blocks^[400-devops__06-Kubernetes__devops-helm__terraform-helm__README.md]. These blocks take a name and a value to map specific configuration parameters.^[400-devops__06-Kubernetes__devops-helm__terraform-helm__README.md]
For example, to configure a service as a LoadBalancer on port 80 and set the replica count, the following set configurations would be applied^[400-devops__06-Kubernetes__devops-helm__terraform-helm__README.md]:
name = "service.type",value = "LoadBalancer"name = "service.externalPort",value = "80"name = "replicaCount",value = "2"
Deployment Behavior¶
The resource manages the deployment state, applying configurations according to the defined plan^[400-devops__06-Kubernetes__devops-helm__terraform-helm__README.md]. Upon creation, the resource generates an ID and provides a status indicating the state of the release^[400-devops__06-Kubernetes__devops-helm__terraform-helm__README.md].
Sources¶
^[400-devops__06-Kubernetes__devops-helm__terraform-helm__README.md]