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.
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:
npm installCreate a new stack:
$ pulumi stack init
Enter a stack name: wordpress-devPreview the deployment of the application and the perform the deployment:
pulumi up
Previewing update (ts-helm-wordpress)
View Live: https://app.pulumi.com/example/wordpress/ts-helm-wordpress/previews/cc683bd2-1e19-49c9-8a88-792c44e3b020
Type Name Plan
+ pulumi:pulumi:Stack wordpress-ts-helm-wordpress create
+ └─ kubernetes:helm.sh:Chart wpdev create
+ ├─ kubernetes:core:Secret default/wpdev-mariadb create
+ ├─ kubernetes:core:Secret wpdev-wordpress create
+ ├─ kubernetes:core:Service default/wpdev-mariadb create
+ ├─ kubernetes:core:Service wpdev-wordpress create
+ ├─ kubernetes:core:ConfigMap default/wpdev-mariadb create
+ ├─ kubernetes:core:PersistentVolumeClaim wpdev-wordpress create
+ ├─ kubernetes:apps:StatefulSet default/wpdev-mariadb create
+ └─ kubernetes:apps:Deployment wpdev-wordpress create
Resources:
+ 10 to create
Do you want to perform this update? yes
Updating (ts-helm-wordpress)
View Live: https://app.pulumi.com/example/wordpress/ts-helm-wordpress/updates/7
Type Name Status
+ pulumi:pulumi:Stack wordpress-ts-helm-wordpress 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:
wordpressIP: "35.193.210.254"
Resources:
+ 10 created
Duration: 53sWe 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's Blog! – 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 (ts-helm-wordpress)
View Live: https://app.pulumi.com/example/wordpress/ts-helm-wordpress/updates/8
Type Name Status
- pulumi:pulumi:Stack wordpress-ts-helm-wordpress 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:
- wordpressIP: "35.193.210.254"
Resources:
- 10 deleted
Duration: 7s