In this setup, we are using a single replica MySQL. If you want a production grade MySQL setup, refer the
MySQL Kubernetes Operator<\/a> setup.<\/div><\/div>Now, that the PVC and ConfigMap have been created, it is time to deploy MySQL database and WordPress.<\/p>
First, we are going to deploy the MySQL database, and run the mysql.yaml<\/code><\/strong> file to deploy the database on the WordPress namespace.<\/p>apiVersion: apps\/v1\nkind: StatefulSet\nmetadata:\n name: mysql\n namespace: wordpress\nspec:\n serviceName: \"mysql\"\n replicas: 1\n selector:\n matchLabels:\n app: mysql\n template:\n metadata:\n labels:\n app: mysql\n spec:\n containers:\n - name: mysql\n image: mysql:latest\n env:\n - name: MYSQL_ROOT_PASSWORD\n valueFrom:\n secretKeyRef:\n name: mysql-cred\n key: admin-password\n - name: MYSQL_USER\n valueFrom:\n secretKeyRef:\n name: mysql-cred\n key: username\n - name: MYSQL_PASSWORD\n valueFrom:\n secretKeyRef:\n name: mysql-cred\n key: password\n - name: MYSQL_DATABASE\n valueFrom:\n secretKeyRef:\n name: mysql-cred\n key: db-name\n volumeMounts:\n - name: mysql-volume\n mountPath: \/var\/lib\/mysql\n - name: mysql-config\n mountPath: \/docker-entrypoint-initdb.d\n resources:\n requests:\n memory: \"256Mi\"\n cpu: \"100m\"\n limits:\n memory: \"512Mi\"\n cpu: \"200m\"\n livenessProbe:\n tcpSocket:\n port: 3306\n initialDelaySeconds: 30\n periodSeconds: 10\n timeoutSeconds: 5\n successThreshold: 1\n failureThreshold: 3\n readinessProbe:\n tcpSocket:\n port: 3306\n initialDelaySeconds: 30\n periodSeconds: 10\n timeoutSeconds: 5\n successThreshold: 1\n failureThreshold: 3\n volumes:\n - name: mysql-config\n configMap:\n name: mysql-configmap\n volumeClaimTemplates:\n - metadata:\n name: mysql-volume\n spec:\n accessModes: [\"ReadWriteOnce\"]\n resources:\n requests:\n storage: 2Gi\n---\napiVersion: v1\nkind: Service\nmetadata:\n name: mysql-service\n namespace: wordpress\nspec:\n type: ClusterIP\n selector:\n app: mysql\n ports:\n - protocol: TCP\n port: 3306\n targetPort: 3306<\/code><\/pre>This file deploys a mysql<\/strong> statefulset database on the wordpress namespace which uses the latest MySQL container image.<\/p>The environment variable gets the values from the secret we created in Step 2<\/strong> and the configmap gets the values during startup.<\/p>The docker-entrypoint-initdb.d<\/code><\/strong> directory is part of the MySQL image. Any MySQL scripts placed in this folder will be executed during MySQL startup. It is primarily used for running database initialization scripts.<\/p>In our setup, we placed an init script (init.sql<\/code><\/strong>) in this folder through a ConfigMap (mysql-configmap<\/strong>). init.sql <\/code><\/strong>creates the username and password, and gives the user all privileges on the WordPress db.<\/p>The script retrieves the username and password from environment variables set by the secret object using secretKeyRef<\/code><\/strong><\/p>And it also creates a PVC and mounts the PV on the \/var\/lib\/mysql<\/strong> directory.<\/p>Also, I have added health checks for MySQL:<\/p>
livenessProbe<\/strong> \u2013 This checks if MySQL is up and running by using a TCP socket check on port 3306.<\/li>readinessProbe<\/strong> \u2013 This checks if MySQL is ready to accept traffic.<\/li><\/ol>Then, this file also creates a Service that exposes the database on port 3306<\/strong>.<\/p>Run the following command to deploy MySQL and its service<\/p>
kubectl apply -f mysql.yaml<\/code><\/pre>Now, run the following commands to check if the MySQL StatefulSet and its service is deployed<\/p>
kubectl get sts\n\nkubectl get svc<\/code><\/pre>You will get the following output.<\/p>Step 7: Deploy WordPress<\/h3> After you finish deploying the MySQL Database, the next step is to deploy the WordPress application by running the file wordpress.yaml<\/strong>.<\/p>apiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\n name: wordpress-pvc\n namespace: wordpress\nspec:\n accessModes:\n - ReadWriteOnce\n resources:\n requests:\n storage: 2Gi\n---\napiVersion: apps\/v1\nkind: Deployment\nmetadata:\n name: wordpress\n namespace: wordpress\nspec:\n replicas: 1\n selector:\n matchLabels:\n app: wordpress\n template:\n metadata:\n labels:\n app: wordpress\n spec:\n securityContext:\n fsGroup: 33\n containers:\n - name: wordpress\n image: techiescamp\/wordpress-nginx:7.0.0\n env:\n - name: DB_HOST\n value: mysql-service.wordpress.svc.cluster.local\n - name: DB_USER\n valueFrom:\n secretKeyRef:\n name: mysql-cred\n key: username\n - name: DB_PASSWORD\n valueFrom:\n secretKeyRef:\n name: mysql-cred\n key: password\n - name: DB_NAME\n valueFrom:\n secretKeyRef:\n name: mysql-cred\n key: db-name\n ports:\n - containerPort: 80\n name: wordpress\n resources:\n requests:\n memory: \"256Mi\"\n cpu: \"100m\"\n limits:\n memory: \"512Mi\"\n cpu: \"200m\"\n volumeMounts:\n - name: nginx-config-volume\n mountPath: \/etc\/nginx\/conf.d\n - name: wordpress-persistent-storage\n mountPath: \/var\/www\/html\/wordpress\/wp-content\/uploads\n readinessProbe:\n httpGet:\n path: \/wp-login.php\n port: 80\n scheme: 'HTTP'\n initialDelaySeconds: 30\n periodSeconds: 10\n timeoutSeconds: 5\n successThreshold: 1\n failureThreshold: 3\n livenessProbe:\n httpGet:\n path: \/wp-admin\/install.php\n port: 80\n scheme: 'HTTP'\n initialDelaySeconds: 60\n periodSeconds: 10\n timeoutSeconds: 5\n successThreshold: 1\n failureThreshold: 3\n volumes:\n - name: nginx-config-volume\n configMap:\n name: nginx-configmap\n - name: wordpress-persistent-storage\n persistentVolumeClaim:\n claimName: wordpress-pvc\n---\nkind: Service\napiVersion: v1\nmetadata:\n name: wordpress-service\n namespace: wordpress\nspec:\n type: NodePort\n selector:\n app: wordpress\n ports:\n - name: http\n protocol: TCP\n port: 80\n targetPort: 80\n nodePort: 30004<\/code><\/pre>First, this application creates a PVC for the WordPress application.<\/p>
Then it deploys the WordPress<\/strong> application on the WordPress namespace which uses the techiescamp\/wordpress-nginx:7.0.0<\/strong> container image we created in Step 1<\/strong>.<\/p>The environment variable gets the values from the secret we created in Step 2<\/strong> and the startup script inside the container image fetches the values and updates them on the \/var\/www\/html\/wordpress\/wp-config.php\/uploads<\/strong> WordPress configuration file.<\/p>It mounts the data on the configmap nginx-cm<\/strong> we created in Step 3<\/strong> on the directory \/etc\/nginx\/conf.d<\/strong> and mounts the PV on the \/var\/www\/html\/wordPress\/wp-content\/uploads<\/strong> directory.<\/p>In the resource configuration, the container\u2019s resource request is set to 256Mi memory and 100m CPU<\/strong>, and the limit is set to 512Mi memory and 200m CPU<\/strong>.<\/p>Also, I have added health checks for this application:<\/p>
readinessProbe<\/strong> \u2013 This checks if the application is ready to accept traffic using the readiness path \/wp-login.php<\/strong>. If this probe fails, it won\u2019t receive any traffic.<\/li>livenessProbe<\/strong> \u2013 Checks if the application is up and running using the liveness path \/wp-admin\/install.php<\/strong>. If the probe fails, Kubernetes will restart the pod.<\/li><\/ol>Then, this file also creates a Service that exposes WordPress to the outside world using nodeport 30004.<\/p>
\ud83d\udca1<\/div>
You can also configure Ingress Controller instead of nodeport service to access the application on the web.<\/div><\/div>
Run the following command to deploy the WordPress.<\/p>
kubectl apply -f wordpress.yaml<\/code><\/pre>Now, run the following commands to check if the WordPress deployment and its service is deployed.<\/p>
kubectl get deploy\n\nkubectl get svc<\/code><\/pre>You will get the following output.<\/p>Since WordPress and MySQL have been created, check the status of PVC and PV using the following commands<\/p>
kubectl get pvc\n\nkubectl get pv<\/code><\/pre>You will get the following output.<\/p>As you can see, the PVC is in a bound state, and two PV for WordPress and MySQL have been created.<\/p>
Step 8: Create a NetworkPolicy<\/h3> Now, that MySQL and WordPress are deployed, create a NetworkPolicy for MySQL running the networkpolicy.yaml<\/strong> file<\/p>apiVersion: networking.k8s.io\/v1\nkind: NetworkPolicy\nmetadata:\n name: mysql-network-policy\n namespace: wordpress\nspec:\n podSelector:\n matchLabels:\n app: mysql\n policyTypes:\n - Ingress\n - Egress\n ingress:\n - from:\n - podSelector:\n matchLabels:\n app: wordpress\n ports:\n - port: 3306\n egress:\n - {}<\/code><\/pre>This file creates a Networkpolicy for MySQL on the WordPress namespace.<\/p>
The mysql-network-policy<\/strong> only allows incoming traffic from the pod labeled as wordpress<\/strong> through port 3306 and allows all outgoing traffic.<\/p>Run the following command to deploy the NetworkPolicy.<\/p>
kubectl apply -f networkpolicy.yaml<\/code><\/pre>To check if the NetworkPolicies are created, run the following command<\/p>
kubectl get netpol<\/code><\/pre>You will get the following output.<\/p>Step 9: Log in to WordPress UI<\/h3> Once every object has been created, try to access WordPress on the browser by searching on the browser as {node-IP:nodeport}<\/strong> or if you have configured the Ingress Controller, search the Domain name on the browser.<\/p>Since I have deployed using NodePort, I am going to use the node-IP:nodeport<\/strong>.<\/p>You can see a tab to select the language and will get the following on the browser.<\/p>After specifying the site title, username, password, and Email, it will be forwarded to the WordPress dashboard as shown below<\/p>Step 10: Clean Up the Setup<\/h2> Once you are done with the setup, run the following command inside the 04-WordPress-deployment<\/strong> to delete all resources<\/p>kubectl delete -f .<\/code><\/pre>This command will delete all the resources created by the manifest files inside the 04-WordPress-deployment<\/strong> directory.<\/p>Conclusion<\/h2> In this blog, we have seen the steps to deploy WordPress on Kubernetes clusters with Nginx and MySQL databases.<\/p>
Not just an installation, also added NetworkPolicy, and Probes like readiness and liveness probes to WordPress and MySQL as best practices.<\/p>
I hope this blog gives you a clear understanding of deploying WordPress on Kubernetes clusters with Nginx and MySQL databases, as well as the objects used in this setup.<\/p>\n
Ngu\u1ed3n:<\/strong> How to Deploy WordPress on Kubernetes with Nginx and MySQL \u2014 DevOpsCube<\/a><\/p>","protected":false},"excerpt":{"rendered":"Source: https:\/\/devopscube.com\/deploy-wordpress-on-kubernetes\/<\/p>\n","protected":false},"author":1,"featured_media":501,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-500","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops"],"_links":{"self":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/posts\/500","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=500"}],"version-history":[{"count":0,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/posts\/500\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/media\/501"}],"wp:attachment":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=500"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=500"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=500"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![\"architecture](\"https:\/\/storage.ghost.io\/c\/5f\/2f\/5f2f4d20-2abf-4534-8d40-7aa233aedd43\/content\/images\/2025\/07\/wordpress-mysql.gif\")
<\/figure>![\"docker](\"https:\/\/storage.ghost.io\/c\/5f\/2f\/5f2f4d20-2abf-4534-8d40-7aa233aedd43\/content\/images\/2025\/07\/image-165.png\")
<\/figure>![\"encoding](\"https:\/\/storage.ghost.io\/c\/5f\/2f\/5f2f4d20-2abf-4534-8d40-7aa233aedd43\/content\/images\/2025\/07\/image-167.png\")
<\/figure>![\"verifying](\"https:\/\/storage.ghost.io\/c\/5f\/2f\/5f2f4d20-2abf-4534-8d40-7aa233aedd43\/content\/images\/2025\/07\/image-166.png\")
<\/figure>![\"verifying](\"https:\/\/storage.ghost.io\/c\/5f\/2f\/5f2f4d20-2abf-4534-8d40-7aa233aedd43\/content\/images\/2025\/07\/image-168.png\")
<\/figure>![\"checking](\"https:\/\/storage.ghost.io\/c\/5f\/2f\/5f2f4d20-2abf-4534-8d40-7aa233aedd43\/content\/images\/2025\/07\/image-170.png\")
<\/figure>![\"checking](\"https:\/\/storage.ghost.io\/c\/5f\/2f\/5f2f4d20-2abf-4534-8d40-7aa233aedd43\/content\/images\/2025\/07\/image-171.png\")
<\/figure>![\"listing](\"https:\/\/storage.ghost.io\/c\/5f\/2f\/5f2f4d20-2abf-4534-8d40-7aa233aedd43\/content\/images\/2025\/07\/image-174.png\")
<\/figure>![\"check](\"https:\/\/storage.ghost.io\/c\/5f\/2f\/5f2f4d20-2abf-4534-8d40-7aa233aedd43\/content\/images\/2025\/07\/image-175.png\")
<\/figure>![\"page](\"https:\/\/storage.ghost.io\/c\/5f\/2f\/5f2f4d20-2abf-4534-8d40-7aa233aedd43\/content\/images\/2025\/03\/image-7-23.png\")
<\/figure>![\"wordpress](\"https:\/\/storage.ghost.io\/c\/5f\/2f\/5f2f4d20-2abf-4534-8d40-7aa233aedd43\/content\/images\/2025\/03\/image-8-19.png\")
<\/figure>