Revisions 210, 211¶
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 |
|---|---|---|---|
|
210 |
8.0.39 |
3.5.4+ |
|
211 |
8.0.39 |
3.5.4+ |
If you are jumping over several stable revisions, make sure to check previous release notes before upgrading to this revision.
OCI image resources:
mysql-image=ghcr.io/canonical/charmed-mysql@sha256:aa4d9b21673d2c6e4db3dc943179bae95dd8d355790b68e4e0610da9513ee6c9
Features¶
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.51v3.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
mysqlapps in a model have the same cluster-name (PR #501 ) (DPE-4861 )Ensure that uninitialized variable not referenced in
_is_cluster_blockedhelper (PR #507 ) (DPE-5481 )Recover from pod restarts during cluster creation during setup (PR #499 )
Bug fixes¶
Fixed unit-initialized test may break when run too early (PR #491 ) (DPE-5209 )
Common credentials fixture and
exectimeout 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
mysqldexporter pebble layers (PR #505 ) (DPE-5417 )Add base in test_multi_relations to workaround
libjujubug (PR #506 ) (DPE-5480 )
Full Changelog: https://github.com/canonical/mysql-k8s-operator/compare/rev180…rev210