Closed arjunrn closed 8 years ago
Properties of the ELB have been split up in multiple components for the ALB, and some were added.
scheme
, securityGroup
, subnet
.port
, protocol
, certificates
The ALB is awesome° as we could do something like this(?):
/api/*
:scream:
° Somehow you can't route based on headers yet.
It might be easier to just have another component in the same stack. I don't think many microservices will have a requirement for path based routing since that would be handled in something like Skipper anyway. So just use a match all wildcard like /*
and use it exactly like the Classic LB. Maybe @hjacobs or @tuxlife could pitch in as well with their opinions.
I agree that it's better to have another component to avoid breaking things that are working now.
We should probably introduce a new component, but AWS guys advice us to switch to ALB for everything HTTP-based (some under-the-hood performance improvements etc).
So I would say:
senza init
templates to use the new componentWe also need to support the new ELBv2 in ZMON AWS agent!
Basic support for Application Load Balancers with HTTP/2 was released in https://github.com/zalando-stups/senza/releases/tag/2.0.121
Still TODO: support ELBv2 metrics in senza health
Still TODO:
senza status
senza health
ALB/ELBv2 support should be fine in https://github.com/zalando-stups/senza/releases/tag/2.0.124
AWS just released a new Load Balancer type with support for HTTP2. There is already support for it in Cloudformation. We could have a new component likewise called
Senza::WeightedDnsApplicationLoadBalancer
.