In Docker for AWS, docker4x/l4controller-aws provides integration between Docker Swarm and an Amazon Classic Load Balancer by syncing published service ports in the swarm with listeners on the load balancer.
Amazon introduced Network Load Balancer in September 2017.
Expected behavior
I would like to use a Network Load Balancer instead of a Classic Load Balancer with my Docker for AWS swarm.
Actual behavior
docker4x/l4controller-aws does not work with Network Load Balancers. Passing it the name of a NLB results in an API error because the elbv2 API is required to work with NLB and ALB load balancers.
In Docker for AWS, docker4x/l4controller-aws provides integration between Docker Swarm and an Amazon Classic Load Balancer by syncing published service ports in the swarm with listeners on the load balancer.
Amazon introduced Network Load Balancer in September 2017.
Expected behavior
I would like to use a Network Load Balancer instead of a Classic Load Balancer with my Docker for AWS swarm.
Actual behavior
docker4x/l4controller-aws does not work with Network Load Balancers. Passing it the name of a NLB results in an API error because the elbv2 API is required to work with NLB and ALB load balancers.
Information
Tested on Docker for AWS 18.06.1.
Steps to reproduce the behavior
N/A