AH
All projects

Kubernetes WordPress Workshop

  • Kubernetes
  • Minikube
  • Docker
  • Helm
  • NGINX Ingress
  • WordPress
  • MariaDB
  • Prometheus
  • Grafana

The problem

Running a stateful application by hand gives no repeatable deployment path and no visibility into what the platform is actually doing.

The goal

Deploy a real application with its database on Kubernetes using Helm, expose it through an ingress, and put a monitoring stack in front of it.

The architecture

  • Minikube cluster as the local Kubernetes environment
  • NGINX Ingress routing external traffic
  • WordPress deployed via Helm
  • MariaDB as the backing database
  • Prometheus collecting metrics
  • Grafana dashboards on top of Prometheus
Minikube Cluster
  ↓
NGINX Ingress
  ↓
WordPress
  ↓
MariaDB

Prometheus → Grafana
Kubernetes WordPress Workshop — architecture diagram

My approach

Use Helm so deployments stay repeatable, then add Prometheus and Grafana so the running platform can be observed rather than assumed.

Implementation

  • Helm-based deployment of WordPress and MariaDB
  • NGINX Ingress configuration for external access
  • Prometheus and Grafana monitoring stack