WordPress Helm chart deployed using the Helm Release resource
A minimal installation of the Wordpress Helm chart using Helm Release support
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-examplesgit -C pulumi-examples sparse-checkout set kubernetes-py-helm-release-wordpresscd pulumi-examples/kubernetes-py-helm-release-wordpressUses 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#
Deploying the example#
-
Create a new stack:
Terminal window pulumi stack init dev -
Install dependencies:
Terminal window python3 -m venv venvsource venv/bin/activatepip install -r requirements.txt -
Deploy the stack:
Terminal window pulumi upUpdating (dev)View Live: https://app.pulumi.com/.../kubernetes-py-helm-release-wordpress/dev/updates/1Type Name Status+ pulumi:pulumi:Stack kubernetes-py-helm-release-wordpress-dev created+ ├─ kubernetes:helm.sh/v3:Release wpdev created└─ kubernetes:core/v1:Service wpdev-wordpressOutputs:frontendIp : "10.96.144.123"portForwardCommand: "kubectl port-forward svc/wpdev-3zbpljcn-wordpress 8080:80"Resources:+ 2 createdDuration: 1m29s -
WordPress was allocated a cluster IP, in this case
10.96.144.123, exported as the stack outputfrontendIp. Since this is a cluster IP, you will need to port-forward to the service in order to hit the endpoint athttp://localhost:8080by running the port-forward command specified inportForwardCommand. 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 destroypulumi stack rm