Is Kubernetes the best choice for this setup? The honest answer: no. It\u2019s too complex. Too many things can go wrong.<\/p>\n\n\n\n
Can it scale? So-so. As long as the database can handle the requests, it should work.<\/p>\n\n\n\n
So why am I doing this? Mostly for the fun of it. Many things could be done better. Credentials could be stored more securely, the database architecture could be improved, resources could be provisioned more efficiently, and scaling could be faster.<\/p>\n\n\n\n
This article is a good reference for how I usually start my projects and gradually improve them. Along the way, I\u2019ll cover some core Kubernetes concepts like Deployments, exposing applications to the internet, and building both stateless and stateful applications.<\/p>\n\n\n\n I already have a Kubernetes cluster<\/a> with persistent volumes<\/a>, a way to expose applications to the Internet<\/a>, and a certificate manager. Let\u2019s get my hands dirty.<\/p>\n\n\n\n My first task is to understand how the application works and create a simple plan to follow.<\/p>\n\n\n\n Where does WordPress store persistent data?<\/strong> How do we tell WordPress where the database is and which hostname to use?<\/strong> Database?<\/strong> The plan is simple:<\/p>\n\n\n\n Let’s see how to deploy it with docker first. From official docker hub<\/a>:<\/p>\n\n\n\n![\"\"](\"https:\/\/blog.twis7.com\/wp-content\/uploads\/2026\/03\/wordpress-inside-kubernetes-1024x559.png\")
<\/figure>\n\n\n\n\n\n\n\nWordPress requirements<\/h3>\n\n\n\n
\n
The obvious questions<\/h3>\n\n\n\n
\/wp-content<\/code><\/p>\n\n\n\n
Environment variables.<\/p>\n\n\n\n
It will be installed in Kubernetes. Usually this is not the best idea, but I need something simple for this setup.<\/p>\n\n\n\nThe plan<\/h3>\n\n\n\n
\n
Build MySQL database<\/h2>\n\n\n\n