Charmed MySQL K8s
- Canonical
- Databases
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| 8.0/stable | 211 | 06 Jan 2025 | |
| 8.0/stable | 210 | 06 Jan 2025 | |
| 8.0/candidate | 211 | 11 Dec 2024 | |
| 8.0/candidate | 210 | 11 Dec 2024 | |
| 8.0/beta | 211 | 09 Dec 2024 | |
| 8.0/beta | 210 | 09 Dec 2024 | |
| 8.0/edge | 222 | 27 Jan 2025 | |
| 8.0/edge | 221 | 27 Jan 2025 |
juju deploy mysql-k8s --channel 8.0/beta
Deploy Kubernetes operators easily with Juju, the Universal Operator Lifecycle Manager. Need a Kubernetes cluster? Install MicroK8s to create a full CNCF-certified Kubernetes system in under 60 seconds.
Platform:
Upgrade
This section contains documentation about performing upgrades (and rollbacks) on:
MySQL upgrades (workload)
There are two types of in-place workload upgrades:
- Major upgrades - E.g. MySQL
8.0→ MySQL9.0- Not supported
- Minor upgrades - E.g. MySQL
8.0.33→8.0.34(includes charm revision bump)
This charm only supports in-place minor upgrades.
To upgrade to a major MySQL version, one must install a new cluster separately and migrate the data from the old to the new installation. This documentation will be updated with the migration instructions when a new MySQL version becomes available.
Juju upgrades
New revisions of the charm may require that you do a major or minor Juju upgrade.
See: How to upgrade Juju