Docker & Kubernetes - Deploying WordPress and MariaDB with Ingress to Minikube using Helm Chart

bogotobogo.com site search:

Introduction

In this post, we'll deploy WordPress on Minikube using Helm. It also packages the Bitnami MariaDB chart which is required for bootstrapping a MariaDB deployment for the database requirements of the WordPress application.

This post is based on https://github.com/bitnami/charts/tree/master/bitnami/wordpress.

The file structure looks like this:

.
├── Chart.lock
├── Chart.yaml
├── README.md
├── ci
│   ├── ct-values.yaml
│   ├── ingress-wildcard-values.yaml
│   ├── values-hpa-pdb.yaml
│   └── values-metrics-and-ingress.yaml
├── templates
│   ├── NOTES.txt
│   ├── _helpers.tpl
│   ├── configmap.yaml
│   ├── deployment.yaml
│   ├── externaldb-secrets.yaml
│   ├── extra-list.yaml
│   ├── hpa.yaml
│   ├── ingress.yaml
│   ├── metrics-svc.yaml
│   ├── pdb.yaml
│   ├── pvc.yaml
│   ├── secrets.yaml
│   ├── servicemonitor.yaml
│   ├── svc.yaml
│   ├── tests
│   │   └── test-mariadb-connection.yaml
│   └── tls-secrets.yaml
├── values.schema.json
└── values.yaml

Minikube start:

$ minikube start --vm=true --cpus 2 --memory 2492
minikube v1.13.0 on Darwin 10.13.3
- KUBECONFIG=/Users/kihyuckhong/.kube/config
Automatically selected the docker driver. Other choices: hyperkit, virtualbox
Starting control plane node minikube in cluster minikube
Creating hyperkit VM (CPUs=2, Memory=2492MB, Disk=20000MB) ...
Preparing Kubernetes v1.19.0 on Docker 19.03.8 ...
Verifying Kubernetes components...
Enabled addons: default-storageclass, storage-provisioner
Done! kubectl is now configured to use "minikube" by default

For Helm 2, tiller should be installed on the Minikube:

$ helm init
$HELM_HOME has been configured at /Users/kihyuckhong/.helm.

Tiller (the Helm server-side component) has been installed into your Kubernetes Cluster.

...

Given the stable deprecation timeline, the Bitnami maintained WordPress Helm chart is now located at bitnami/charts.

The Bitnami repository can be added using helm repo add:

$ helm repo add bitnami https://charts.bitnami.com/bitnami

$ helm repo list
NAME   	URL                               
bitnami	https://charts.bitnami.com/bitnami
stable 	https://charts.helm.sh/stable

To deploy the WordPress chart, we can use either one of the following depending on the Helm version:

$ helm install my-release bitnami/<chart>           # Helm 3
$ helm install --name my-release bitnami/<chart>    # Helm 2

Ref: bitnami / charts

In this post, we'll use Heml 3, so issue the following command from ~/charts/bitnami/wordpress directory:

$ helm install my-release \
  --set wordpressUsername=admin \
  --set wordpressPassword=password \
  --set mariadb.auth.rootPassword=secretpassword \
    bitnami/wordpress
NAME: my-release
LAST DEPLOYED: Wed Mar 17 16:42:40 2021
NAMESPACE: default
STATUS: deployed
REVISION: 1
NOTES:    
** Please be patient while the chart is being deployed **

Your WordPress site can be accessed through the following DNS name from within your cluster:

    my-release-wordpress.default.svc.cluster.local (port 80)

To access your WordPress site from outside the cluster follow the steps below:

1. Get the WordPress URL by running these commands:

  NOTE: It may take a few minutes for the LoadBalancer IP to be available.
        Watch the status with: 'kubectl get svc --namespace default -w my-release-wordpress'

   export SERVICE_IP=$(kubectl get svc --namespace default my-release-wordpress --template "{{ range (index .status.loadBalancer.ingress 0) }}{{.}}{{ end }}")
   echo "WordPress URL: http://$SERVICE_IP/"
   echo "WordPress Admin URL: http://$SERVICE_IP/admin"

2. Open a browser and access WordPress using the obtained URL.

3. Login with the following credentials below to see your blog:

  echo Username: admin
  echo Password: $(kubectl get secret --namespace default my-release-wordpress -o jsonpath="{.data.wordpress-password}" | base64 --decode)

Not used here but if we want to use just the default parameters defined in ./values.yaml, the command should look like this:

$ helm install wordpress bitnami/wordpress -f ./values.yaml

where the values.yaml is available from https://github.com/helm/charts/blob/master/stable/wordpress/values.yaml.

Wait for couple of minutes and then check the following:

$ kubectl get pods
NAME                         READY   STATUS    RESTARTS   AGE
my-release-mariadb-0                    1/1     Running   0          5m42s
my-release-wordpress-76d8bb6c6c-jz2xj   1/1     Running   1          5m42s

$ kubectl get svc
NAME                   TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)
kubernetes             ClusterIP      10.96.0.1       <none>        443/TCP                      10m
my-release-mariadb     ClusterIP      10.110.165.71   <none>        3306/TCP                     6m5s
my-release-wordpress   LoadBalancer   10.99.101.249   <pending>     80:32233/TCP,443:30204/TCP   6m5s

$ kubectl get deployment
NAME                   READY   UP-TO-DATE   AVAILABLE   AGE
my-release-wordpress   1/1     1            1           6m52s

$ kubectl get pv
NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                               STORAGECLASS   REASON   AGE
pvc-29cce85e-7beb-443b-84f8-ecfef87121a0   10Gi       RWO            Delete           Bound    default/my-release-wordpress        standard                8m53s
pvc-f9545501-2cc9-419d-9184-fba15c194d3f   8Gi        RWO            Delete           Bound    default/data-my-release-mariadb-0   standard                8m52s

$ kubectl get pvc
NAME                        STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
data-my-release-mariadb-0   Bound    pvc-f9545501-2cc9-419d-9184-fba15c194d3f   8Gi        RWO            standard       8m33s
my-release-wordpress        Bound    pvc-29cce85e-7beb-443b-84f8-ecfef87121a0   10Gi       RWO            standard       8m34s

$ kubectl get configmap
NAME                 DATA   AGE
my-release-mariadb   1      9m23s

$ kubectl get secrets
NAME                               TYPE                                  DATA   AGE
default-token-bqx9f                kubernetes.io/service-account-token   3      14m
my-release-mariadb                 Opaque                                2      9m43s
my-release-mariadb-token-vvlgt     kubernetes.io/service-account-token   3      9m43s
my-release-wordpress               Opaque                                1      9m43s
sh.helm.release.v1.my-release.v1   helm.sh/release.v1                    1      9m43s

$ kubectl get statefulsets
NAME                 READY   AGE
my-release-mariadb   1/1     10m

$ kubectl get pods --all-namespaces
NAMESPACE     NAME                                    READY   STATUS    RESTARTS   AGE
default       my-release-mariadb-0                    1/1     Running   0          10m
default       my-release-wordpress-76d8bb6c6c-jz2xj   1/1     Running   1          10m
kube-system   coredns-f9fd979d6-4wgt6                 1/1     Running   0          14m
kube-system   etcd-minikube                           1/1     Running   0          14m
kube-system   kube-apiserver-minikube                 1/1     Running   0          14m
kube-system   kube-controller-manager-minikube        1/1     Running   0          14m
kube-system   kube-proxy-wv878                        1/1     Running   0          14m
kube-system   kube-scheduler-minikube                 1/1     Running   0          14m
kube-system   storage-provisioner                     1/1     Running   0          14m

$ helm list
NAME      	NAMESPACE	REVISION	UPDATED                             	STATUS  	CHART            	APP VERSION
my-release	default  	1       	2021-03-17 16:52:39.698742 -0700 PDT	deployed	wordpress-10.6.13	5.7.0

$ kubectl exec -it my-release-mariadb-0 -- dash

$ ps aux
USER         PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
1001           1  0.5  3.3 1474720 84700 ?       Ssl  Mar17   0:03 /opt/bitnami/mariadb/sbin/mysqld --defaul
1001         733  0.0  0.0   2388   764 pts/0    Ss   00:03   0:00 dash
1001         784  0.0  0.1   7640  2712 pts/0    R+   00:04   0:00 ps aux

$ mysql -u root -p
Enter password: 
Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MariaDB connection id is 213
Server version: 10.5.9-MariaDB Source distribution

Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MariaDB [(none)]> show databases;
+--------------------+
| Database           |
+--------------------+
| bitnami_wordpress  |
| information_schema |
| mysql              |
| performance_schema |
| test               |
+--------------------+
5 rows in set (0.012 sec)

MariaDB [(none)]> use bitnami_wordpress;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
MariaDB [bitnami_wordpress]> show tables;
+-----------------------------+
| Tables_in_bitnami_wordpress |
+-----------------------------+
| wp_commentmeta              |
| wp_comments                 |
| wp_links                    |
| wp_options                  |
| wp_postmeta                 |
| wp_posts                    |
| wp_term_relationships       |
| wp_term_taxonomy            |
| wp_termmeta                 |
| wp_terms                    |
| wp_usermeta                 |
| wp_users                    |
+-----------------------------+
12 rows in set (0.001 sec)

MariaDB [bitnami_wordpress]>

$ minikube service my-release-wordpress --url
Starting tunnel for service my-release-wordpress.
|-----------|----------------------|-------------|------------------------|
| NAMESPACE |         NAME         | TARGET PORT |          URL           |
|-----------|----------------------|-------------|------------------------|
| default   | my-release-wordpress |             | http://127.0.0.1:52812 |
|           |                      |             | http://127.0.0.1:52813 |
|-----------|----------------------|-------------|------------------------|
http://127.0.0.1:52812
http://127.0.0.1:52813
ecause you are using a Docker driver on darwin, the terminal needs to be open to run it.

Enable Ingress

In the previous section, we were connecting to our API on ephemeral port. However, it's not desired and we should be able to connect to our API on port 80.

We'll use an ingress resource to manage external access. An ingress resource defines rules that allow inbound connections to access the services within the cluster. Those rules require an ingress controller to be running inside the cluster.

Minikube, by default, uses the ingress-nginx controller which is the one we're going to use. Since it's Minikube's default, we could use it implicitly by enabling the ingress addon:

$ kubectl get pod -n kube-system
NAME                               READY   STATUS    RESTARTS   AGE
coredns-f9fd979d6-9vd7z            1/1     Running   0          7m56s
etcd-minikube                      1/1     Running   0          7m49s
kube-apiserver-minikube            1/1     Running   0          7m49s
kube-controller-manager-minikube   1/1     Running   0          7m49s
kube-proxy-m8wrd                   1/1     Running   0          7m56s
kube-scheduler-minikube            1/1     Running   0          7m49s
storage-provisioner                1/1     Running   1          7m54s

$ minikube addons enable ingress
Verifying ingress addon...
The 'ingress' addon is enabled

$ kubectl get pod -n kube-system
NAME                                       READY   STATUS      RESTARTS   AGE
coredns-f9fd979d6-9vd7z                    1/1     Running     0          10m
etcd-minikube                              1/1     Running     0          10m
ingress-nginx-admission-create-vhz42       0/1     Completed   0          106s
ingress-nginx-admission-patch-p89cc        0/1     Completed   0          106s
ingress-nginx-controller-789d9c4dc-wrpth   1/1     Running     0          106s
kube-apiserver-minikube                    1/1     Running     0          10m
kube-controller-manager-minikube           1/1     Running     0          10m
kube-proxy-m8wrd                           1/1     Running     0          10m
kube-scheduler-minikube                    1/1     Running     0          10m
storage-provisioner                        1/1     Running     1          10m

We'll install additional ingress controller as a dependency so that when we later deploy to a cloud provider we can rest assured that the same controller will be used in all our environments.

~/charts/bitnami/wordpress/charts.yaml (note that dependency information was transferred from the requirements.yaml to the Chart.yaml file, v2->v3):

annotations:
  category: CMS
apiVersion: v2
appVersion: 5.7.0
dependencies:
  - condition: mariadb.enabled
    name: mariadb
    repository: https://charts.bitnami.com/bitnami
    version: 9.x.x
  - name: nginx-ingress
    repository: https://helm.nginx.com/stable
    version: 0.8.0
  - name: common
    repository: https://charts.bitnami.com/bitnami
    tags:
      - bitnami-common
    version: 1.x.x
...

Once we have defined dependencies, we can run helm dependency update and it will use our dependency file to download all the specified charts into our charts/ directory for us:

$ helm dependency update
Getting updates for unmanaged Helm repositories...
...Successfully got an update from the "https://helm.nginx.com/stable" chart repository
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "bitnami" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete. ⎈Happy Helming!⎈
Saving 3 charts
Downloading mariadb from repo https://charts.bitnami.com/bitnami
Downloading nginx-ingress from repo https://helm.nginx.com/stable
Downloading common from repo https://charts.bitnami.com/bitnami
Deleting outdated charts

When helm dependency update retrieves charts, it will store them as chart archives in the charts/ directory. So in our case, one would expect to see the following files in the charts directory:

~/charts/bitnami/wordpress $ tree
.
├── Chart.lock
├── Chart.yaml
├── Chart.yaml.SAVED
├── README.md
├── charts
│   ├── common-1.4.1.tgz
│   ├── mariadb-9.3.5.tgz
│   └── nginx-ingress-0.8.0.tgz
├── ci
│   ├── ct-values.yaml
│   ├── ingress-wildcard-values.yaml
│   ├── values-hpa-pdb.yaml
│   └── values-metrics-and-ingress.yaml
├── templates
│   ├── NOTES.txt
│   ├── _helpers.tpl
│   ├── configmap.yaml
│   ├── deployment.yaml
│   ├── externaldb-secrets.yaml
│   ├── extra-list.yaml
│   ├── hpa.yaml
│   ├── ingress.yaml
│   ├── metrics-svc.yaml
│   ├── pdb.yaml
│   ├── pvc.yaml
│   ├── secrets.yaml
│   ├── servicemonitor.yaml
│   ├── svc.yaml
│   ├── tests
│   │   └── test-mariadb-connection.yaml
│   └── tls-secrets.yaml
├── values.schema.json
└── values.yaml

Now we need to define ingress rules specifying where to route incoming traffic. Our routing rules are simple — route all HTTP traffic to our wordpress service. Note that the nginx-ingress controller provides capabilities such as routing traffic to different services based on path (layer-7 routing), adding sticky sessions, doing TLS termination, etc.

values.yaml:

...
ingress:
  ## Set to true to enable ingress record generation
  ##
  enabled: true

  ## Set this to true in order to add the corresponding annotations for cert-manager
  ##
  certManager: false

  ## When the ingress is enabled, a host pointing to this will be created
  ##
  hostname: wordpress.local
 ...

Updating the chart for Ingress

We may want to update the chart using helm upgrade command.

$ helm ls
NAME      	NAMESPACE	REVISION	UPDATED                            	STATUS  	CHART            	APP VERSION
my-release	default  	1       	2021-03-17 17:57:59.11862 -0700 PDT	deployed	wordpress-10.6.13	5.7.0 

$ helm upgrade \
  --set wordpressUsername=admin \
  --set wordpressPassword=password \
  --set mariadb.auth.rootPassword=secretpassword \
  --set mariadb.auth.password=secretpassword \
  my-release ./  
W0317 22:31:01.745835   52531 warnings.go:70] networking.k8s.io/v1beta1 IngressClass is deprecated in v1.19+, unavailable in v1.22+; use networking.k8s.io/v1 IngressClassList
W0317 22:31:04.680630   52531 warnings.go:70] networking.k8s.io/v1beta1 IngressClass is deprecated in v1.19+, unavailable in v1.22+; use networking.k8s.io/v1 IngressClassList
W0317 22:31:04.694483   52531 warnings.go:70] networking.k8s.io/v1beta1 IngressClass is deprecated in v1.19+, unavailable in v1.22+; use networking.k8s.io/v1 IngressClassList
Release "my-release" has been upgraded. Happy Helming!
NAME: my-release
LAST DEPLOYED: Wed Mar 17 22:31:01 2021
NAMESPACE: default
STATUS: deployed
REVISION: 2
NOTES:
** Please be patient while the chart is being deployed **

Your WordPress site can be accessed through the following DNS name from within your cluster:

    my-release-wordpress.default.svc.cluster.local (port 80)

To access your WordPress site from outside the cluster follow the steps below:

1. Get the WordPress URL and associate WordPress hostname to your cluster external IP:

   export CLUSTER_IP=$(minikube ip) # On Minikube. Use: `kubectl cluster-info` on others K8s clusters
   echo "WordPress URL: http://wordpress.local/"
   echo "$CLUSTER_IP  wordpress.local" | sudo tee -a /etc/hosts

2. Open a browser and access WordPress using the obtained URL.

3. Login with the following credentials below to see your blog:

  echo Username: admin
  echo Password: $(kubectl get secret --namespace default my-release-wordpress -o jsonpath="{.data.wordpress-password}" | base64 --decode)

Following the steps from the output:

$ helm get values my-release
USER-SUPPLIED VALUES:
mariadb:
  auth:
    password: secretpassword
    rootPassword: secretpassword
wordpressPassword: password
wordpressUsername: admin    
    
$ kubectl cluster-info
Kubernetes master is running at https://192.168.64.12:8443
KubeDNS is running at https://192.168.64.12:8443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.   

$ echo "192.168.64.12 wordpress.local" | sudo tee -a /etc/hosts
Password:
192.168.64.12 wordpress.local

$ cat /etc/hosts
...
192.168.64.12 wordpress.local
...

The source codes are available from "ingress" branch: https://github.com/Einsteinish/Helm-Chart-for-Wordpress-and-MariaDB.git.

Uninstall chart

To uninstall/delete the my-release deployment:

$ helm uninstall my-release
W0317 23:05:15.806918   52851 warnings.go:70] networking.k8s.io/v1beta1 IngressClass is deprecated in v1.19+, unavailable in v1.22+; use networking.k8s.io/v1 IngressClassList
release "my-release" uninstalled

$ helm ls
NAME	NAMESPACE	REVISION	UPDATED	STATUS	CHART	APP VERSION