-
Notifications
You must be signed in to change notification settings - Fork 183
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
chore: Clarify failed scheduling error on all disruption methods #1233
chore: Clarify failed scheduling error on all disruption methods #1233
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jonathan-innis 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 |
ea8861a
to
151a5af
Compare
Pull Request Test Coverage Report for Build 8975809269Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
151a5af
to
8094e19
Compare
0c300d2
to
9baf552
Compare
9baf552
to
bf47e5a
Compare
/lgtm |
Fixes #N/A
Description
This change updates the eventing to be more specific about why not all pods were able to schedule, similar to how Consolidation gives this information back through eventing right now.
Before PR
After PR
How was this change tested?
make presubmit
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.