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

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

This chart has been designed and tested under a bare metal installation of Kubernetes. As far as I know there is an open issue about the way a service is exposed to the world in bare metal clusters. So this chart uses NodePort in Services and Ingress Controller for publishing services. More info here and here.

After the deployment you should be able to access the service through the hostname var setted on values.yaml. Update the DNS records before in order to point the Node IP where the ingress controller is running on.

• Kubernetes 1.4+ with Beta APIs enabled
• Ingress controller running. (Tested with Traefik)
• PV provisioner support in the underlying infrastructure
• MySQL Server running
• NFS Server running for persistence

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

$ git clone https://github.com/nordri/helm-wordpress
$ helm install --name my-release ./helm-wordpress

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

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.

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

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

$ helm install --name my-release \
  --set root_db_password=s3cr3t \
    helm-wordpress

The above command uses s3cr3t as MySQL root password.

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 helm-wordpress

This Chart uses NFS server for persistence. The exported volume is mounted under /var/www/html where Apache HTTPD server puts the web pages. You should use an export for each WP installation.