-
Notifications
You must be signed in to change notification settings - Fork 47
DOC-875 Add section on disabling automatic node maintenance and OS upgrades #941
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
Conversation
…grades - Added guidance for manually managing worker nodes and OS upgrades in production environments. - Explained the importance of managing Redpanda as a stateful workload to prevent disruptions. - Included Kubernetes-specific instructions for disabling automatic node maintenance on Azure, GCP, and AWS. - Provided general recommendations for scheduling node maintenance and using controlled upgrade strategies like blue-green migrations.
✅ Deploy Preview for redpanda-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
@JakeSCahill Is it possible to somehow also link to this in Next Steps section of Overview? This seems like the most logical place to discover this if you were new to Redpanda K8s. I think one would first go to Overview, then go directly to installing on K8s if I were to follow what's being documented without following the nav bar. |
|
Is it possible also to include a blurb about moving from Managed to Unmanaged Node images are also susceptible to downtime and thus its advisable to deploy with Unmanaged node upgrades for now? |
|
Thanks @david-yu - I made some improvements based on your feedback |
|
Looks good thank you! |
|
|
||
| ifdef::env-kubernetes[] | ||
| NOTE: The Redpanda Helm chart configures xref:reference:k-redpanda-helm-spec.adoc#statefulset-podantiaffinity[`podAntiAffinity` rules] to make sure that each Redpanda broker runs on its own {node}. | ||
| NOTE: The Redpanda Helm chart configures xref:reference:k-redpanda-helm-spec.adoc#statefulset-podantiaffinity[`podAntiAffinity` rules] to make sure that each Redpanda broker runs on its own node. |
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.
Does "rules" need to be included in the link? Destination heading only has the name shown here.
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.
The link goes to the definition of the default rules. The rules are defined in a config called podAntiAffinity.
Co-authored-by: Joyce Fee <[email protected]>
Description
Resolves https://github.com/redpanda-data/documentation-private/issues/2813
Review deadline: 10 Jan
Page previews
Checks