-
Notifications
You must be signed in to change notification settings - Fork 39
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
DOC-967 Add more details to the node upgrade doc for Kubernetes #960
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for redpanda-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
SE([System Event]):::systemAction | ||
end | ||
|
||
%% -- MAIN FLOWCHART -- |
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.
Love the flow chart--very helpful!
One thing...
I'm not a designer, but the layout here feels a bit off.
Not sure I understand why the legend appears aligned with the diagram. I would expect it to site above it.
Then, the Start circle and everything underneath would be center-aligned underneath. This would leave a lot less blank space here. Thoughts on having borders around these diagrams?
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.
Please have a look at comment re diagram. Otherwise, well-written!
Co-authored-by: Joyce Fee <[email protected]>
Sorry for taking so long on this one. IIRC this ask was kicked off as we were trying to determine how best to migrate an Azure cluster as we had written up some instructions. That operation ended up going the worst way imaginable which got me thinking more deeply about this topic, especially because the landscape of self hosted is much broader than cloud. Here's a heavily annotated flow chart that should capture most cases. It doesn't touch on how to perform the operation manually, just whether or not it needs to be manual 😓 |
Description
Review deadline: 25 Jan
We recently had a P1 related to ephemeral data loss due to how Azure handles automated node upgrades. We already implemented a clarification in docs to recommend disabling automated node upgrades: https://redpandadata.atlassian.net/browse/DOC-875
However, @chrisseto and I met and discussed improvements we can make to the node upgrade guide, including:
Page previews
https://deploy-preview-960--redpanda-docs-preview.netlify.app/current/upgrade/k-upgrade-kubernetes/
Checks