WordPress Helm chart deployed using the 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-go-helm-release-wordpress
$ cd pulumi-examples/kubernetes-go-helm-release-wordpress

Uses the Helm Release resource in pulumi-kubernetes to deploy v13.0.6 of the WordPress Helm chart to a Kubernetes cluster. Pulumi will use native Helm support to deploy the chart on the target Kubernetes cluster.

Prerequisites#

1. Install Pulumi
2. Configure Kubernetes
3. Install Go

Deploying the example#

1. Create a new stack:

   pulumi stack init dev

2. Install dependencies:

   go mod download

3. Deploy the stack:

   pulumi up

   Updating (dev)
   
   View Live: https://app.pulumi.com/.../kubernetes-go-helm-release-wordpress/dev/updates/11
   
        Type                              Name                                      Status
    +   pulumi:pulumi:Stack               kubernetes-go-helm-release-wordpress-dev  created
    +   ├─ kubernetes:helm.sh/v3:Release  wpdev                                     created
        └─ kubernetes:core/v1:Service     svc
   
   Outputs:
       frontendIp        : "10.96.109.99"
       portForwardCommand: "kubectl port-forward svc/wpdev-ysmr245n-wordpress 8080:80"
   
   Resources:
       + 2 created
   
   Duration: 1m13s

4. WordPress was allocated a cluster IP, in this case 10.96.109.99, exported as the stack output 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