This Kubernetes template deploys a stable, persistent, and production-grade MySQL database using StatefulSets, Headless Services, and Persistent Volumes. It is architected to handle the specific challenges of running stateful database workloads in dynamic, containerized environments.
By using this template, you avoid the risks of data loss and networking instability common in standard Deployment objects, ensuring your MySQL instance remains reliable under production pressure.
What This Template Creates for Your Cluster
This MySQL configuration provides a modular, best-practice infrastructure for your data layer.
Database Infrastructure
- MySQL 8.0 A high-performance, industry-standard relational database.
- StatefulSet Unlike a Deployment, this guarantees stable Pod names (e.g.,
mysql-0,mysql-1) and ordered startup and termination. - VolumeClaimTemplates Automatically provisions a dedicated Persistent Volume (PV) for each replica, ensuring data remains mapped to the correct Pod identity.
Networking & Access
-
Headless Service (
ClusterIP: None) Essential for discovery; it allows applications or backup scripts to address individual Pods directly.- Provides stable DNS endpoints such as:
mysql-0.mysql-headless.default.svc.cluster.local
- Provides stable DNS endpoints such as:
-
Standard Service Provides a single, load-balanced IP for applications to connect to the active database endpoint.
Configuration & Security
- ConfigMap Centralizes non-sensitive settings such as the default database name (
MYSQL_DATABASE). - Kubernetes Secrets Securely manages the root password and application user credentials, preventing sensitive data from being committed to version control.
- SecurityContext Enforces non-root execution (UID
1001) and sets filesystem permissions (fsGroup) to ensure MySQL can safely read and write persistent data.
