-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
set loadbalancer configs before initializing the OS clients #14887
Conversation
another issue after cluster is up and running
|
|
||
hasDNS := !cluster.IsGossip() && !cluster.UsesNoneDNS() | ||
return buildClients(provider, tags, cluster.Spec.CloudProvider.Openstack, config, region, hasDNS) | ||
// used by protokube |
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.
when protokube uses this the cluster is nil always
I don't have enough OpenStack expertise to review this |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: olemarkus 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 |
…-upstream-release-1.26 Automated cherry pick of #14887: set loadbalancer configs before initializing the OS
…-of-#14887-upstream-release-1.26 Automated cherry pick of kubernetes#14887: set loadbalancer configs before initializing the OS
fixes #14886
the problem was that Openstack cloud clients were called and initialised before setting up base setup for loadbalancer.
cc @olemarkus I think you modified this part of code sometime ago.