Docker & Kubernetes: WordPress and MySQL with PV and Kustumization on Minikube

bogotobogo.com site search:

Introduction

This post is based on Deploying WordPress and MySQL with Persistent Volumes.

We need the following three yaml files (kustomization.yaml, mysql-deployment.yaml, and wordpress-deployment.yaml):

.
├── kustomization.yaml
├── mysql-deployment.yaml
└── wordpress-deployment.yaml

kustomization.yaml:

secretGenerator:
- name: mysql-pass
  literals:
  - password=Passw0rd
resources:
  - mysql-deployment.yaml
  - wordpress-deployment.yaml

mysql-deployment.yaml:

apiVersion: v1
kind: Service
metadata:
  name: wordpress-mysql
  labels:
    app: wordpress
spec:
  ports:
    - port: 3306
  selector:
    app: wordpress
    tier: mysql
  clusterIP: None
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: mysql-pv-claim
  labels:
    app: wordpress
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 3Gi
---
apiVersion: apps/v1 # for versions before 1.9.0 use apps/v1beta2
kind: Deployment
metadata:
  name: wordpress-mysql
  labels:
    app: wordpress
spec:
  selector:
    matchLabels:
      app: wordpress
      tier: mysql
  strategy:
    type: Recreate
  template:
    metadata:
      labels:
        app: wordpress
        tier: mysql
    spec:
      containers:
      - image: mysql:5.6
        name: mysql
        env:
        - name: MYSQL_ROOT_PASSWORD
          valueFrom:
            secretKeyRef:
              name: mysql-pass
              key: password
        ports:
        - containerPort: 3306
          name: mysql
        volumeMounts:
        - name: mysql-persistent-storage
          mountPath: /var/lib/mysql
      volumes:
      - name: mysql-persistent-storage
        persistentVolumeClaim:
          claimName: mysql-pv-claim

wordpress-deployment.yaml:

apiVersion: v1
kind: Service
metadata:
  name: wordpress
  labels:
    app: wordpress
spec:
  ports:
    - port: 80
  selector:
    app: wordpress
    tier: frontend
  type: LoadBalancer
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: wp-pv-claim
  labels:
    app: wordpress
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 3Gi
---
apiVersion: apps/v1 # for versions before 1.9.0 use apps/v1beta2
kind: Deployment
metadata:
  name: wordpress
  labels:
    app: wordpress
spec:
  selector:
    matchLabels:
      app: wordpress
      tier: frontend
  strategy:
    type: Recreate
  template:
    metadata:
      labels:
        app: wordpress
        tier: frontend
    spec:
      containers:
      - image: wordpress:4.8-apache
        name: wordpress
        env:
        - name: WORDPRESS_DB_HOST
          value: wordpress-mysql
        - name: WORDPRESS_DB_PASSWORD
          valueFrom:
            secretKeyRef:
              name: mysql-pass
              key: password
        ports:
        - containerPort: 80
          name: wordpress
        volumeMounts:
        - name: wordpress-persistent-storage
          mountPath: /var/www/html
      volumes:
      - name: wordpress-persistent-storage
        persistentVolumeClaim:
          claimName: wp-pv-claim

Deploy to Minikube

The kustomization.yaml contains all the resources for deploying a WordPress site and a MySQL database including a Secret generator for the MySQL password we want to use.

$ kubectl apply -k ./
secret/mysql-pass-km99f6b4f8 created
service/wordpress-mysql created
service/wordpress created
deployment.apps/wordpress-mysql created
deployment.apps/wordpress created
persistentvolumeclaim/mysql-pv-claim created
persistentvolumeclaim/wp-pv-claim created    

$ kubectl get all
NAME                                   READY   STATUS    RESTARTS   AGE
pod/wordpress-6bcdc557df-xm4qn         1/1     Running   0          46s
pod/wordpress-mysql-6fffffbdfc-xzckl   1/1     Running   0          46s

NAME                      TYPE           CLUSTER-IP       EXTERNAL-IP   PORT(S)        AGE
service/kubernetes        ClusterIP      10.96.0.1        <none>        443/TCP        14h
service/wordpress         LoadBalancer   10.105.115.173   <pending>     80:31389/TCP   46s
service/wordpress-mysql   ClusterIP      None             <none>        3306/TCP       47s

NAME                              READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/wordpress         1/1     1            1           46s
deployment.apps/wordpress-mysql   1/1     1            1           46s

NAME                                         DESIRED   CURRENT   READY   AGE
replicaset.apps/wordpress-6bcdc557df         1         1         1       46s
replicaset.apps/wordpress-mysql-6fffffbdfc   1         1         1       46s

$ kubectl get secret
NAME                    TYPE                                  DATA   AGE
default-token-kz545     kubernetes.io/service-account-token   3      14h
mysql-pass-km99f6b4f8   Opaque                                1      4m44s

$ kubectl describe secrets mysql-pass-km99f6b4f8
Name:         mysql-pass-km99f6b4f8
Namespace:    default
Labels:       <none>
Annotations:  
Type:         Opaque

Data
====
password:  8 bytes

To get the IP Address for the WordPress Service:

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

Copy the IP address, and load the page in a browser to view the site. We should see the WordPress set up page: