Vitess MySQL Docker Image

[frouioui]

Description

This Pull Request adds a new Docker Image: vitess/mysql (visible on DockerHub here). The image is built of the main branch of the repository. Each tag of that image represent a certain MySQL version, for now in this PR only 8.0.30 (current MySQL version of Vitess) and 8.0.34 (latest 8.0 MySQL version) are available and will be built.

This PR is the first building-block to support major MySQL upgrades in the vitess-operator. Since the mysqld container image will be tagged by the underlying MySQL version, detecting a MySQL upgrade when the end-users apply a new image/tag will be possible.

In the future, the vitess/mysql image will be used by new Vitess deployments on K8S instead of using vitess/lite for the mysqld container. For now, this PR just focuses on creating the images and making them available for the incoming vitess-operator work.

Related Issue(s)

• Part of Upgrade the mysqld version and support major version upgrades in vitess-operator #14160

Checklist

• "Backport to:" labels have been added if this change should be back-ported
• Tests were added or are not required
• Did the new or modified tests pass consistently locally and on the CI
• Documentation was added or is not required

[vitess-bot]

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

• Ensure that the Pull Request has a descriptive title.
• Ensure there is a link to an issue (except for internal cleanup and flaky test fixes), new features should have an RFC that documents use cases and test cases.

Tests

• Bug fixes should have at least one unit or end-to-end test, enhancement and new features should have a sufficient number of tests.

Documentation

• Apply the release notes (needs details) label if users need to know about this change.
• New features should be documented.
• There should be some code comments as to why things are implemented the way they are.
• There should be a comment at the top of each new or modified test to explain what the test does.

New flags

• Is this flag really necessary?
• Flag names must be clear and intuitive, use dashes (-), and have a clear help text.

If a workflow is added or modified:

• Each item in Jobs should be named in order to mark it as required.
• If the workflow needs to be marked as required, the maintainer team must be notified.

Backward compatibility

• Protobuf changes should be wire-compatible.
• Changes to _vt tables and RPCs need to be backward compatible.
• RPC changes should be compatible with vitess-operator
• If a flag is removed, then it should also be removed from vitess-operator and arewefastyet, if used there.
• vtctl command output order should be stable and awk-able.

[shlomi-noach]

Nice!

[GuptaManan100]

Lgtm!