Wordpress Helm Chart in Go

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-wordpress
$ cd pulumi-examples/kubernetes-go-helm-wordpress

Uses the Helm API of pulumi-kubernetes to deploy v9.6.0 of the Wordpress Helm Chart to a Kubernetes cluster. Pulumi will expand the Helm Chart and submit the expanded YAML to the cluster.

Running the App#

If you haven’t already, follow the steps in Pulumi Installation and Setup and Configuring Pulumi Kubernetes to get set up with Pulumi and Kubernetes.

Now, install dependencies:

go mod download

Create a new stack:

$ pulumi stack init
Enter a stack name: wordpress-dev

Preview the deployment of the application and the perform the deployment:

pulumi up
Previewing update (wordpress-dev)

View Live: https://app.pulumi.com/...

     Type                                            Name                                        Plan
 +   pulumi:pulumi:Stack                             kubernetes-go-helm-wordpress-wordpress-dev  create
 +   └─ kubernetes:helm.sh/v2:Chart                  wpdev                                       create
 +      ├─ kubernetes:core/v1:PersistentVolumeClaim  wpdev-wordpress                             create
 +      ├─ kubernetes:core/v1:Secret                 wpdev-wordpress                             create
 +      ├─ kubernetes:core/v1:Service                wpdev-wordpress                             create
 +      ├─ kubernetes:core/v1:ConfigMap              default/wpdev-mariadb                       create
 +      ├─ kubernetes:core/v1:Secret                 default/wpdev-mariadb                       create
 +      ├─ kubernetes:core/v1:Pod                    wpdev-credentials-test                      create
 +      ├─ kubernetes:core/v1:Service                default/wpdev-mariadb                       create
 +      ├─ kubernetes:apps/v1:Deployment             wpdev-wordpress                             create
 +      └─ kubernetes:apps/v1:StatefulSet            default/wpdev-mariadb                       create

Resources:
    + 11 to create

Do you want to perform this update? yes
Updating (wordpress-dev)

View Live: https://app.pulumi.com/.../updates/7

     Type                                         Name                                        Status
 +   pulumi:pulumi:Stack                          kubernetes-go-helm-wordpress-wordpress-dev  created
 +   └─ kubernetes:helm.sh:Chart                  wpdev                                       created
 +      ├─ kubernetes:core:Secret                 default/wpdev-mariadb                       created
 +      ├─ kubernetes:core:Secret                 wpdev-wordpress                             created
 +      ├─ kubernetes:core:PersistentVolumeClaim  wpdev-wordpress                             created
 +      ├─ kubernetes:core:Service                wpdev-wordpress                             created
 +      ├─ kubernetes:core:ConfigMap              default/wpdev-mariadb                       created
 +      ├─ kubernetes:core:Service                default/wpdev-mariadb                       created
 +      ├─ kubernetes:apps:StatefulSet            default/wpdev-mariadb                       created
 +      └─ kubernetes:apps:Deployment             wpdev-wordpress                             created

Outputs:
    frontendIp: "35.193.210.254"

Resources:
    + 10 created

Duration: 53s

We can see here in the ---outputs:--- section that Wordpress was allocated a public IP, in this case 35.193.210.254. It is exported with a stack output variable, frontendIp. We can use curl and grep to retrieve the <title> of the site the proxy points at.

$ curl -sL $(pulumi stack output frontendIp):80 | grep "<title>"
<title>User&#039;s Blog! &#8211; Just another WordPress site</title>

You can also navigate to the site in a web browser.

When you’re done, you can remove these resources with pulumi destroy:

pulumi destroy --skip-preview
Destroying (wordpress-dev)

View Live: https://app.pulumi.com/example/.../updates/8

     Type                                         Name                                        Status
 -   pulumi:pulumi:Stack                          kubernetes-go-helm-wordpress-wordpress-dev  deleted
 -   └─ kubernetes:helm.sh:Chart                  wpdev                                       deleted
 -      ├─ kubernetes:core:Secret                 wpdev-wordpress                             deleted
 -      ├─ kubernetes:core:Secret                 default/wpdev-mariadb                       deleted
 -      ├─ kubernetes:core:ConfigMap              default/wpdev-mariadb                       deleted
 -      ├─ kubernetes:core:Service                default/wpdev-mariadb                       deleted
 -      ├─ kubernetes:core:PersistentVolumeClaim  wpdev-wordpress                             deleted
 -      ├─ kubernetes:core:Service                wpdev-wordpress                             deleted
 -      ├─ kubernetes:apps:StatefulSet            default/wpdev-mariadb                       deleted
 -      └─ kubernetes:apps:Deployment             wpdev-wordpress                             deleted

Outputs:
  - frontendIp: "35.193.210.254"

Resources:
    - 10 deleted

Duration: 7s

Wordpress Helm Chart

Running the App#

Related

Deleting Helm Chart Default Values

Helm Chart on Kubernetes

The infrastructure as code platform for any cloud.