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

Support NLB type of load balancer (AWS) #820

Open
pbochynski opened this issue May 15, 2024 · 1 comment
Open

Support NLB type of load balancer (AWS) #820

pbochynski opened this issue May 15, 2024 · 1 comment
Assignees
Labels
area/service-mesh Issues or PRs related to service-mesh kind/feature Categorizes issue or PR as related to a new feature.

Comments

@pbochynski
Copy link
Contributor

pbochynski commented May 15, 2024

Description
Support NLB type of load balancer (AWS). At the beginning, it could be a configuration (or feature toggle). In the future maybe even a default option.

Reasons
The default LoadBalancer for the AWS cluster is ELB. There is a newer and more performant solution: NLB. The connectivity proxy team requested it as the latency for NLB is much lower than for the classic load balancer.

Ideas
I tried to change the LoadBalancer type, using the annotation in the ingress gateway service (https://cloud-provider-aws.sigs.k8s.io/service_controller/):

   service.beta.kubernetes.io/aws-load-balancer-type: nlb

The new LB was provisioned and used as external-ip in the ingress gateway service.
Of course it has to be added on the istio level:
https://istio.io/v1.14/blog/2018/aws-nlb/#generate-the-istio-manifest

@pbochynski pbochynski added the kind/feature Categorizes issue or PR as related to a new feature. label May 15, 2024
@strekm strekm added the area/service-mesh Issues or PRs related to service-mesh label Sep 5, 2024
@strekm
Copy link
Collaborator

strekm commented Sep 5, 2024

we might want to consider setting NLB type default. Before making decision we need to check how this change will take effect on existing installations. obviously downtime and IP change needs to be avoided

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/service-mesh Issues or PRs related to service-mesh kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

2 participants