-
Notifications
You must be signed in to change notification settings - Fork 4k
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
AWS: only cache instance requirements when needed #7383
AWS: only cache instance requirements when needed #7383
Conversation
Hi @rrangith. 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 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. |
/ok-to-test |
/assign @gjtempleton |
Thanks for this |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gjtempleton, rrangith 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
/kind regression
Fixes #7102
What this PR does / why we need it:
This PR reduces the number of unneeded
DescribeLaunchTemplateVersions
API calls. Previously there was a PR that only looked for instance requirements when needed #5550. However this PR #6245 introduced a regression where now it looks for instance requirements all the time.However in the original fix PR it was stated:
This PR makes it so we again only look for instance requirements if instance type overrides are not used.
The screenshot below shows the huge increase in
DescribeLaunchTemplateVersions
API calls when we upgraded our cluster autoscaler to include the bug PR at 16:00 #6245The screenshot below is after I applied this fix at 10:30, and the
DescribeLaunchTemplateVersions
API calls dropped back down.The screenshot below shows the main loop duration spiking when the bug was introduced after 15:00 and the duration returned to normal after my fix at 10:30
Does this PR introduce a user-facing change?