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

Cannot delete last LoadBalancer service when using VMO #374

Closed
kon-angelo opened this issue Sep 21, 2021 · 2 comments · Fixed by #398
Closed

Cannot delete last LoadBalancer service when using VMO #374

kon-angelo opened this issue Sep 21, 2021 · 2 comments · Fixed by #398
Labels
area/control-plane Control plane related kind/bug Bug platform/azure Microsoft Azure platform/infrastructure priority/3 Priority (lower number equals higher priority)

Comments

@kon-angelo
Copy link
Contributor

How to categorize this issue?

/area control-plane
/kind bug
/priority 3
/platform azure

What happened:

Deleting the last loadbalancer service will fail with error:

  Warning  SyncLoadBalancerFailed   3m27s (x11 over 6m35s)  service-controller               Error syncing load balancer: failed to delete load balancer: not a vmss instance

What you expected to happen:

For the service to be deleted

How to reproduce it (as minimally and precisely as possible):

  1. Create a VMO cluster
  2. Create a new service of type loadbalancer
  3. Try to delete the service.

Be mindful, that if the shoot is not using the reverse VPN tunneling, then the "last" service will be the vpn-shoot service. In that case the skip step 2 and the_vpn-shoot_ service should be deleted

Anything else we need to know?:

The error seems to not be reproducible with the latest cloud-provider-azure version (v1.1.1). Solving #373 is a potential mitigation.

Environment:

  • Gardener version (if relevant):
  • Extension version: v1.21.x
  • Kubernetes version (use kubectl version): 1.21.x
  • Cloud provider or hardware configuration:
  • Others:
@kon-angelo kon-angelo added the kind/bug Bug label Sep 21, 2021
@gardener-robot gardener-robot added area/control-plane Control plane related platform/azure Microsoft Azure platform/infrastructure priority/3 Priority (lower number equals higher priority) labels Sep 21, 2021
@ialidzhikov
Copy link
Member

ialidzhikov commented Sep 21, 2021

I can confirm that this issue occurs. I checked that LoadBalancer creation and deletion works as expected with CCM v1.21.1. It seems that something changed in CCM v1.21.4 and it does no longer work for VMO clusters.

@ialidzhikov
Copy link
Member

Ref kubernetes/kubernetes#105185 (credits to @kon-angelo)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/control-plane Control plane related kind/bug Bug platform/azure Microsoft Azure platform/infrastructure priority/3 Priority (lower number equals higher priority)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants