-
Notifications
You must be signed in to change notification settings - Fork 195
ECK: mention PodTopologyLabelsAdmission #4660
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
✅ Vale Linting ResultsNo issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
🔍 Preview links for changed docs |
67d227d to
932d970
Compare
yetanothertw
left a comment
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.
Thank you for making these changes! 🪴
LGTM with one minor suggestion for style and clarity.
deploy-manage/deploy/cloud-on-k8s/advanced-elasticsearch-node-scheduling.md
Outdated
Show resolved
Hide resolved
…scheduling.md Co-authored-by: Vlada Chirmicci <[email protected]>
Summary
Adds an informational note about Kubernetes 1.35 changes that simplify topology label configuration. With the PodTopologyLabelsAdmission feature enabled by default in K8s 1.35+, users may no longer need the eck.k8s.elastic.co/downward-node-labels annotation since topology labels are automatically propagated from nodes to Pods.
Generative AI disclosure