Release Notes#

#v4.3.2

#New and Optimized Features

#MySQL-PXC Removal

The deprecated MySQL-PXC architecture has been removed. MySQL-MGR is now the sole supported topology. Existing PXC instances continue running but are no longer reconciled by the MySQL operator. Migrate any remaining PXC instances to MySQL-MGR before upgrading. See Migrate MySQL-PXC to MySQL-MGR for the full procedure.

#Deployment on Non-TopoLVM Environments

You can now deploy MySQL-MGR clusters on environments that do not provide TopoLVM, such as MicroOS or bare-metal clusters, by using a manually provisioned local StorageClass. See Deploy MySQL-MGR Without TopoLVM.

#Backup Reliability

• S3 backups for large files now use multipart upload to avoid the EntityTooLarge error.
• A stale backup annotation on a MySQL cluster is automatically cleared when the referenced backup has already completed, preventing new backups from being incorrectly rejected.

#SSL with Strict Security Mode

SSL volumes and certificate mounts are now provisioned correctly when both SSL and strict security mode are enabled, eliminating the unavailable-state regression that affected SSL-enabled MGR clusters in earlier 4.3 builds.

#RBAC Hardening

RBAC permissions for MGR cluster components were tightened to follow least-privilege principles.

#Fixed Issues

• Occasionally, when an MGR instance is created to create an incremental backup, the backup fails due to a GTID calculation error.
  This issue has been fixed in Alauda Database Service for MySQL v4.2.0.
• Occasionally, when an MGR instance is created to create an incremental backup, the backup fails due to a GTID calculation error.
  This issue has been fixed in Alauda Database Service for MySQL v4.2.0.

#Known Issues

No issues in this release.