charts/wordpress

Wordpress

WordPress is one of the most versatile open source content management systems on the market. A publishing platform for building blogs and websites.

TL;DR;

$ helm install wordpress-x.x.x.tgz

Introduction

Bitnami charts for Helm are carefully engineered, actively maintained and are the quickest and easiest way to deploy containers on a Kubernetes cluster that are ready to handle production workloads.

This chart bootstraps a Wordpress deployment on a Kubernetes cluster using the Helm package manager.

It also packages the Bitnami MariaDB chart which is required for bootstrapping a MariaDB deployment for the database requirements of the Wordpress application.

Get this chart

Download the latest release of the chart from the releases page.

Alternatively, clone the repo if you wish to use the development snapshot:

$ git clone https://github.com/bitnami/charts.git

Installing the Chart

To install the chart with the release name my-release:

$ helm install --name my-release wordpress-x.x.x.tgz

Replace the x.x.x placeholder with the chart release version.

The command deploys Wordpress on the Kubernetes cluster in the default configuration. The configuration section lists the parameters that can be configured during installation.

Tip

: List all releases using helm list

Uninstalling the Chart

To uninstall/delete the my-release deployment:

$ helm delete my-release

The command removes all the Kubernetes components associated with the chart and deletes the release.

Configuration

The following tables lists the configurable parameters of the Wordpress chart and their default values.

Parameter	Description	Default
imageTag	bitnami/wordpress image tag	Wordpress image version
imagePullPolicy	Image pull policy	Always if imageTag is latest, else IfNotPresent.
wordpressUsername	User of the application	user
wordpressPassword	Application password	bitnami
wordpressEmail	Admin email	user@example.com
wordpressFirstName	First name	FirstName
wordpressLastName	Last name	LastName
wordpressBlogName	Blog name	User's Blog!
smtpHost	SMTP host	nil
smtpPort	SMTP port	nil
smtpUser	SMTP user	nil
smtpPassword	SMTP password	nil
smtpUsername	User name for SMTP emails	nil
smtpProtocol	SMTP protocol [tls, ssl]	nil
mariadb.mariadbRootPassword	MariaDB admin password	nil

The above parameters map to the env variables defined in bitnami/wordpress. For more information please refer to the bitnami/wordpress image documentation.

Specify each parameter using the --set key=value[,key=value] argument to helm install. For example,

$ helm install --name my-release \
  --set wordpressUsername=admin,wordpressPassword=password,mariadb.mariadbRootPassword=secretpassword \
    wordpress-x.x.x.tgz

The above command sets the Wordpress application username and password to admin and password respectively. Additionally it sets the MariaDB root user password to secretpassword.

Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,

$ helm install --name my-release -f values.yaml wordpress-x.x.x.tgz

Tip

: You can use the default values.yaml

Persistence

The Bitnami Wordpress image stores the Wordpress data and configurations at the /bitnami/wordpress path of the container.

As a placeholder, the chart mounts an emptyDir volume at this location.

"An emptyDir volume is first created when a Pod is assigned to a Node, and exists as long as that Pod is running on that node. When a Pod is removed from a node for any reason, the data in the emptyDir is deleted forever."

For persistence of the data you should replace the emptyDir volume with a persistent storage volume, else the data will be lost if the Pod is shutdown.

Step 1: Create a persistent disk

You first need to create a persistent disk in the cloud platform your cluster is running. For example, on GCE you can use the gcloud tool to create a gcePersistentDisk:

$ gcloud compute disks create --size=500GB --zone=us-central1-a wordpress-data-disk

Step 2: Update templates/deployment.yaml

Replace:

      volumes:
      - name: wordpress-data
        emptyDir: {}

with

      volumes:
      - name: wordpress-data
        gcePersistentDisk:
          pdName: wordpress-data-disk
          fsType: ext4

Note

:

You should also use a persistent storage volume for the MariaDB deployment.

Install the chart after making these changes.