-
Notifications
You must be signed in to change notification settings - Fork 269
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
fix: don't set vm entry as nil in cache when vm is in Deleting state to avoid VMSSList throttling #2060
fix: don't set vm entry as nil in cache when vm is in Deleting state to avoid VMSSList throttling #2060
Conversation
✅ Deploy Preview for kubernetes-sigs-cloud-provide-azure canceled.
|
✅ Deploy Preview for warm-cascaron-bb779f canceled.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andyzhangx 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 |
Coverage increased (+0.004%) to 79.808% when pulling 5272185bab3739d696c919183b657ec40da0002d on andyzhangx:deleting-set-nil-issue into 8ffd413 on kubernetes-sigs:master. |
/assign @nilo19 @MartinForReal |
5272185
to
a1027fb
Compare
/retest |
2 similar comments
/retest |
/retest |
/lgtm |
What type of PR is this?
/kind bug
What this PR does / why we need it:
fix: don't set vm entry as nil in cache when vm is in Deleting state to avoid VMSSList throttling
When VM is in Deleting state, original behavior is setting as nil, and then with this PR(#1578), Deleting state VM will be not found in cache, then it would trigger VMSSList again, found VM is still in Deleting state, return nil, trigger VMSSList again and again, finally get VMSSList throttling.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: