Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Be more explicit in release notes regarding the deprecation of certain vitess/lite tags #15040

Merged
merged 4 commits into from
Jan 29, 2024
Merged

Be more explicit in release notes regarding the deprecation of certain vitess/lite tags #15040

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
3a1c69f
Be more explicit regarding the deprecation of version specific vitess…
frouioui Jan 25, 2024
60f1e66
Be even more explicit in the given code example
frouioui Jan 25, 2024
d3cce7b
Update changelog/19.0/19.0.0/summary.md
frouioui Jan 26, 2024
8820dc9
Merge remote-tracking branch 'origin/main' into fix-mysqld-deprecatio…
frouioui Jan 29, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 24 additions & 6 deletions changelog/19.0/19.0.0/summary.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)
- **[Breaking Changes](#breaking-changes)**
- [ExecuteFetchAsDBA rejects multi-statement SQL](#execute-fetch-as-dba-reject-multi)
- **[New Stats](#new-stats)**
Expand Down Expand Up @@ -45,21 +45,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.

#### <a id="mysql-binary-in-lite-image"/>MySQL binary in vitess/lite Docker image
#### <a id="deprecation-vitess-lite-mysqld"/>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 encapsulates MySQL 8.0.30 and its binaries
frouioui marked this conversation as resolved.
Show resolved Hide resolved

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
```
Expand Down
Loading