Deploy MySQL on Kubernetes with Backup: StatefulSet Template

Running MySQL on Kubernetes as a standard Deployment does not guarantee stable pod identity or ordered lifecycle management, which can lead to data inconsistency and storage reattachment failures. This template deploys MySQL 8.0 as a StatefulSet with VolumeClaimTemplates, a headless Service for stable DNS, a ClusterIP Service for load-balanced connections, a non-root security context, externalized credentials, and a scheduled backup CronJob.

What's Included

Component	Type	Port	Role
MySQL 8.0	StatefulSet	3306	Primary database with stable pod identity and ordered lifecycle
PVC (via VolumeClaimTemplates)	PersistentVolumeClaim	-	Automatically provisioned persistent storage per pod
Headless Service	Service	-	Stable DNS for direct pod addressing (mysql-0.mysql-headless)
ClusterIP Service	Service	3306	Load-balanced access for standard database connections
ConfigMap	ConfigMap	-	Non-sensitive database name configuration
Secret	Secret	-	MySQL credentials injected at runtime
Backup CronJob	CronJob	-	Scheduled database backups

Architecture Overview

MySQL 8.0 runs as a StatefulSet with VolumeClaimTemplates that automatically provision a PVC per pod. A headless Service provides stable DNS addresses (mysql-0.mysql-headless.default.svc.cluster.local) for clients that require a direct connection to a specific pod. A standard ClusterIP Service handles load-balanced traffic for general database clients. The ConfigMap stores the database name and the Secret injects credentials at runtime. A SecurityContext enforces non-root execution at UID 1001. A CronJob handles scheduled backups.

Prerequisites

A running Kubernetes cluster
Storage class configured for dynamic PVC provisioning
KubeKanvas CLI installed and running on your computer (Optional, if you want to use one-click deployment)

How to Deploy

Click Use Template to load the manifest into the editor.
Update the ConfigMap with your database name.
Replace the credential placeholders in the Secret with your base64-encoded MySQL username and password.
Confirm the storage class in the VolumeClaimTemplates matches what is available in your cluster.
Deploy the template to your cluster via the Play button in the top right bar. If you prefer to deploy manually, download the YAML and apply it with kubectl.
Wait for all pods to reach Running status. You can monitor progress in the Release Monitor screen.

How to Test

Confirm the StatefulSet pod is running and the PVC is bound: kubectl get pods,pvc -n <namespace>.
Open a MySQL shell on the pod: kubectl exec -it mysql-0 -n <namespace> -- mysql -u <username> -p.
Run SHOW DATABASES; to confirm your configured database is listed.
Run SELECT VERSION(); to verify MySQL 8.0 is running.

Use Cases

Stateful MySQL workloads: Replacing a MySQL Deployment with a StatefulSet for guaranteed stable pod naming and reliable PVC reattachment across restarts.
Dual-access database setup: Applications that need both direct pod addressing via the headless Service and load-balanced access via the ClusterIP Service simultaneously.
Backup-enabled database deployment: Running MySQL on Kubernetes with automated CronJob backups built in from day one.
Non-root database containers: Environments that require all database processes to run as a non-root user as part of a security policy.

Summary

This template configures a MySQL 8.0 StatefulSet on Kubernetes with automatic persistent storage, dual-service networking, a non-root security context, externalized credentials, and scheduled backups.

Tags:

#MySQL#StatefulSet#CronJob#BackupAndRecovery

Created by:

Mahmood

Deploy MySQL on Kubernetes with Backup: StatefulSet Template template preview

0 uses

What's Included

Component	Type	Port	Role
MySQL 8.0	StatefulSet	3306	Primary database with stable pod identity and ordered lifecycle
PVC (via VolumeClaimTemplates)	PersistentVolumeClaim	-	Automatically provisioned persistent storage per pod
Headless Service	Service	-	Stable DNS for direct pod addressing (mysql-0.mysql-headless)
ClusterIP Service	Service	3306	Load-balanced access for standard database connections
ConfigMap	ConfigMap	-	Non-sensitive database name configuration
Secret	Secret	-	MySQL credentials injected at runtime
Backup CronJob	CronJob	-	Scheduled database backups

Architecture Overview

How to Deploy

Click Use Template to load the manifest into the editor.

Update the ConfigMap with your database name.

Replace the credential placeholders in the Secret with your base64-encoded MySQL username and password.

Confirm the storage class in the VolumeClaimTemplates matches what is available in your cluster.

Deploy the template to your cluster via the Play button in the top right bar. If you prefer to deploy manually, download the YAML and apply it with kubectl.

Wait for all pods to reach Running status. You can monitor progress in the Release Monitor screen.

How to Test

Confirm the StatefulSet pod is running and the PVC is bound: kubectl get pods,pvc -n <namespace>.

Open a MySQL shell on the pod: kubectl exec -it mysql-0 -n <namespace> -- mysql -u <username> -p.

Run SHOW DATABASES; to confirm your configured database is listed.

Run SELECT VERSION(); to verify MySQL 8.0 is running.

Use Cases

Stateful MySQL workloads: Replacing a MySQL Deployment with a StatefulSet for guaranteed stable pod naming and reliable PVC reattachment across restarts.

Dual-access database setup: Applications that need both direct pod addressing via the headless Service and load-balanced access via the ClusterIP Service simultaneously.

Backup-enabled database deployment: Running MySQL on Kubernetes with automated CronJob backups built in from day one.

Non-root database containers: Environments that require all database processes to run as a non-root user as part of a security policy.