WordPress Helm chart deployed using Helm Release resource

This example lives in the pulumi/examples repository. Check out just this directory to use it:

$ git clone --filter=blob:none --sparse https://github.com/pulumi/examples pulumi-examples
$ git -C pulumi-examples sparse-checkout set kubernetes-ts-helm-release-wordpress
$ cd pulumi-examples/kubernetes-ts-helm-release-wordpress

Uses the Helm Release API of @pulumi/kubernetes to deploy v13.0.6 of the WordPress Helm chart to a Kubernetes cluster. The Helm Release resource will install the chart, mimicking the behavior of the Helm CLI.

Prerequisites#

1. Install Pulumi
2. Configure Kubernetes
3. Install Node.js

Deploying the example#

1. Create a new stack:

   pulumi stack init dev

2. Install dependencies:

   npm install

3. Deploy the stack:

   pulumi up

   Updating (dev)
   
        Type                              Name                           Status
    +   pulumi:pulumi:Stack               ts-helm-release-wordpress-dev  created
    +   └─ kubernetes:helm.sh/v3:Release  wpdev                          created
        └─ kubernetes:core/v1:Service     wpdev-wordpress
   
   Outputs:
       frontendIp: "10.96.206.152"
       portForwardCommand: "kubectl port-forward svc/wpdev-vaj5az35-wordpress 8080:80"
   
   Resources:
       + 2 created
   
   Duration: 1m9s

4. We can see in the Outputs: section that WordPress was allocated a cluster IP, in this case 10.96.206.152. It is exported with a stack output variable, frontendIp. Since this is a cluster IP, you will need to port-forward to the service in order to hit the endpoint at http://localhost:8080 by running the port-forward command specified in portForwardCommand. You can then navigate to the site in a web browser.

Cleaning up#

Once you’re finished experimenting, you can destroy your stack and remove it to avoid incurring any additional cost:

pulumi destroy
pulumi stack rm