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
[KEP-3521] Part 2: Core scheduling implementation #113275
Conversation
cc @ahg-g this is the 2nd PR of the overall KEP impl. There is a third PR upcoming to cover integration/e2e tests. |
This PR may require API review. If so, when the changes are ready, complete the pre-review checklist and request an API review. Status of requested reviews is tracked in the API Review project. |
7dbe124
to
4de7b6b
Compare
This PR may require stable metrics review. Stable metrics are guaranteed to not change. Please review the documentation for the requirements and lifecycle of stable metrics and ensure that your metrics meet these guidelines. |
/retest |
1 similar comment
/retest |
continue | ||
} | ||
pInfo.UnschedulablePlugins.Insert(pl.Name()) | ||
klog.InfoS("PreEnqueue failed", "pod", klog.KObj(pod), "plugin", pl.Name(), "error", s.AsError()) |
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.
ErrorS
instead?
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.
also, should we log only on Error status?
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.
I'd do klog.V(5).InfoS
on failures and klog.ErrorS
on unexpected errors, which is consistent with what we did in other extension point:
kubernetes/pkg/scheduler/schedule_one.go
Lines 145 to 150 in a0b69ec
if status.Code() == framework.Error { | |
klog.ErrorS(nil, "Status after running PostFilter plugins for pod", "pod", klog.KObj(pod), "status", status) | |
} else { | |
fitError.Diagnosis.PostFilterMsg = status.Message() | |
klog.V(5).InfoS("Status after running PostFilter plugins for pod", "pod", klog.KObj(pod), "status", status) | |
} |
pkg/scheduler/framework/plugins/defaultenqueue/default_enqueue.go
Outdated
Show resolved
Hide resolved
/remove-sig api-machinery |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Huang-Wei, liggitt, logicalhan 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 |
@ahg-g almost all comments have been addressed. Let me know if it's good to squash. |
looks good, please squash |
- Add PreEnqueuePlugin to Scheduler Framework - Implement PreEnqueuePlugin in scheduler queue - Implementation of SchedulingGates plugin - Metrics
/retest |
@ahg-g commits squashed and CI is green now. |
/hold cancel |
/retest |
@Huang-Wei: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
/retest |
As discussed for other plugins, a plugin that only does some work when a certain feature gate is enabled should only get included in the default configuration when that feature gate is enabled. The plugin still needs to check the feature gate itself because it might be enabled explicitly in some configuration, with the feature gate off. Ref: - kubernetes#113705 - kubernetes#113275 (comment)
As discussed for other plugins, a plugin that only does some work when a certain feature gate is enabled should only get included in the default configuration when that feature gate is enabled. The plugin still needs to check the feature gate itself because it might be enabled explicitly in some configuration, with the feature gate off. Ref: - kubernetes#113705 - kubernetes#113275 (comment)
As discussed for other plugins, a plugin that only does some work when a certain feature gate is enabled should only get included in the default configuration when that feature gate is enabled. The plugin still needs to check the feature gate itself because it might be enabled explicitly in some configuration, with the feature gate off. Ref: - kubernetes#113705 - kubernetes#113275 (comment)
As discussed for other plugins, a plugin that only does some work when a certain feature gate is enabled should only get included in the default configuration when that feature gate is enabled. The plugin still needs to check the feature gate itself because it might be enabled explicitly in some configuration, with the feature gate off. Ref: - kubernetes#113705 - kubernetes#113275 (comment)
What type of PR is this?
/kind feature
/sig scheduling
What this PR does / why we need it:
This PR is rebased atop Part 1 (#113274), covering the following logic:
Which issue(s) this PR fixes:
Part of #113269
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: