-
Notifications
You must be signed in to change notification settings - Fork 36
⚠️ Work in progress ⚠️ MariaDB Enterprise Operator 25.08 #81
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
base: main
Are you sure you want to change the base?
Conversation
mariadb-mmontes
commented
Aug 19, 2025
3b5a8ec
to
19bc421
Compare
7d1ea54
to
03deabe
Compare
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.
Some suggestions and a small typo
```bash | ||
helm uninstall mariadb-enterprise-operator | ||
``` | ||
Alternatively, you may only downscale and delete the webhook configurations: |
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.
I wonder if it will be easier to provide a single main migration path and provide "Alternatives" in a separate secition? This should make it more readable
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.
I think jumping to an Alternatives
section would break the flow. The idea is that we have a no brainer guide for migrating, yet, giving some options to not fully uninstall de operator.
|
||
This guide illustrates, step by step, how to migrate to `25.8.0` from previous versions. | ||
|
||
- Uninstall you current `mariadb-enterprise-operator` for preventing conflicts: |
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.
I wonder if we can set these as Headers ##
to make clear distinction if each section?
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.
I think I've tried this approach some time ago in the community operator, but, I was feeling that the headers were kindof redundant, the comands are mostly self-explanatory, but I could be wrong. Thanks for the feedback