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.

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

Upgrading from 5.5 to 5.7 - What is best practice? #209

Closed
cfoskin opened this issue Nov 20, 2017 · 4 comments
Closed

Upgrading from 5.5 to 5.7 - What is best practice? #209

cfoskin opened this issue Nov 20, 2017 · 4 comments

Comments

@cfoskin
Copy link

cfoskin commented Nov 20, 2017

When running a 5.5 pod on openshift, what is the procedure for performing an upgrade to version 5.7? Basically I am looking at upgrading but just replacing the image with the 5.7 version will not work due to changes that need to be made to tables etc.

@cfoskin cfoskin changed the title Upgrading from 5.6 to 5.7 - What is best practice? Upgrading from 5.5 to 5.7 - What is best practice? Nov 21, 2017
@hhorak
Copy link
Member

hhorak commented Jan 31, 2018

Upstream only supports upgrading from the previous version, so when going from 5.5, you need to upgrade to 5.6 first, and only then to 5.7.

@hhorak
Copy link
Member

hhorak commented Jan 31, 2018

Some more upstream documentation is in https://dev.mysql.com/doc/refman/5.7/en/upgrading-strategies.html.

@hhorak
Copy link
Member

hhorak commented Jan 31, 2018

E.g.:

  • running mysql_ssl_rsa_setup if own SSL config is not provided is one thing.
  • maybe, as a back-up, also support extensions using /docker-entrypoint-initdb.d
  • an interesting feature is also MYSQL_ONETIME_PASSWORD, that makes the root password expired if set, although it's not clear to me what is the use case of this one, they just call it security features (docker-library/mysql@141b713).

Otherwise the containers are pretty much compatible in basic features

@phracek
Copy link
Member

phracek commented Apr 17, 2024

Closing this issue as upgrade from 5.5 -> 5.7 was deprecated a long time ago. Currently only 8.0 version is supported.
We do not have capacity to fix this issue.

Feel free to re-open it, in case you want it.
Closing it.

@phracek phracek closed this as completed Apr 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants