MediaWiki is an extremely powerful, scalable software and a feature-rich wiki implementation that uses PHP to process and display data stored in a database, such as MySQL.

TL;DR;

$ helm install stable/mediawiki

Introduction

This chart bootstraps a MediaWiki 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 MediaWiki application.

Prerequisites

Kubernetes 1.4+ with Beta APIs enabled
PV provisioner support in the underlying infrastructure

Installing the Chart

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

$ helm install --name my-release stable/mediawiki

The command deploys MediaWiki 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 table lists the configurable parameters of the MediaWiki chart and their default values.

Parameter	Description	Default
`image.registry`	MediaWiki image registry	`docker.io`
`image.repository`	MediaWiki Image name	`bitnami/mediawiki`
`image.tag`	MediaWiki Image tag	`{VERSION}`
`image.pullPolicy`	Image pull policy	`Always`
`image.pullSecrets`	Specify image pull secrets	`nil`
`mediawikiUser`	User of the application	`user`
`mediawikiPassword`	Application password	random 10 character long alphanumeric string
`mediawikiEmail`	Admin email	`user@example.com`
`mediawikiName`	Name for the wiki	`My Wiki`
`allowEmptyPassword`	Allow DB blank passwords	`yes`
`smtpHost`	SMTP host	`nil`
`smtpPort`	SMTP port	`nil`
`smtpHostID`	SMTP host ID	`nil`
`smtpUser`	SMTP user	`nil`
`smtpPassword`	SMTP password	`nil`
`externalDatabase.host`	Host of the external database	`nil`
`externalDatabase.user`	Existing username in the external db	`bn_mediawiki`
`externalDatabase.password`	Password for the above username	`nil`
`externalDatabase.database`	Name of the existing database	`bitnami_mediawiki`
`mariadb.enabled`	Use or not the mariadb chart	`true`
`mariadb.rootUser.password`	MariaDB admin password	`nil`
`mariadb.db.name`	Database name to create	`bitnami_mediawiki`
`mariadb.db.user`	Database user to create	`bn_mediawiki`
`mariadb.db.password`	Password for the database	random 10 character long alphanumeric string
`service.type`	Kubernetes Service type	`LoadBalancer`
`service.loadBalancer`	Kubernetes LoadBalancerIP to request	`nil`
`service.externalTrafficPolicy`	Enable client source IP preservation	`Local`
`service.nodePorts.http`	Kubernetes http node port	`""`
`service.nodePorts.https`	Kubernetes https node port	`""`
`ingress.enabled`	Enable ingress controller resource	`false`
`ingress.hosts[0].name`	Hostname to your Mediawiki installation	`mediawiki.local`
`ingress.hosts[0].path`	Path within the url structure	`/`
`ingress.hosts[0].tls`	Utilize TLS backend in ingress	`false`
`ingress.hosts[0].tlsSecret`	TLS Secret (certificates)	`mediawiki.local-tls-secret`
`ingress.hosts[0].annotations`	Annotations for this host's ingress record	`[]`
`ingress.secrets[0].name`	TLS Secret Name	`nil`
`ingress.secrets[0].certificate`	TLS Secret Certificate	`nil`
`ingress.secrets[0].key`	TLS Secret Key	`nil`
`persistence.enabled`	Enable persistence using PVC	`true`
`persistence.apache.storageClass`	PVC Storage Class for Apache volume	`nil` (uses alpha storage class annotation)
`persistence.apache.accessMode`	PVC Access Mode for Apache volume	`ReadWriteOnce`
`persistence.apache.size`	PVC Storage Request for Apache volume	`1Gi`
`persistence.mediawiki.storageClass`	PVC Storage Class for MediaWiki volume	`nil` (uses alpha storage class annotation)
`persistence.mediawiki.accessMode`	PVC Access Mode for MediaWiki volume	`ReadWriteOnce`
`persistence.mediawiki.size`	PVC Storage Request for MediaWiki volume	`8Gi`
`resources`	CPU/Memory resource requests/limits	Memory: `512Mi`, CPU: `300m`
`livenessProbe.enabled`	Enable/disable the liveness probe (ingest nodes pod)	`true`
`livenessProbe.initialDelaySeconds`	Delay before liveness probe is initiated (ingest nodes pod)	120
`livenessProbe.periodSeconds`	How often to perform the probe (ingest nodes pod)	10
`livenessProbe.timeoutSeconds`	When the probe times out (ingest nodes pod)	5
`livenessProbe.failureThreshold`	Minimum consecutive failures to be considered failed	6
`livenessProbe.successThreshold`	Minimum consecutive successes to be considered successful	1
`readinessProbe.enabled`	would you like a readinessProbe to be enabled	`true`
`readinessProbe.initialDelaySeconds`	Delay before readinessProbe is initiated (ingest nodes pod)	30
`readinessProbe.periodSeconds`	How often to perform the probe (ingest nodes pod)	10
`readinessProbe.timeoutSeconds`	When the probe times out (ingest nodes pod)	5
`readinessProbe.failureThreshold`	Minimum consecutive failures to be considered failed	6
`readinessProbe.successThreshold`	Minimum consecutive successes to be considered successful	1

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

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

$ helm install --name my-release \
  --set mediawikiUser=admin,mediawikiPassword=password,mariadb.mariadbRootPassword=secretpassword \
    stable/mediawiki

The above command sets the MediaWiki administrator account 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 stable/mediawiki

Tip

: You can use the default values.yaml

Persistence

The Bitnami MediaWiki image stores the MediaWiki data and configurations at the /bitnami/mediawiki and /bitnami/apache paths of the container.

Persistent Volume Claims are used to keep the data across deployments. This is known to work in GCE, AWS, and minikube. See the Configuration section to configure the PVC or to disable persistence.