Closed jai closed 3 years ago
Looks like something has changed in the autobuild config on docker. All vitess/lite images off main are being built with mysql57 instead of the correct flavor. I have fixed the configuration and queued up new builds. v11.0.0-mysql80 was built with the correct underlying mysql.
Thanks @deepthi - what would you think about me PR'ing/adding examples to the examples folder to include a mysql8 cluster? or let me know if another location would be more appropriate.
I'd probably want to add a mention on the Vitess Operator for Kubernetes page as well.
I think both examples and website docs will be good. Thank you for volunteering!
I just checked the most recent docker build for mysql80 and it built with the correct steps, so it should be good now.
Yes, now running MySQL Ver 8.0.23
$ /usr/sbin/mysqld --version
/usr/sbin/mysqld Ver 8.0.23 for Linux on x86_64 (MySQL Community Server - GPL)
Thanks for the help @deepthi !
@deepthi created issue here: https://github.com/vitessio/vitess/issues/8627 - I can't assign myself though, appreciate if you can assign me?
@jai Can you explain at least, how you solved this issue?
Hi - not sure if I'm missing something on how to set up Vitess Operator to use MySQL 8.0?
Ref Slack thread: https://vitess.slack.com/archives/CNE9WP677/p1628481964005800
Overview of the Issue
Using the Vitess Operator to set up a
VitessCluster
with the following spec:The
mysqld
version running on thevttablet
andvtctld
Pods still return their version as 5.7.Reproduction Steps
Steps to reproduce this issue, example:
VitessCluster
resource using the above spec/imagesvttablet
orvtctld
PodBinary version
Using the Vitess operator.yaml from main
Operating system and Environment details
Running on AWS EKS.