Fix: the pod pipeline status is incompatible with autoscaler capacity expansion #3001
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
volcano-sh-bot
added
the
size/XS
…od. It is more reasonable to set reason to Unschedulable and compatible with autoscaler capacity expansion Signed-off-by: w00568049 <[email protected]>
wangyang0616
force-pushed
the
fix_pipeline_pod_reason
branch
from
e332582
to
f9646bc
Compare
|
[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 |
volcano-sh-bot
added
the
approved
This was referenced Jul 27, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fix: Scale-out cannot be triggered by autoscaler for pods in the pipeline state #3000
If a terminating pod exists in a cluster, the pod queues up and waits for the terminating pod to release resources. Then the scheduling is successful. In the current scheduling period, pods in the pipeline state fail to be scheduled. Therefore, it is more appropriate to set the reason of pod status to Unschedulable.