-
Notifications
You must be signed in to change notification settings - Fork 39.9k
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
if loadbalancer section is not defined in cloudconfig, do not init support #65781
Conversation
…ize lb support use reflect because structs with []string cannot be compared
one thing that I am thinking: is there possibility to use openstack lbaas currently with empty config? I tried to look opts in https://github.com/kubernetes/kubernetes/blob/master/pkg/cloudprovider/providers/openstack/openstack.go#L93-L105 and for me it looks like all fields are optional? https://kubernetes.io/docs/concepts/cluster-administration/cloud-providers/#openstack So if we merge this PR, it might break things in some users. Any ideas how we can really check is this section added to config or not? Gfg does not have feature to check "does section exist"? |
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.
/approve
/kind bug |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims, FengyunPan2, zetaab 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 |
@zetaab can you update the release notes to say |
Automatic merge from submit-queue (batch tested with PRs 65902, 65781). If you want to cherry-pick this change to another branch, please follow the instructions here. |
What this PR does / why we need it: if LoadBalancer section is not defined in cloudconfig, we should not initialize loadbalancer support for openstack cloudprovider.
Which issue(s) this PR fixes:
Fixes #65775
Special notes for your reviewer:
Release note: