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.

Sign up for GitHub

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

Jump to bottom

Upgrade Orchestrator? #427

Closed
abh opened this issue Nov 7, 2019 · 2 comments
Closed

Upgrade Orchestrator? #427

abh opened this issue Nov 7, 2019 · 2 comments

Comments

@abh
Copy link
Contributor

abh commented Nov 7, 2019 •
edited

(I'm still fussing with the 3 clusters that lost their replicas when upgrading the mysql-operator last weekend).

One of the clusters ran into the MySQL bug that's worked around in this openark/orchestrator#807

I think it's included in the Orchestrator releases from this summer; but mysql-operator includes the one from January.
@AMecea
Copy link
Contributor

AMecea commented Nov 7, 2019

Hi @abh,

This is a good idea, I will love to review and merge a PR that does that.

Best regards,

@abh
Copy link
Contributor Author

abh commented Nov 8, 2019

See #428

@AMecea AMecea closed this as completed Nov 14, 2019
chapsuk pushed a commit to chapsuk/mysql-operator that referenced this issue Oct 16, 2023
@GuptaManan100
Merge pull request bitpoke#427 from planetscale/create-pull-request/p…
564d915 
…atch

Upgrade Vitess Dependency to Latest
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@abh @AMecea