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

Should we switch to standard SKU load balancers in Azure? #15

Closed
rfranzke opened this issue Jun 26, 2018 · 9 comments
Closed

Should we switch to standard SKU load balancers in Azure? #15

rfranzke opened this issue Jun 26, 2018 · 9 comments

Comments

@rfranzke
Copy link
Member

We are using basic SKU load balancers for our Shoots in Azure, however, Azure supports also standard SKU load balancers which provide more features: https://docs.microsoft.com/en-us/azure/load-balancer/load-balancer-standard-overview

Should we switch to them?

Hint: To use this feature in Kubernetes we require version 1.11 for the Seed clusters, and must set {"loadBalancerSku": "standard"} in the Azure cloud provider config. See kubernetes/kubernetes#61884 and kubernetes/kubernetes#62707.

@rfranzke
Copy link
Member Author

rfranzke commented Oct 5, 2018

@dkistner any recommendation?

@rfranzke
Copy link
Member Author

rfranzke commented Oct 5, 2018

@bergerx @luisdavim do you have some experience with standard SKU LBs in Azure?

@rfranzke
Copy link
Member Author

rfranzke commented Jan 8, 2019

any advice here?

@marwinski
Copy link

Just one note: Azure support suggested to use standard SKU load balancers. Not sure whether there will be a real benefit.

@vlerenc
Copy link
Member

vlerenc commented Apr 10, 2019

@dkistner WDYT?

@dkistner
Copy link
Member

dkistner commented Apr 15, 2019

Hard to say. The good thing with the basic sku lbs is that they are free of charge.

On the hand side the basic sku lbs allow only 100 machines in their backend pools (standard 1000 machines). The basics do also not support Azure AZs. Update operations (e.g. add a lb rule or attach an ip) should faster then < 30 sec (basics 60-90sec). This could speed up loadbalancer service provisining times.

The SLA is also interesting. The basics have no dedicated SLA and rely completely on the machine SLAs. The standard ones have an SLA: https://azure.microsoft.com/en-us/support/legal/sla/load-balancer/v1_0/

So long term I see a need for standard sku lbs, because otherwise we can't support clusters with more 100 nodes on Azure.

@vlerenc
Copy link
Member

vlerenc commented Apr 16, 2019

Then it looks as if we should do that. At least, you only list advantages (modulo the price of course). Since the goal of the people are mature clusters, it seems reasonable to integrate them.

@vlerenc
Copy link
Member

vlerenc commented Apr 18, 2019

@zanetworker proposed to do that also because of the current and ongoing Azure connectivity issues. He also offered to do that soon.

@dkistner
Copy link
Member

Ok thanks @zanetworker for taking over :)

@rfranzke rfranzke transferred this issue from gardener/gardener Jul 23, 2019
@rfranzke rfranzke transferred this issue from gardener-attic/gardener-extensions Jan 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants