The need to include a mysqlbinlog binary in a k8s deployment about vitess

[shlomi-noach]

Thank you @GenLN. More context:

This is a followup to #14765. For the purpose of point in time recoveries, the mysqlbinlog binary is required.

I believe this is a documentation change. Modify the changelog to explicitly call out mysqlbinlog.

[mattlord]

Confirmed:

❯ docker run --entrypoint /bin/bash -it mysql:8.0.36 -- command -v mysql
/usr/bin/mysql
❯ docker run --entrypoint /bin/bash -it mysql:8.0.36 -- command -v mysqlbinlog
❯ docker run --entrypoint /bin/bash -it mysql:8.0.36 -- command -v mysqld
/usr/sbin/mysqld

/cc @frouioui as this may complicate our plans to remove MySQL from the vitess/lite images.

[shlomi-noach]

Yeah, the binaries in that image are:

mysql
mysql-secret-store-login-path
mysql_config
mysql_migrate_keyring
mysql_ssl_rsa_setup
mysql_tzinfo_to_sql
mysql_upgrade
mysqladmin
mysqldump
mysqlpump
mysqlsh

[deepthi]

Thank you @GenLN. More context:

This is a followup to #14765. For the purpose of point in time recoveries, the mysqlbinlog binary is required.

I believe this is a documentation change. Modify the changelog to explicitly call out mysqlbinlog.

Beyond that we will need to package mysqlbinlog in our published docker images for k8s users. But as @mattlord pointed out, this complicates things. Which version of mysqlbinlog do we bundle into the docker image?

[frouioui]

I have proposed a fix in #15775 which adds mysqlbinlog back to the lite image while avoiding to re-install all of mysql in the final image.