Reference > Release Notes > All releases > Revision 305/306

Revision 305/306

_TODO

Dear community,

Canonical’s newest Charmed MySQL operator has been published in the 8.0/stable channel.

Due to the newly added support for arm64 architecture, the MySQL charm now releases two revisions simultaneously:

• Revision 306 is built for amd64
• Revision 305 is built for arm64

To make sure you deploy for the right architecture, we recommend setting an architecture constraint for your entire Juju model.

Otherwise, you can specify the architecture at deploy time with the --constraints flag as follows:

juju deploy mysql --constraints arch=<arch>

where <arch> can be amd64 or arm64.

Highlights

Below is an overview of the major highlights, enhancements, and bugfixes in this revision. For a detailed list of all commits since the last stable release, see the GitHub release notes.

• Upgraded MySQL from v8.0.36 → v8.0.37 (see Packaging)
• Added support or ARM64 architecture (PR #472)
• Added support for Audit plugin (PR #488) (DPE-4366)

Enhancements

• Added Awesome Prometheus Alert Rules (criticality) (PR #493) (DPE-2477)
• Add integration with COS Tempo HA (DPE-5312)
• New Terraform module (DPE-5627)
• Changeed binlog retention period (one week by default) (PR #503) (DPE-4247)
• Added support for re-scanning cluster for unit rejoin after node drain (PR #462) (DPE-4118)
• Enable and use admin address/port for operator users (PR #516) (DPE-5178)

Bugfixes

• Fixed MySQL Group replication start logic during the juju refresh (PR #546) (DPE-5941)
• Removed passwords from outputs and tracebacks (PR #499) (DPE-4266)
• Fixed cluster metadata and instance state checks (PR #482) (DPE-4850)
• Ensure username uniqueness (PR #464) (DPE-4643)
• Set instance offline mode on restore (PR #478) (DPE-4699)
• Added support for re-scanning cluster for unit rejoin after node drain (PR #462) (DPE-4118)
• Fixes for backup logging (PR #471) (DPE-4699)
• Fixed global-primary on endpoint (PR #467) (DPE-4658)
• Skip set unknown config keys (PR #532) (DPE-5628)
• Change key logs from debug->info (PR #527) (DPE-4910)
• Fixed timeout node count query (PR #528) (DPE-5582)
• Skip plugin install for not file found (PR #524) (DPE-5540)
• Skip tls reconfiguration on unit teardown (PR #522) (DPE-5493)
• Upgrade fix for admin-address enabled charm (PR #520) (DPE-5178)
• Update all dependencies to the latest versions.

Technical details

This section contains some technical details about the charm’s contents and dependencies.

If you are jumping over several stable revisions, check previous release notes before upgrading.

Requirements and compatibility

This charm revision features the following changes in dependencies:

• (increased) MySQL version v8.0.37

This release of Charmed MySQL requires Juju v.3.4.3 or 3.5.2+. See the guide How to upgrade Juju for a new database revision.

See the system requirements page for more details about software and hardware prerequisites.

Integration tests

Below are the charm integrations tested with this revision on different Juju environments and architectures:

• Juju v2.9.49 on amd64
• Juju v3.4.4 on amd64 and arm64

Juju v2.9.49 on amd64:

Juju v3.4.4 on amd64 and arm64:

All:

See the /lib/charms directory on GitHub for a full list of supported libraries.

See the Integrations tab for a full list of supported integrations/interfaces/endpoints.

Packaging

This charm is based on the charmed-mysql snap Revision 113/114. It packages:

• mysql-server-8.0: 8.0.37-0ubuntu0.22.04.1
• mysql-router v8.0.37: 8.0.37-0ubuntu0.22.04.1
• mysql-shell v8.0.37: 8.0.37+dfsg-0ubuntu0.22.04.1~ppa3
• prometheus-mysqld-exporter v0.14.0: 0.14.0-0ubuntu0.22.04.1~ppa2
• prometheus-mysqlrouter-exporter v5.0.1: 5.0.1-0ubuntu0.22.04.1~ppa1
• percona-xtrabackup v8.0.35: 8.0.35-31-0ubuntu0.22.04.1~ppa3

Contact us

Charmed MySQL is an open source project that warmly welcomes community contributions, suggestions, fixes, and constructive feedback.

• Raise software issues or feature requests on GitHub
• Report security issues through Launchpad
• Contact the Canonical Data Platform team through our Matrix channel.