-
Notifications
You must be signed in to change notification settings - Fork 13
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
add(mysql): upgrade and failover procedures #239
base: main
Are you sure you want to change the base?
Conversation
Deploying aiven-docs with
|
Latest commit: |
a2b1eac
|
Status: | ✅ Deploy successful! |
Preview URL: | https://44201711.aiven-docs.pages.dev |
Branch Preview URL: | https://dorota-mysql-upgrade-failove.aiven-docs.pages.dev |
ce87aeb
to
d7cbc92
Compare
This procedure doesn't apply to major version upgrades, which can be performed from the | ||
[Aiven Console](https://console.aiven.io): service page > | ||
<ConsoleLabel name="servicesettings"/> > **Service management** > | ||
<ConsoleLabel name="actions"/> > **Upgrade version**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ideally, we should never repeat this. That should be a link on how to perform major upgrades, not a repeat. The day the UI changes, that'll create maintenance issues.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're not repeating :-) There's no MySQL upgrade doc, so I just wanted to give at least a short hint how to do that here. It's better than no info at all, which is the case a the moment. Or shall I remove it ?
b23df80
to
b3584a4
Compare
1b95741
to
d396702
Compare
Signed-off-by: Arthur <arthur.flageul-marquez@aiven.io>
https://aiven.atlassian.net/browse/DOC-989
Checklist
/docs/
.