Revisions 254, 255

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

See also: Releases overview page, How to perform an upgrade

OCI image resources:

• mysql-image=ghcr.io/canonical/charmed-mysql@sha256:089fc04dd2d6f1559161ddf4720c1e06559aeb731ecae57b050c9c816e9833e9

What's Changed

Features

• DPE-1531 Avoid using initialize-insecure and instead use init-file to reset root user's password by @shayancanonical in #596
• DPE-6487 Point-in-time recovery support by @paulomach and @Zvirovyi in #600
• DPE-3830 Default to paxos single leader by @paulomach in #604
• DPE-6312 Add security policy by @paulomach in #605
• DPE-7534 use absolute fqdn for replication and consumers by @paulomach in #618

Bug fixes

• DPE-6733 test for DNS availability by @paulomach in #612

Full Changelog: rev240...rev255

Requirements and compatibility

• Recommended Juju version: v3.6.3+
• Minimum Juju version: v3.4.3 or v.3.5.2+

See the system requirements for more details about Juju versions and other software and hardware prerequisites.

Revisions 240, 241

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

See also: Releases overview page, How to perform an upgrade

OCI image resources:

• mysql-image=ghcr.io/canonical/charmed-mysql@sha256:089fc04dd2d6f1559161ddf4720c1e06559aeb731ecae57b050c9c816e9833e9

What's changed

This section outlines the most important features and bug fixes in this release.

Features

• DPE-5063 Update MySQL to v8.0.41 by @shayancanonical in #566 , #574
• DPE-5656 log rotation new options by @paulomach in #568
• DPE-6651 Update rock tag for new builds with updated percona packages by @shayancanonical in #594

Bug fixes

• DPE-6137 insecure password calls removal by @paulomach in #553
• DPE-4375 Add cluster manual re-join handler by @sinclert-canonical in #560
• DPE-6521 Add missing check and wait for pebble calls by @paulomach in #571
• DPE-6485 Manage mysqld directly by @paulomach in #575
• DPE-6666 Remove async-replication test workaround by @sinclert-canonical in #588
• DPE-5164 ensure failed bootstrap cleanup by @paulomach in #592

Full Changelog: rev210...rev240

New contributors

• @sinclert-canonical made their first contribution in #539

Requirements and compatibility

• Recommended Juju version: v3.6.3+
• Minimum Juju version: v3.4.3 or v.3.5.2+

See the system requirements for more details about Juju versions and other software and hardware prerequisites.

Revisions 210, 211

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

See also: Releases overview page, How to perform an upgrade

OCI image resources:

• mysql-image=ghcr.io/canonical/charmed-mysql@sha256:aa4d9b21673d2c6e4db3dc943179bae95dd8d355790b68e4e0610da9513ee6c9

What's changed

This section outlines the most important features and bug fixes in this release.

Features

• Updated MySQL to v8.0.39 (PR #488) (DPE-4573)
• Added fully-featured terraform module (PR #522) (DPE-5627)
  • See also: How to deploy on Terraform
• Updated COS alert rule descriptions (PR #519) (DPE-5659)
  • See also: How to enable alert rules,
• Bumped juju versions (PR #517)
  • v2.9.50 -> v2.9.51
  • v3.4.5 -> v3.5.4
• Integrated with Tempo HA and tested relay support of tracing traffic through grafana-agent-k8s (PR #518) (DPE-5312)
• Adopted admin address throughout charm (PR #502) (DPE-5178)
• Avoid ambiguous service selector when multiple mysql apps in a model have the same cluster-name (PR #501) (DPE-4861)
• Ensure that uninitialized variable not referenced in _is_cluster_blocked helper (PR #507) (DPE-5481)
• Recover from pod restarts during cluster creation during setup (PR #499)
• Added timeout on node count query (PR #514) (DPE-5582)

Bug fixes

• Fixed unit-initialized test may break when run too early (PR #491) (DPE-5209)
• Common credentials fixture and exec timeout workaround (PR #493) (DPE-5210)
• Fixed /database requested wait container (PR #500) (DPE-5385)
• Attempted to stabilize failing integration tests (PR #496)
• Add test to ensure correct k8s endpoints created for clusters with the same name (PR #508)
• Add check to ensure peer databag populated before reconciling mysqld exporter pebble layers (PR #505) (DPE-5417)
• Add base in test_multi_relations to workaround libjuju bug (PR #506) (DPE-5480)

Requirements and compatibility

• Minimum Juju version: v3.4.5 -> v3.5.4

See the system requirements for more details about Juju versions and other software and hardware prerequisites.

Full Changelog: rev180...rev210

Revisions 180, 181

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

See also: Releases overview page, How to perform an upgrade

What's changed

This section outlines the most important features and bug fixes in this release.

Features

• Upgraded MySQL from v8.0.36 -> v8.0.37 (see Packaging)
• Added support or ARM64 architecture (PR #448)
• Added support for Audit plugin (PR #474) (DPE-4970)
• Add first Awesome Alert Rules (PR #469) (DPE-2477)
• Added support for rescanning cluster for unit rejoin after node drain (PR #433) (DPE-4118)
• Changed binlog retention period (one week by default) (PR #478) (DPE-4247)

Bug fixes

• Removed passwords from outputs and tracebacks (PR #473) (DPE-4266)
• Fixed intermittent issue on AKS deployments (unknown/idle state) (PR #458) (DPE-4850)
• Strip passwords from command execute output and tracebacks (PR #473) (DPE-4266)
• Address drained units rejoining the cluster with a new PV (PR #433) (DPE-4118)
• Ensure username uniqueness (PR #439) (DPE-4643)
• Backup stabilization fixes (PR #444) (DPE-4699)
• Idempotent configure method (PR #451) (DPE-4800)
• Show global-primary on endpoint (PR #440) (DPE-4658)
• Fix metrics-endpoint created on scale up (PR #483)

Full Changelog: rev153...rev180

Requirements and compatibility

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.

• Minimum Juju version: 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.

Packaging

This charm is based on the charmed-mysql rock (CharmHub mysql-image resource-revision 113). 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

Revision 153

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

See also: Releases overview page, How to perform an upgrade

What's changed

This section outlines the most important features and bug fixes in this release.

Important

This charm revision requires Juju v3.4.3 or v3.5.2+
See: How to upgrade Juju

Features

• New workload version MySQL 8.0.36
• Async replication between clouds [DPE-2959]
• Add COS Tempo tracing support [#424][DPE-4368]
• Add experimental_max_connections config [#425][DPE-3706]
• Latest ROCK latest version [DPE-3717]
• Internal disable operator mode [DPE-2184]
• TLS CA chain support [PR#383]
• All the functionality from previous revisions

Bug fixes

• Updated shared libraries
• Applied the latest Juju secrets related fixes
• Fixed Sunbeam: charm is trying fail to set report_host on scale up #435, DPE-3896
• Skip config change when no pebble connection in #445, DPE-4768
• Fix restart for single-unit in #438, DPE-4411

Full Changelog: rev127...rev153

Inside the charms

• Charmed MySQL K8s ships MySQL 8.0.36-0ubuntu0.22.04.1
• CLI mysql-shell updated to 8.0.36+dfsg-0ubuntu0.22.04.1~ppa4
• Backup tools xtrabackup/xbcloud is 8.0.35-30
• The Prometheus mysqld-exporter is 0.14.0-0ubuntu0.22.04.1~ppa2
• K8s charms based on our ROCK OCI (Ubuntu LTS 22.04.4) mysql-image resource-revision 111
• Principal charms support the latest Ubuntu 22.04 LTS only

Technical notes

• Upgrade (juju refresh) is possible from revision 75+
• Creating Async replication under significant write load to Primary could lead to MySQL DB deadlock and replication setup failures, more details in official charm bugreport and MySQL bug.
• Use this operator together with modern operator MySQL Router K8s
• Please check restrictions from previous release notes
• Ensure the charm requirements met.

Revision 127

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

See also: Releases overview page, How to perform an upgrade

What's changed

This section outlines the most important features and bug fixes in this release.

Features

• Updated workload to MySQL 8.0.35 in #360
• Juju 3.1.7+ support in #2037120
• DPE-3402 Update TLS test lib and test charm in #370
• DPE-3617 Add CA chain support in #383
• Add Allure Report beta in #366
• All the functionality from the previous revisions

Bug fixes

• DPE-3547 Fixed mitigations for container restart in #377
• DPE-3389 Fixed support for rollbacks with incompatible data dir in #385
• DPE-2919 Fixed pod labels update on preemptive switchover in #367
• DPE-3265 Refactored lib secrets in #362
• DPE-2758 Fixed messaging when no bucket + ceph testing in #332
• DPE-3027 Fixed retry policy for is_mysqld_running in #356
• Fixed typo in secrets marker in #380
• Fixed parallel backup tests in #375
• Removed colon from logrotate file path in #351

Full Changelog: rev113...rev127

What is inside the charms

• Charmed MySQL K8s ships MySQL “8.0.35-0ubuntu0.22.04.1”
• CLI mysql-shell updated to "8.0.33-0ubuntu0.22.04.1~ppa1"
• Backup tools xtrabackup/xbcloud updated to "8.0.35-30"
• The Prometheus mysqld-exporter is "0.14.0-0ubuntu0.22.04.1~ppa1"
• K8s charms based on our ROCK OCI (Ubuntu 22.04 LTS - ubuntu:22.04-based)
• Principal charms supports the latest Ubuntu 22.04 LTS only

Technical notes

• Upgrade (juju refresh) is possible from revision 75+
• Use this operator together with a modern operator "MySQL Router K8s"
• Please check additionally the previously posted restrictions
• Ensure the charm requirements met

Project and community

Charmed MySQL K8s is an official distribution of MySQL. It’s an open-source project that welcomes community contributions, suggestions, fixes and constructive feedback.

• Read our Code of Conduct
• Join the Discourse forum
• Contribute and report issues
• Explore all Canonical Data Fabric solutions
• Contact us for all further questions

Revision 113

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

See also: Releases overview page, How to perform an upgrade

What's changed

This section outlines the most important features and bug fixes in this release.

Features

• Add profile-limit-memory option [PR#318]
• Add log rotation of error, general and slow query logs [PR#312][DPE-1797]
• Use Juju secret labels [PR#333][DPE-2885]
• Updated data-platform-libs for external secrets [PR#314]
• All the functionality from the previous revisions

Bug fixes

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

• Fixed dateformat 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: 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

• Upgrade (juju refresh) is possible from this revision 75+
• Use this operator together with a modern operator "MySQL Router K8s"
• Please check additionally the previously posted restrictions
• Ensure the charm requirements met

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!

Revision 99

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

See also: Releases overview page, How to perform an upgrade

What's changed

This section outlines the most important features and bug fixes in this release.

Features

• Add Juju 3 support (Juju 2 is still supported) [DPE-1790]
• Peer secrets are now stored in Juju secrets [DPE-1813]
• Charm minor upgrades and minor rollbacks [DPE-2206]
• Profiles configuration support [DPE-2154]
• Workload updated to MySQL 8.0.34 [DPE-2426]
• Support juju expose [DPE-1215]
• Add the first Prometheus alert rule (COS Loki) [PR#244]
• New documentation:
  • Architecture (HLD/LLD)
  • Upgrade section
  • Release Notes
  • Requirements
  • Users
  • Statuses
  • Development
  • Testing reference
  • Legacy charm
  • Contacts

Bug fixes

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

• DPE-1919 Fixed GKE deployment support
• DPE-1519 Stabilized integration with mysql-route-k8s
• DPE-2069 Fixed MySQL max_connections auto tune
• DPE-2225 Fixed MySQL memory allocation (use K8s Allocatable memory instead of free + consider group_replication_message_cache_size)
• DPE-988 Fixed standby units (9+ cluster members are waiting to join the cluster)
• DPE-2352 Start mysqld-exporter on COS relation only + restart upon monitoring password change
• DPE-1512 Auto-generate username/database when config values are empty (for legacy mysql relation)
• DPE-2178 Stop configuring mysql user root@% (removed as no longer necessary)

Full Changelog: rev75...rev99

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)
• Principal charms supports the latest LTS series “22.04” only.
• Subordinate charms support LTS “22.04” and “20.04” only.

Technical notes

• Upgrade (juju refresh) from the old-stable revision 75 to the current-revision 99 is NOT supported!!! The upgrade functionality is new and supported for revision 99+ only!
• Please check additionally the previously posted restrictions.
• Ensure the charm requirements met.

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!

Revision 75

A the first stable revision of Charmed MySQL K8s has been published in the 8.0/stable channel.

See also: Releases overview page

What's changed

This section outlines the most important features and bug fixes in this release.

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

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

These release notes were originally posted here.