Skip to content
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

ManagedAPIServerLoadBalancer flag doesn't work as expected #974

Closed
malstoun opened this issue Aug 20, 2021 · 5 comments · Fixed by #978
Closed

ManagedAPIServerLoadBalancer flag doesn't work as expected #974

malstoun opened this issue Aug 20, 2021 · 5 comments · Fixed by #978
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug.

Comments

@malstoun
Copy link

/kind bug

What steps did you take and what happened:
We don’t have loadbalancer in our Openstack installation. If I set ManagedAPIServerLoadBalancer: false to disable load balancer usage I see an error failed to create load balancer service client: No suitable endpoint could be found in the service catalog. in logs and reconciliation fails.

What did you expect to happen:
I expected to see successful reconciliation without load balancer errors. I think that if I set ManagedAPIServerLoadBalancer: false, controller shouldn’t try to create loadBalancerService.

Anything else you would like to add:
Discussion in slack: https://kubernetes.slack.com/archives/CFKJB65G9/p1628930844032400

Environment:

  • Cluster API Provider OpenStack version: v0.4.0
  • Cluster-API version: v0.4.0
  • OpenStack version: N/A
  • Minikube/KIND version: v0.11.1
  • Kubernetes version (use kubectl version): v1.21.1
  • OS (e.g. from /etc/os-release): 20.04.2 LTS (Focal Fossa)
@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Aug 20, 2021
@chrischdi
Copy link
Member

I think there are three occurencies where the loadbalancer.NewService function is getting used without checking if ManagedAPIServerLoadBalancer was set:

We have to adjust the code to only call loadbalancer.NewService if we really want to use the client (ManagedAPIServerLoadBalancer==true).

@chrischdi
Copy link
Member

/help

@k8s-ci-robot
Copy link
Contributor

@chrischdi:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Aug 22, 2021
@jichenjc
Copy link
Contributor

in addition, we need disable
https://github.com/kubernetes-sigs/cluster-api-provider-openstack/blob/master/hack/ci/devstack-default-cloud-init.yaml.tpl#L56

when doing CI without LB case, thus, we should be able to find this issue early

@raildo
Copy link

raildo commented Aug 23, 2021

Just adding my 2 cents in this thread, this is a regression comparing with the CAPO v0.3.3, since we were able to have a Cluster API deployed without LB and then creating an external LB object. I believe that we should keep the same behavior as we had before.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants