-
Notifications
You must be signed in to change notification settings - Fork 236
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
Update karpenter_scheduler_unschedulable_pods_count #2006
base: main
Are you sure you want to change the base?
Update karpenter_scheduler_unschedulable_pods_count #2006
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: priyanshikhetwani The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Welcome @priyanshikhetwani! |
Hi @priyanshikhetwani. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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-sigs/prow repository. |
Pull Request Test Coverage Report for Build 13399319610Details
💛 - Coveralls |
@@ -219,9 +219,6 @@ func (s *Scheduler) Solve(ctx context.Context, pods []*corev1.Pod) Results { | |||
// had 5xA pods and 5xB pods were they have a zonal topology spread, but A can only go in one zone and B in another. | |||
// We need to schedule them alternating, A, B, A, B, .... and this solution also solves that as well. | |||
errors := map[*corev1.Pod]error{} | |||
// Reset the metric for the controller, so we don't keep old ids around | |||
UnschedulablePodsCount.DeletePartialMatch(map[string]string{ControllerLabel: injection.GetControllerName(ctx)}) |
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.
Do we need to drop the controller label when this metric is set too?
karpenter_scheduler_unschedulable_pods_count has unnecessary DeletePartialMatch in the scheduler
Fixes #1993
Description
karpenter_scheduler_unschedulable_pods_count is set at the top of every provisioning loop -- realistically, this value is continually set as provisioning loops are run and we shouldn't need this metric in the disruption loops (because we expect that there are going to be cases with consolidation where pods won't schedule) -- we should remove the DeletePartialMatch as well as the controller label on the metric since it's unneccesary
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.