From c09ede9e991684d946ae59ca4e0f1e394af6e5f3 Mon Sep 17 00:00:00 2001 From: Florent Poinsard <35779988+frouioui@users.noreply.github.com> Date: Mon, 29 Jan 2024 08:53:38 -0600 Subject: [PATCH] Be more explicit in release notes regarding the deprecation of certain `vitess/lite` tags (#15040) Signed-off-by: Florent Poinsard Signed-off-by: Florent Poinsard <35779988+frouioui@users.noreply.github.com> Co-authored-by: Matt Lord --- changelog/19.0/19.0.0/summary.md | 30 ++++++++++++++++++++++++------ 1 file changed, 24 insertions(+), 6 deletions(-) diff --git a/changelog/19.0/19.0.0/summary.md b/changelog/19.0/19.0.0/summary.md index 00395d26471..a4b16111adc 100644 --- a/changelog/19.0/19.0.0/summary.md +++ b/changelog/19.0/19.0.0/summary.md @@ -6,7 +6,7 @@ - **[Dropping Support for MySQL 5.7](#drop-support-mysql57)** - **[Deprecations and Deletions](#deprecations-and-deletions)** - [VTTablet Flags](#vttablet-flags) - - [MySQL binary in vitess/lite Docker image](#mysql-binary-in-lite-image) + - [Docker Image vitess/lite](#deprecation-vitess-lite-mysqld) - [Explain Statement Format](#explain-stmt-format) - **[Breaking Changes](#breaking-changes)** - [ExecuteFetchAsDBA rejects multi-statement SQL](#execute-fetch-as-dba-reject-multi) @@ -47,21 +47,39 @@ Vitess will however, continue to support importing from MySQL 5.7 into Vitess ev `--vreplication_healthcheck_topology_refresh`, `--vreplication_healthcheck_retry_delay`, and `--vreplication_healthcheck_timeout`. - The `--vreplication_tablet_type` flag is now deprecated and ignored. -#### MySQL binary in vitess/lite Docker image +#### Docker Image vitess/lite The `mysqld` binary is now deprecated in the `vitess/lite` Docker image and will be removed in a future release. +This means that the MySQL/Percona version specific image tags for the `vitess/lite` image are deprecated. -If you are currently using `vitess/lite` as your `mysqld` image in your vitess-operator deployment we invite you to use an official MySQL image such as `mysql:8.0.30`. +Below is a full list of available tags for `v19.0.0` and their deprecation status: + +| Image | Deprecated | +|---------------------------------|------------| +| `vitess/lite:v19.0.0` | NO | +| `vitess/lite:v19.0.0-mysql57` | YES | +| `vitess/lite:v19.0.0-mysql80` | YES | +| `vitess/lite:v19.0.0-percona57` | YES | +| `vitess/lite:v19.0.0-percona80` | YES | + +If you are currently using `vitess/lite` as your `mysqld` image in your vitess-operator deployment we invite you to use an official MySQL image, such as `mysql:8.0.30`. Below is an example of a kubernetes yaml file before and after upgrading to an official MySQL image: ```yaml -# before +# before: + +# the image used here includes MySQL 8.0.30 and its binaries + mysqld: - mysql80Compatible: vitess/lite:19.0.0 + mysql80Compatible: vitess/lite:v19.0.0-mysql80 ``` ```yaml -# after +# after: + +# if we still want to use MySQL 8.0.30, we now have to use the +# official MySQL image with the 8.0.30 tag as shown below + mysqld: mysql80Compatible: mysql:8.0.30 # or even mysql:8.0.34 for instance ```