---
title: "Wordpress Helm Chart Deployed Using Helm Release Resource"
description: "A minimal installation of the Wordpress Helm chart using Helm Release support"
url: "https://www.pulumi.com/dev/examples/kubernetes-cs-helm-release-wordpress/"
image: "https://www.pulumi.com/assets/og/dev/examples/kubernetes-cs-helm-release-wordpress.png"
---

# Wordpress Helm Chart Deployed Using Helm Release Resource

A minimal installation of the Wordpress Helm chart using Helm Release support

- Source on GitHub: https://github.com/pulumi/examples/tree/master/kubernetes-cs-helm-release-wordpress

## Get started with this example

This example lives in the [pulumi/examples](https://github.com/pulumi/examples/tree/master/kubernetes-cs-helm-release-wordpress) repo. Pull down just this directory to follow along:

```bash
git clone --filter=blob:none --sparse https://github.com/pulumi/examples pulumi-examples
git -C pulumi-examples sparse-checkout set kubernetes-cs-helm-release-wordpress
cd pulumi-examples/kubernetes-cs-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 mimicing behavior of the Helm CLI.

![wordpress](./images/deploy.gif "Wordpress Helm Release deployment")

## Running the App

If you haven't already, follow the steps in [Pulumi Installation and
Setup](https://www.pulumi.com/docs/get-started/install/) and [Configuring Pulumi
Kubernetes](https://www.pulumi.com/docs/intro/cloud-providers/kubernetes/setup/) to get set up with
Pulumi and Kubernetes.

Create a new stack:

```sh
$ pulumi stack init
Enter a stack name: dev
```

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

```sh
pulumi up
Previewing update (dev)

View Live: https://app.pulumi.com/.../kubernetes-cs-helm-release-wordpress/dev/previews/aa6d614e-d4b9-4abf-9a21-4c2c353fca3f

     Type                              Name                                      Plan
 +   pulumi:pulumi:Stack               kubernetes-cs-helm-release-wordpress-dev  create
 +   ├─ kubernetes:helm.sh/v3:Release  wpdev                                     create
 +   └─ kubernetes:core/v1:Service     wpdev-wordpress                           create

Resources:
    + 3 to create

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

View Live: https://app.pulumi.com/.../kubernetes-cs-helm-release-wordpress/dev/updates/4

     Type                              Name                                      Status
 +   pulumi:pulumi:Stack               kubernetes-cs-helm-release-wordpress-dev  created
 +   ├─ kubernetes:helm.sh/v3:Release  wpdev                                     created
     └─ kubernetes:core/v1:Service     wpdev-wordpress

Outputs:
    FrontendIP        : "10.96.224.4"
    PortForwardCommand: "kubectl port-forward svc/wpdev-277o20tl-wordpress 8080:80"

Resources:
    + 2 created

Duration: 1m18s
```

We can see here in the `---outputs:---` section that Wordpress was allocated a Cluster IP, in this
case `10.96.224.4`. 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 navigate to the site in a web browser.

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

```sh
pulumi destroy --skip-preview
Destroying (dev)

View Live: https://app.pulumi.com/.../kubernetes-cs-helm-release-wordpress/dev/updates/5

     Type                              Name                                      Status
 -   pulumi:pulumi:Stack               kubernetes-cs-helm-release-wordpress-dev  deleted
 -   └─ kubernetes:helm.sh/v3:Release  wpdev                                     deleted

Outputs:
  - FrontendIP        : "10.96.224.4"
  - PortForwardCommand: "kubectl port-forward svc/wpdev-277o20tl-wordpress 8080:80"

Resources:
    - 2 deleted

Duration: 16s

The resources in the stack have been deleted, but the history and configuration associated with the stack are still maintained.
If you want to remove the stack completely, run 'pulumi stack rm dev'.
```