Applications may need database copies for read traffic or to help recover when the writable server fails. The historical mysqlha chart deployed a MySQL primary with replicas that copied its changes. That is the arrangement represented by this package name, rather than a separate database engine. The chart is retired, and its replica count alone does not explain who promotes a replacement primary, prevents conflicting writers or changes the application's connection destination.
Current guidance
The original incubator/mysqlha README marks the chart deprecated and no longer supported. It describes a single writable primary with replicas and lists MySQL 5.7-era and sample XtraBackup images. The historical name mysqlha is a package name, not a certification of automated promotion, fencing or recovery.
Inventory replication users, server identifiers, PVC ownership and client routing before replacing an existing release. Determine what actually happens when the primary fails: which component promotes a replica, prevents conflicting writers and changes the application endpoint. Read replicas and persistent volumes alone do not answer those questions.
Choose a currently documented MySQL deployment approach and compare its topology and upgrade path with the existing data. For example, MySQL’s documented upgrade path from 5.7 to 8.4 passes through 8.0; replacing the chart does not make a direct version jump supported. Rehearse a supported migration and restore separately, checking replication lag, accounts and application behavior during reconnection. Preserve a recoverable source and avoid starting two independent primaries over the same data. The retired chart does not retire MySQL itself, and a replacement operator should not be presented as compatible with these old values without a specific migration test.
Historical upstream link check · 2026-10-09
The recorded upstream address responded successfully (HTTP 200) on 2026-10-09. GitHub confirms that helm/charts is archived: this is a historical chart distribution, not evidence that the application itself is retired. Link availability does not certify the historical installation instructions or current security support.
Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.
Historical Kubedex content
Preserved for context. Commands, versions, prices and results below reflect the original research.
MySQL is one of the most popular database servers in the world. Notable users include Wikipedia, Facebook, and Google.
This chart bootstraps a single master and multiple slave MySQL deployment on a Kubernetes cluster using the Helm package manager. Largely inspired by this tutorial, further work was made to ‘production-ize’ the example.
Prerequisites
- Kubernetes 1.6+
- PV provisioner support in the underlying infrastructure
The MySQL image stores the MySQL data and configurations at the /var/lib/MySQL path of the container.
By default, persistence is enabled, and a PersistentVolumeClaim is created and mounted in that directory.
In order to disable this functionality, you can change the values.yaml to disable persistence and use an emptyDir instead.
Sources & further reading
Spotted something that needs another look?
Help improve this page →