Release Notes

Page last updated:

These are the release notes for VMware Tanzu™ SQL with MySQL for Kubernetes v1.0.

v1.0.0

Release Date: April 15, 2021

This is the first generally available (GA) release of VMware Tanzu™ SQL with MySQL for Kubernetes. For an overview of this product, see About Tanzu MySQL for Kubernetes.

Features

New feature in this release:

Known Issues

This release has the following issues:

  • Upgrades from beta releases are not supported: Upgrades from beta releases to the VMware Tanzu™ SQL with MySQL for Kubernetes v1.0.0 release are not supported. Download and install the latest version.
  • Scaling down a HA instance is unsupported: Creating a HA instance and scaling back to a single pod is not supported and may incur data loss. The operator does not prevent changing the property, and changing the property will result in unknown behavior. If the pods for the HA instance crash while the cluster and its metadata are still being created, the cluster may not recover automatically.
  • Pods may restart when creating a HA instance: Proxy pods may spuriously restart while the cluster is being initialized.

Limitations

  • There is no ability to configure anti-affinity for a HA instance so the pods of a HA instance may be scheduled to the same Kubernetes node.
  • Backups are only supported on S3-compatible blobstores that support the S3 ListObjectsV2 API. Notably, Google Cloud Storage (GCS) does not support this API in its S3-compatibility mode.
  • Changing spec.storageSize in a MySQL object to scale the Persistent Volume is not supported. See here for a workaround to expand the Persistent Volume.
  • Rotating MySQL system account passwords requires a manual restart of pods. For details, see here on rotating MySQL credentials.
  • TLS is required for external connections to the database. There is no supported option to disable this requirement.
  • Some common operations require an administrator to run kubectl exec to access a pod. Some examples are:
    • Checking for an HA instance that is not tolerant to additional members leaving the replication group.
    • Configuring schemas and users for an application.
  • Backups are unencrypted. Enable S3 server side encryption and ensure the MySQLBackupLocation object is configured with a secure endpoint (spec.endpoint begins with https://). For more on server side encryption, see the AWS documentation.

Compatibility

The following components are compatible with this release:

Component Version
Percona Server8.0.22–13
Percona XtraBackup8.0.23–16

v0.2.0-beta

Release Date: February 4, 2021

Features

New features and changes in this release:

  • Configure TLS: TanzuMySQL instances only accept encrypted client connections. Users can now configure a TanzuMySQL instance for TLS by creating a TLS Secret. For more information, see Configuring TLS for MySQL Instances.

  • Allow off-platform connections: Users can connect to a TanzuMySQL instance from outside the Kubernetes cluster using an external load balancer. For more information, see Connect to the MySQL Server with an External IP Address in Accessing MySQL Instances.

Known Issues

There are no known issues for this release.

Compatibility

The following components are compatible with this release:

Component Version
Percona Server8.0.22-13
Percona XtraBackup8.0.22-15

v0.1.0-beta

Release Date: December 17, 2020

Features

New features and changes in this release:

  • MySQL for Kubernetes Operator: VMware Tanzu™ SQL with MySQL for Kubernetes implements the Kubernetes Operator pattern to provision and manage on-demand TanzuMySQL instances. Tanzu MySQL for Kubernetes supports single-node MySQL database instances.

    For more information about Tanzu MySQL for Kubernetes features and compatibility, see Overview. For information about Tanzu MySQL for Kubernetes architecture, see Architecture. For more information about the Kubernetes Operator pattern, see the Kubernetes documentation.

  • Installation Using Helm: Kubernetes admins can use Helm to install the Tanzu MySQL for Kubernetes Operator. This simplifies the installation process while maintaining flexibility in configuration. For information about how to install the Tanzu MySQL for Kubernetes Operator, see Installing the Operator.

  • Backup and Restore: Tanzu MySQL for Kubernetes automates on-demand and scheduled full physical backups using the Percona XtraBackup tool. It also automates restoring and managing backups. For more information, see Backing Up and Restoring MySQL Instances.

  • Sane and Secure Server Defaults: Tanzu MySQL for Kubernetes configures MySQL server settings to optimize for security and performance. Certain server settings, like max-connections, are auto-tuned based on the compute resources and persistent storage provisioned for the Tanzu MySQL for Kubernetes instance.

    To see all MySQL server settings configured, follow the procedure in (Optional) Verify MySQL Server Settings.

  • MySQL credential management: Tanzu MySQL for Kubernetes uses Kubernetes automation to simplify rotating MySQL user credentials. For more information, see Rotating MySQL Credentials.

Compatibility

The following components are compatible with this release:

Component Version
Percona Server8.0.21–12
Percona XtraBackup8.0.14