docker: k8s release process updates

[derekperkins]

This is an update to the release process for the /docker/k8s/... images for individual binaries. This should all be pushed into Docker Hub configuration, and then release.sh can be removed I just haven't had the chance to do it. I still manually build and publish images from my machine for every release.

[derekperkins]

None of the failing tests are related to these changes

[mattlord]

We'll need to tweak the equality conditions but otherwise it seems fine. I'm not familiar with the context here though like you are. Is there anything related to this that we should do as part of the upcoming 13.0-RC and/or 13.0 (GA) releases?

Thank you!

[derekperkins]

Thanks for the review. The only thought I have about v13 is about the default debian version. I'm publishing both buster and bullseye specific images, but the unspecified tag v12.0.3 currently matches buster. I was thinking about switching that to bullseye for v13.

IIRC, nothing in official Vitess documentation uses these anymore, but anyone running from the original helm charts would use these. Docker Hub shows a few hundred thousand downloads on average for most of these, but I'm not sure how active they are recently. FWIW, I didn't publish the log4j images until I submitted this PR, so nobody was beating down the door for the updates.

[mattlord]

Thanks for the review. The only thought I have about v13 is about the default debian version. I'm publishing both buster and bullseye specific images, but the unspecified tag v12.0.3 currently matches buster. I was thinking about switching that to bullseye for v13.

I would default to pairing latest GA with latest GA here. So Vitess 13.0 on bullseye.

IIRC, nothing in official Vitess documentation uses these anymore, but anyone running from the original helm charts would use these. Docker Hub shows a few hundred thousand downloads on average for most of these, but I'm not sure how active they are recently. FWIW, I didn't publish the log4j images until I submitted this PR, so nobody was beating down the door for the updates.

Those have been deprecated in previous releases and entirely removed in v13 AFAIK. So I think we're OK there.

THANK YOU!