-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🌱 propagate ctx to retryWithExponentialBackoff in clusterctl #9437
Conversation
/hold for squash |
1779aec
to
3aa37b2
Compare
squashed! |
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.
/lgtm
/assign @fabriziopandini
LGTM label has been added. Git tree hash: 1656686d50a7976e532dbcef59189f90713c0cc9
|
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.
/lgtm
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer 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 this PR does / why we need it: In the spirit of of #8733, this PR adds a
context.Context
parameter to theretryWithExponentialBackoff
helper used throughout clusterctl. This allows backoff to short circuit if a context is canceled during a sleep between retries instead of only while the retried function is running. The primary change is to call apimachinery'swait.ExponentialBackoffWithContext
instead ofwait.ExponentialBackoff
.Almost every call to this helper already had a context available, but there are a couple that needed
context.Background()
s.Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
/area clusterctl