Move Pod Topology Spread Constraints into scheduling

These constraints apply specifically to the mechanism for placing Pods
onto nodes (that is, scheduling).
This commit is contained in:
Tim Bannister
2022-05-10 11:01:05 +01:00
parent bde5fe9e2a
commit 6700656cb4
11 changed files with 12 additions and 10 deletions
@@ -67,7 +67,7 @@ Let's see an example of a cluster to understand this API.
As the feature name "PodTopologySpread" implies, the basic usage of this feature
is to run your workload with an absolute even manner (maxSkew=1), or relatively
even manner (maxSkew>=2). See the [official
document](/docs/concepts/workloads/pods/pod-topology-spread-constraints/)
document](/docs/concepts/scheduling-eviction/topology-spread-constraints/)
for more details.
In addition to this basic usage, there are some advanced usage examples that