-
Notifications
You must be signed in to change notification settings - Fork 39.7k
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
Feature/hpa upscale downscale delay configurable #42101
Feature/hpa upscale downscale delay configurable #42101
Conversation
Hi @Dmitry1987. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with 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. |
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://github.com/kubernetes/kubernetes/wiki/CLA-FAQ to sign the CLA. Once you've signed, please reply here (e.g. "I signed it!") and we'll verify. Thanks.
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. |
1 similar comment
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://github.com/kubernetes/kubernetes/wiki/CLA-FAQ to sign the CLA. Once you've signed, please reply here (e.g. "I signed it!") and we'll verify. Thanks.
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. |
|
Hi @DirectXMan12 , one of the commits was made from ubuntu VM where I was testing. And other commits from windows. So, the commit from ubuntu has an "X", it thinks no CLA signed (the username of commit "Dmitry Shmakov" different from account username "Dmitry1987"...), is it ok and will be possible to merge, or I should fix this somehow? |
You'll need to fix it. You can amend the commit while using the |
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.
A couple of minor changes, otherwise looks good in general. Thanks for doing this! :-)
pkg/apis/componentconfig/types.go
Outdated
@@ -699,6 +699,10 @@ type KubeControllerManagerConfiguration struct { | |||
// horizontalPodAutoscalerSyncPeriod is the period for syncing the number of | |||
// pods in horizontal pod autoscaler. | |||
HorizontalPodAutoscalerSyncPeriod metav1.Duration | |||
// horizontalPodAutoscalerUpscaleForbiddenWindow is a period after which next upscale allowed. |
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.
you appear to have some indentation issues here
@@ -367,7 +375,7 @@ func (a *HorizontalController) reconcileAutoscaler(hpav1Shared *autoscalingv1.Ho | |||
desiredReplicas = calculateScaleUpLimit(currentReplicas) | |||
} | |||
|
|||
rescale = shouldScale(hpa, currentReplicas, desiredReplicas, timestamp) | |||
rescale = shouldScale(a, hpa, currentReplicas, desiredReplicas, timestamp) |
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.
just make this a method of the HPA controller instead of passing the HPA as the first argument.
Punting to @piosz and @DirectXMan12. It doesn't appear that sig-instrumentation has their kubernetes team configured properly. |
Very nice ! |
44f0193
to
3306615
Compare
3306615
to
abe024b
Compare
rebased and added needed params to "legacy_horizontal_test.go" (this file didn't yet exist in my branch), so test shouldn't fail now, i hope =) . |
@k8s-bot test this |
@Dmitry1987: The following test(s) failed:
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. |
Hi guys, from latest failed tests I found and fixed all "gofmt" needed files with "gofmt -s -w". But why "kops" test failed and where to fix what, I don't understand :( , can someone take a quick look at the log here: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/pr-logs/pull/42101/pull-kubernetes-e2e-kops-aws/16450/?log#log The 3d test "/hack/verify-flags-underscore.py" failure I fixed too, added flags like it says to "hack/verify-flags/known-flags.txt"... so I just need help with kops test. Thanks :) |
b0b2309
to
c23fa18
Compare
Hi @jszczepkowski , can you help with the bot? it doesn't run test after my last push... and I don't know what is the failure in 'kops' test, maybe you can help? |
@k8s-bot test this |
92a56fb
to
c23fa18
Compare
22d6cd3
to
1f816cf
Compare
1f816cf
to
965dab3
Compare
as long as the tests pass, looks good! 👍 |
@k8s-bot ok to test |
/lgtm /approve |
Hi @deads2k, @mikedanese , do you have a minute to have a look at this PR? |
/approve |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: DirectXMan12, Dmitry1987, deads2k, mtaufen
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
Automatic merge from submit-queue (batch tested with PRs 44862, 42241, 42101, 43181, 44147) |
What this PR does / why we need it:
Makes "upscale forbidden window" and "downscale forbidden window" duration configurable in arguments of kube-controller-manager. Those are options of horizontal pod autoscaler.
Special notes for your reviewer:
Please have a look @DirectXMan12 , the PR as discussed in Slack.
Release note: