Skip to content

Conversation

@mich-elle-luna
Copy link
Collaborator

  • Add clear explanation of node labeling requirements for rack-awareness
  • Emphasize that ALL eligible nodes must be labeled with chosen label
  • Explain what eligible nodes are (nodes where RS pods can be scheduled)
  • Suggest topology.kubernetes.io/zone as commonly available label
  • Clarify that not all platforms have this label by default
  • Update example to use current topology.kubernetes.io/zone instead of deprecated failure-domain.beta.kubernetes.io/zone
  • Fix kubectl command formatting (add space after $)
  • Add warning about operator failing if nodes are missing labels

Addresses DOC-1815

- Add clear explanation of node labeling requirements for rack-awareness
- Emphasize that ALL eligible nodes must be labeled with chosen label
- Explain what eligible nodes are (nodes where RS pods can be scheduled)
- Suggest topology.kubernetes.io/zone as commonly available label
- Clarify that not all platforms have this label by default
- Update example to use current topology.kubernetes.io/zone instead of deprecated failure-domain.beta.kubernetes.io/zone
- Fix kubectl command formatting (add space after $)
- Add warning about operator failing if nodes are missing labels

Addresses DOC-1815
@github-actions
Copy link
Contributor

Copy link
Contributor

@kaitlynmichael kaitlynmichael left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggested some wording changes to simplify and make sure it's in active voice. Thanks for tackling this!

@mich-elle-luna mich-elle-luna merged commit d16adb1 into main Jul 1, 2025
5 checks passed
@mich-elle-luna mich-elle-luna deleted the DOC-1815 branch July 1, 2025 20:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants