Charmed MySQL K8s
- Canonical
- Databases
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| 8.0/stable | 180 | 02 Sep 2024 | |
| 8.0/stable | 181 | 02 Sep 2024 | |
| 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 | 211 | 09 Dec 2024 | |
| 8.0/edge | 210 | 09 Dec 2024 |
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:
Charmed MySQL K8s revision 75
April 20, 2023
Dear community, this is to inform you that new Canonical Charmed MySQL K8s charm is published in 8.0/stable charmhub channel for Kubernetes.
The features you can start using today:
- Deploying on Kubernetes (tested with MicroK8s, GKE)
- juju constraints are supported to limit CPU/RAM/Storage size
- Scaling up/down in one simple juju command
- HA using Innodb Group replication
- Full backups and restores are supported when using any S3-compatible storage
- TLS support (using “tls-certificates” operator)
- DB access outside of Juju using “data-integrator”
- Data import using standard tools e.g. mysqldump, etc.
- Documentation:
| Charm | Version | Charm channel | Documentation | License |
|---|---|---|---|---|
| MySQL K8s | 8.0.32 | 8.0/stable (r75) | Tutorial, Readme, Contributing | Apache 2.0 |
What is inside the charms:
- Charmed MySQL K8s charm ships the latest MySQL “8.0.32-0ubuntu0.22.04.2”
- K8s charms based on our ROCK OCI (Ubuntu LTS “22.04” - ubuntu:22.04-based)
- Principal charms supports the latest LTS series “22.04” only.
- Subordinate charms support LTS “22.04” and “20.04” only.
Technical notes:
Compatibility with legacy charms:
- New MySQL charm is a juju-interface compatible replacement for legacy charms such as “MariaDB”, “OSM MariaDB”, “Percona Cluster” and “Mysql Innodb Cluster” (using legacy interface “mysql”, via endpoints “mysql” and “mysql-root”). Other legacy interfaces such as “mysql-router” interface (“db-router” endpoint) and “mysql-shared” interface (“shared-db” endpoint) are also supported. However, it is highly recommended to migrate to the modern interface ‘mysql_client ’. It can be easily done using the charms library ‘data_interfaces’ from ‘data-platform-libs’.
Please contact us, see details below, if you are considering migrating from other “legacy” charms not mentioned above. Additionally:
- Tracks description:
- Charm MySQL K8s charm follows the SNAP track “8.0” (through repacked ROCK/OCI image).
- No “latest” track in use (no surprises in tracking “latest/stable”)!
- Charmed MySQL K8s charms provide legacy charm through “latest/stable”.
- Charm lifecycle flowchart diagrams: MySQL.
- Modern interfaces are well described in “Interfaces catalogue” and implemented by ‘data-platform-libs’.
How to reach us:
If you would like to chat with us about your use-cases or ideas, you can reach us at Canonical Mattermost public channel or Discourse. Check all other contact details here.
Consider opening a GitHub issue if you want to open a bug report. Contribute to the project!
Footer:
The document was originally posted here.