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 | 235 | 17 Feb 2025 | |
| 8.0/beta | 234 | 17 Feb 2025 | |
| 8.0/edge | 237 | 19 Feb 2025 | |
| 8.0/edge | 236 | 19 Feb 2025 |
juju deploy mysql-k8s --channel 8.0/stable
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:
Note: All commands are written for juju >= v3.0
If you are using an earlier version, check the Juju 3.0 Release Notes.
How to restore backup
This is a How-To for performing a basic restore (restoring a locally made backup). To restore a backup that was made from the a different cluster, (i.e. cluster migration via restore), please reference the Cluster Migration via Restore How-To:
Prerequisites
- Scale-down to the single MySQL unit (scale it up after the backup is restored).
- Access to S3 storage
- Have configured settings for S3 storage
- Have existing backups in your S3-storage
Summary
List backups
To view the available backups to restore you can enter the command list-backups:
juju run mysql-k8s/leader list-backups
This should show your available backups
backups: |-
backup-id | backup-type | backup-status
----------------------------------------------------
YYYY-MM-DDTHH:MM:SSZ | physical | finished
Restore backup
To restore a backup from that list, run the restore command and pass the backup-id to restore:
juju run mysql-k8s/leader restore backup-id=YYYY-MM-DDTHH:MM:SSZ
Your restore will then be in progress.