Revision 75

The first stable revision of Charmed MySQL for K8s has been published in the 8.0/stable channel on Charmhub .

See also: System requirements

Architecture

Charm revision

MySQL version

Minimum Juju version

amd64

75

8.0.32

2.9.32+

Features

  • 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.

Charm

Version

Charm channel

Documentation

License

MySQL K8s

8.0.32

8.0/stable (r75)

Tutorial , README , Contributing

Apache 2.0

Full Changelog: https://github.com/canonical/mysql-k8s-operator/commits/rev75

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

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!

These release notes were originally posted here .