Scaling a containerized WordPress site with Kubernetes, worth it for a mid-size blog

Hi everyone, I run a content site called Crabguide built on WordPress (recently moved parts of it to Docker for consistent environments). One of our high-traffic guides is our molted crab identification page, and traffic spikes hard whenever it ranks well or gets shared.

I am wondering if moving from plain Docker Compose to a small Kubernetes cluster is overkill for a site this size, or if it genuinely helps handle traffic spikes better than just scaling a single Droplet manually. Would appreciate hearing from anyone who runs a content-heavy WordPress site on k8s, is the complexity worth it at a small scale, or should I wait until traffic justifies it more?

Thanks!

In my previous job i have created next.js blog which did had a lot of traffic.

Though k8s CAN help in this case, i don’t think it does worth the complexity of k8s (and cost as well)

The easiest solution would be move to a stronger VM, for example to hetzner which have the highest spec per cost comparing to other providers and use cloudflare to cache static content aggressively.

Another easiest solution is just use manage wordpress services.

I will only go with k8s in this case if:

  1. I know k8s really well and other part of my service/apps depends on it.
  2. You are ready to pay for it. (as far as i know the lowest cost of k8s manage service is provided by civo even there if you use 3 nodes it would cost you around ~$60)

Thank you so much, Daniel. I will try it for sure.

1 Like