Revision 113

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

See also: System requirements, How to upgrade

Architecture

Charm revision

MySQL version

Minimum Juju version

amd64

113

8.0.34

3.1.6+

If you are jumping over several stable revisions, make sure to check previous release notes before upgrading to this revision.

Features

Bug fixes

Canonical Data issues are now public on both Jira and GitHub platforms.
GitHub Releases provide a detailed list of bug fixes/PRs/Git commits for each revision.
Highlights for the current revision:

  • Fixed date format in logrotate config to avoid causing filename conflicts after 24hrs of uptime [PR#343][DPE-3063]

  • Fixed bug that resulted in wrong output displayed from list-backups action [PR#340]

  • Fixed unit removal issue if TLS operator is in use [PR#347]

  • Fixed the single unit upgrade [PR#324][DPE-2661]

  • Improved cluster metadata node addresses consistency [PR#328][DPE-2774]

  • Fixed lib config file render [#303][DPE-2124]

  • Prevent starting logrotate dispatcher or flush mysql logs until unit initialized [PR#323]

  • Defer reconciling pebble layer for exporter [PR#302]

Full Changelog: https://github.com/canonical/mysql-k8s-operator/compare/rev99…rev113

What is inside the charms

  • Charmed MySQL K8s ships the latest MySQL “8.0.34-0ubuntu0.22.04.1”

  • CLI mysql-shell updated to “8.0.34-0ubuntu0.22.04.1~ppa1”

  • Backup tools xtrabackup/xbcloud updated to “8.0.34-29”

  • The Prometheus mysqld-exporter is “0.14.0-0ubuntu0.22.04.1~ppa1”

  • K8s charms based on our ROCK OCI (Ubuntu LTS “22.04” - ubuntu:22.04-based) based on SNAP revision 69

  • Principal charms supports the latest LTS series “22.04” only

  • Subordinate charms support LTS “22.04” and “20.04” only

Technical notes

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!