Update the description of TopologySpreadConstraints's matchLabelKeys to align with the design change#49607
Conversation
👷 Deploy Preview for kubernetes-io-vnext-staging processing.
|
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
sftim
left a comment
There was a problem hiding this comment.
My main feedback here is not to use a warning callout, as warning is too prominent.
| A null or empty list means only match against the `labelSelector`. | ||
|
|
||
| {{< caution >}} | ||
| It's not recommended to use `matchLabelKeys` with labels that might be updated directly on pods. |
There was a problem hiding this comment.
Slightly better: The Kubernetes project recommends against using…
(because we favor the active voice)
|
LGTM label has been added. DetailsGit tree hash: 42a82068fa8e633bf5b8cce31dda86d5c2041a1e |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sftim The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Description
This PR updates the description of TopologySpreadConstraints's
matchLabelKeysto align with the design change by kubernetes/kubernetes#129874.This also includes the deprecation notice related to
matchLabelKeys.related: