-
Notifications
You must be signed in to change notification settings - Fork 963
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
Remove Undetermined
reason to fix cluster autoscaler compatibility
#2602
Remove Undetermined
reason to fix cluster autoscaler compatibility
#2602
Conversation
bce9890
to
968cb35
Compare
/assign @wpeng102 |
@tgaddair The test file job_info_test.go is also needed to update to fix the CI error :) |
44ec006
to
ebefca0
Compare
Signed-off-by: Travis Addair <[email protected]>
Signed-off-by: Travis Addair <[email protected]>
Signed-off-by: Travis Addair <[email protected]>
ebefca0
to
ab74336
Compare
Signed-off-by: Travis Addair <[email protected]>
Thanks for taking a look @william-wang! Tests are updated and everything is passing. |
That's great :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: william-wang The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Fixes #1775.
#1672 introduced fine-grained Reasons to give users more context about why scheduling did not succeed. However, this breaks compatibility with cluster autoscalers like Karpenter, which rely on the reason being set to
Unschedulable
to trigger scale-up, and the more fine-grained reasonUndetermined
causes the autoscaler to skip the pod.This PR removes this reason to fix support for cluster autoscalers.