planetscale / planetscale/vitess-operator
Support major MySQL version upgrade in the operator
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 372
- Forks
- 102
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 15
Description
We should be able to support major MySQL version upgrade in the vitess-operator. https://github.com/planetscale/vitess-operator/pull/361 adds support for minor version upgrades.
The issue with doing a major version upgrade lies in the different collations used by MySQL 5.7 and 8.0. During the upgrade process, VReplication fails because of the default collation of the primary mysqld (mysql8.0) does not exists on the replica mysqld (mysql5.7).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing PR #361, which added minor version upgrade support, then trace how the Vitess operator handles the upgrade and VReplication process. Done means a major MySQL 5.7-to-8.0 upgrade completes despite the differing default collations, without VReplication failing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, mysql
- Domain
- databases, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100