-
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
fix: scale up broken for providers not implementing NodeGroup.GetOptions() #6677
fix: scale up broken for providers not implementing NodeGroup.GetOptions() #6677
Conversation
…ons() Properly handle calls to `NodeGroup.GetOptions()` that return `cloudprovider.ErrNotImplemented` in the scale up path.
Thanks for reporting this! I'm wondering if we could just change all of the cloud providers that return @gjtempleton @MaciekPytel WDYT? |
@MaciekPytel volunteered for the long-term fix, merging this before that happens. /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: apricote, towca 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 |
[CA 1.30 #6677 cherry-pick] fix: scale up broken for providers not implementing NodeGroup.GetOptions()
[CA 1.28 #6677 cherry-pick] fix: scale up broken for providers not implementing NodeGroup.GetOptions()
[CA 1.29 #6677 cherry-pick] fix: scale up broken for providers not implementing NodeGroup.GetOptions()
[CA 1.28 kubernetes#6677 cherry-pick] fix: scale up broken for providers not implementing NodeGroup.GetOptions()
[CA 1.29 kubernetes#6677 cherry-pick] fix: scale up broken for providers not implementing NodeGroup.GetOptions()
What type of PR is this?
/kind bug
/kind documentation
What this PR does / why we need it:
Properly handle calls to
NodeGroup.GetOptions()
that returncloudprovider.ErrNotImplemented
in the scale up path.Which issue(s) this PR fixes:
Fixes #6676
Special notes for your reviewer:
All call sites check for
options != nil
right after the error check.Does this PR introduce a user-facing change?
I have only confirmed that this was actually affecting the Hetzner Provider, there are other providers that also return
ErrNotImplemented
, but I did not verify if there was user visible breakage for them.Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: