Skip to content

Commit 33d2511

Browse files
Tamilselvantengqm
andauthored
Fix stale info about spread minDomains (#42758)
* Stale information about minDomains * Update topology-spread-constraints.md * Update topology-spread-constraints.md * Update topology-spread-constraints.md * Update content/en/docs/concepts/scheduling-eviction/topology-spread-constraints.md Co-authored-by: Qiming Teng <[email protected]> --------- Co-authored-by: Qiming Teng <[email protected]>
1 parent 1a32094 commit 33d2511

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

content/en/docs/concepts/scheduling-eviction/topology-spread-constraints.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -97,8 +97,11 @@ your cluster. Those fields are:
9797
nodes match the node selector.
9898

9999
{{< note >}}
100-
The `minDomains` field is a beta field and disabled by default in 1.25. You can enable it by enabling the
101-
`MinDomainsInPodTopologySpread` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/).
100+
The `MinDomainsInPodTopologySpread` [feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
101+
enables `minDomains` for pod topology spread. Starting from v1.28,
102+
the `MinDomainsInPodTopologySpread` gate
103+
is enabled by default. In older Kubernetes clusters it might be explicitly
104+
disabled or the field might not be available.
102105
{{< /note >}}
103106

104107
- The value of `minDomains` must be greater than 0, when specified.

0 commit comments

Comments
 (0)