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
Replace DeepEqual
to Diff
compare on scheduler-binding
#109662
Replace DeepEqual
to Diff
compare on scheduler-binding
#109662
Conversation
Please note that we're already in Test Freeze for the |
@astraw99: This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
6e96a51
to
985b389
Compare
985b389
to
943ec6b
Compare
/retest |
943ec6b
to
c8c84a1
Compare
4b1365c
to
c10c850
Compare
/remove-kind bug |
/retest |
c10c850
to
d3d9258
Compare
/retest |
2 similar comments
/retest |
/retest |
/lgtm |
d3d9258
to
e3ea17a
Compare
DeepEqual
to Diff
compare on scheduler-binding
/assign @thockin |
/lgtm |
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.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: astraw99, thockin 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 |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Add retry logic when updating PVC/PV on binding pod volumes, to avoid the
FailedScheduling
backoff to improve the scheduling efficiency.Which issue(s) this PR fixes:
Fixes #109661
Special notes for your reviewer:
When scheduler encounter
FailedScheduling
, the backoff will make it slow to schedule again.Does this PR introduce a user-facing change?