-
Notifications
You must be signed in to change notification settings - Fork 40.1k
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
Ensure backoff step is set to 1 for Azure armclient #94180
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: feiskyer 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 |
/priority important-soon |
/assign @nilo19 |
Awesome, thanks for the fix @feiskyer ! |
/retest |
2 similar comments
/retest |
/retest |
/retest |
/lgtm |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Ensure backoff step is set to 1 for Azure armclient. When the clients passed in a non-nil clientBackoff, the backoff steps may be 0, which would cause client panic:
kubernetes/staging/src/k8s.io/legacy-cloud-providers/azure/clients/armclient/azure_armclient.go
Lines 65 to 71 in 14a1106
This PR fixes the issue by ensuring the backoff step is 1 on such case.
Which issue(s) this PR fixes:
Refer #94078 (comment).
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: