Helm Chart on Kubernetes
The Helm Chart template creates an infrastructure as code project in your favorite language that deploys a Helm chart to an existing cluster using Pulumi. It uses Pulumi’s Native Kubernetes Provider to create a new namespace in an existing Kubernetes cluster and a new Helm chart that deploys an application (in this case, the Nginx ingress controller). The template generates a complete infrastructure as code program, including sample application code, to give you a working project out of the box that you can customize easily and extend to suit your needs.
Using this template
To use this template to deploy a Helm chart to a Kubernetes cluster, make sure you’ve already provisioned a Kubernetes cluster, installed Pulumi and
kubectl, and configured your kubeconfig file. Then create a new project using the template in your language of choice:
$ mkdir my-k8s-app && cd my-k8s-app $ pulumi new helm-kubernetes-typescript
$ mkdir my-k8s-app && cd my-k8s-app $ pulumi new helm-kubernetes-python
$ mkdir my-k8s-app && cd my-k8s-app $ pulumi new helm-kubernetes-go
$ mkdir my-k8s-app && cd my-k8s-app $ pulumi new helm-kubernetes-csharp
$ mkdir my-k8s-app && cd my-k8s-app $ pulumi new helm-kubernetes-yaml
Follow the prompts to complete the new-project wizard. When it’s done, you’ll have a complete Pulumi project that’s ready to deploy and configured with the most common settings. Feel free to inspect the code in
Deploying the project
The template requires no additional configuration. By default, it will install an Nginx ingress controller with Helm. Once the new project is created, you can deploy it immediately with
$ pulumi up
When the deployment completes, Pulumi exports the following stack output values:
- The name of your new Helm chart deployment.
Output values like these are useful in many ways, most commonly as inputs for other stacks or related cloud resources.
Customizing the project
Projects created with the Helm Chart template expose the following configuration settings:
- The name of the namespace to be created in your existing cluster. Defaults to
All of these settings are optional and may be adjusted either by editing the stack configuration file directly (by default,
Pulumi.dev.yaml) or by changing their values with
pulumi config set as shown below.
$ pulumi config set someProp ../some/value $ pulumi up
You can customize the Helm chart by passing values to it in your Pulumi code. An example of passing a few values to the Helm chart is already included in the template for easy reference.
You can cleanly destroy the stack and all of its infrastructure with
$ pulumi destroy
Congratulations! You’re now well on your way to managing a production-grade Kubernetes application with Pulumi — and there’s lots more you can do from here:
- Discover more architecture templates in Templates →
- Dive into the Kubernetes package by exploring the API docs in the Registry →
- Expand your understanding of how Pulumi works in Learn Pulumi →
- Read up on the latest new features in the Pulumi Blog →