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

Add support for new NLB #1639

Closed
AncientCulture opened this issue Sep 12, 2017 · 4 comments
Closed

Add support for new NLB #1639

AncientCulture opened this issue Sep 12, 2017 · 4 comments

Comments

@AncientCulture
Copy link

Hi,

AWS ec2 has a new LB, the network load balancer (NLB). It is a replacement for the previous ELB. AWS recommends using the old ELB primary for AWS ec2-classic envs.

As the NLB works similar as the ALB (listener, target groups) and shares API calls implementation might be quick feasible.

Here the block post:
https://aws.amazon.com/blogs/aws/new-network-load-balancer-effortless-scaling-to-millions-of-requests-per-second/

aws-go-sdk added support in version 1.10.40, which is alreadythe current version in vendor directory.

Cheers and thanks,
Nils

@AncientCulture
Copy link
Author

oh and to be consistent the "old" elb may need to be renamed to CLB (classic load balancer) as this is the new name in AWS

@stack72
Copy link
Contributor

stack72 commented Sep 12, 2017

@AncientCulture this is being taken care of in #1629

FWIW, classic load balancer is known as ELB in Terraform. Application load balancers were known as ALB but I have renamed those to load balancers as they can be either application or network

@Ninir
Copy link
Contributor

Ninir commented Sep 13, 2017

Hi @AncientCulture

@stack72 is right on that! :)
I would like to add that there is another thread keeping track of this issue here.

I am now going to close this one if you don't mind: if you want to comment & discuss, please do it on the thread! 👍

Thanks!

@Ninir Ninir closed this as completed Sep 13, 2017
@ghost
Copy link

ghost commented Apr 11, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked and limited conversation to collaborators Apr 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants