Skip to content
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

Document limitations around default topology spread constraints #48798

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -529,6 +529,11 @@ profiles:
whenUnsatisfiable: ScheduleAnyway
defaultingType: List
```

If you are using the default cluster-autoscaler make sure not to use `DoNotSchedule` as it
[does not know about custom default constraints](https://github.com/kubernetes/autoscaler/issues/3879)
or you might end up with unschedulable pods.

### Built-in default constraints {#internal-default-constraints}

{{< feature-state for_k8s_version="v1.24" state="stable" >}}
Expand Down Expand Up @@ -621,6 +626,9 @@ section of the enhancement proposal about Pod topology spread constraints.
You can work around this by using a cluster autoscaling tool that is aware of
Pod topology spread constraints and is also aware of the overall set of topology
domains.
- [cluster-autoscaler does not know about custom default constraints](https://github.com/kubernetes/autoscaler/issues/3879)
and will ignore them. If you use `DoNotSchedule` in your constraints this will result
in unschedulable pods.

## {{% heading "whatsnext" %}}

Expand Down