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

Upgrade MySQL to 8.0 #391

Closed
3 tasks
gkcalat opened this issue Sep 27, 2022 · 2 comments · Fixed by #394
Closed
3 tasks

Upgrade MySQL to 8.0 #391

gkcalat opened this issue Sep 27, 2022 · 2 comments · Fixed by #394
Assignees

Comments

@gkcalat
Copy link
Contributor

gkcalat commented Sep 27, 2022

As MySQL 8 is a default version in GCP and katib, it was proposed to upgrade MySQL version to 8.0.

    cc @gkcalat for upgrading MySQL version in the future release.

Originally posted by @zijianjoy in #382 (comment)

Additional docs:

Consideration:

  • Is it a breaking change for users using KF 1.6.0 and prior?
  • Do we need to upgrade tier?
  • Do we need to enforce utf8 charset as MySQL8 migrated to utf8mb4?
@gkcalat gkcalat self-assigned this Sep 27, 2022
@gkcalat
Copy link
Contributor Author

gkcalat commented Sep 27, 2022

/cc @zijianjoy

@zijianjoy
Copy link
Collaborator

FYI, MLMD and Argo have already migrated to MySQL 8. And KFP on AI Platform Pipelines also allows us to configure MySQL 8 connection too. That means that the usability on MySQL 8 should be verified already. However, we need to do the followings:

  1. Upgrade KFP base mysql deployment to v8: https://github.com/kubeflow/pipelines/blob/master/manifests/kustomize/third-party/mysql/base/mysql-deployment.yaml#L29
  2. Validate the upgrade from v5 to v8 in full Kubeflow mode so we can determine whether it is a breaking change.
  3. I think there should still be some degree of breaking changes any way, so we need to update documentation about it.

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

Successfully merging a pull request may close this issue.

2 participants