Open miwithro opened 3 years ago
@Azure/aks-pm issue needs labels
@Azure/aks-pm issue needs labels
Action required from @Azure/aks-pm
Action required from @Azure/aks-pm
@palma21 @miwithro hey, is there any support for multiple load balancers in AKS?
There's currently a limitation of 300 Rules per NIC, so having multiple load balancers would be great.
Thanks, Guilherme
Hey @palma21 @miwithro any updates on this?
I'm struggling with the exact same scenario as @thperapp in #1754... meanwhile, does anyone have a workaround for having one egress public ip per pod?
Tks, Stefano
https://github.com/kubernetes-sigs/cloud-provider-azure/issues/908 What is your plan?
Similiar issue here: we seek to have more than 8 private link services available from an AKS. But with one private loadbalancer only this is limited to 8.
@palma21 @miwithro hey, is there any support for multiple load balancers in AKS?
There's currently a limitation of 300 Rules per NIC, so having multiple load balancers would be great.
Thanks, Guilherme
Hello Guilherme, By any chance, have you been able to find a workaround ?
thank you in advance.
regards, Nouha
@miwithro any timeline available for when this feature going to be delivered? I have a client who wants to use multiple load balancers in their AKS clsuter because of the 8 private link service per LB limit.
Similiar issue here: we seek to have more than 8 private link services available from an AKS. But with one private loadbalancer only this is limited to 8.
@hofmannma , I wrote a blog article to workaround a similar situation. Perhaps this will help: https://dev.to/lastcoolnameleft/azure-private-link-service-load-balancer-aks-limitation-44db
@Azure/aks-pm Do we have any update on when this feature will be implemented?
+1 Use case: gaming company deploying 500+ db services in a single cluster that is required to have routable IP (and this is a TCP binary connection not HTTP) with little flexibility to change port numbers.
Our other workloads running in the cluster are all HTTP/S and ingress via Traefik, though we may in the future introduce additional workloads that would also require TCP routing via a load balancer service.
I have another use case for this feature. We need to have a Public Load Balancer for public access and an Internal Load Balancer for loads that come from internal networks and VPNs. We run UDP/TCP services (Layer 4) in different ports, so Layer 7 load balancing services are not helpful.
Any plans to have this feature supported?
@aritraghosh - any ETA for this, ?
Would also like to see this feature. Thanks!
Public Preview ETA: Q4 2024*
*ETAs are estimations and subject to change
Status: delayed for security priority work.