5 ms·
Hi - I do a lot of work on Kubernetes on AWS. We definitely have room for improvement - and not just in the glib "there's always room for improvement" way. Bu
by justinsb 10y ago
Hi - I do a lot of work on Kubernetes on AWS. We definitely have room for improvement - and not just in the glib "there's always room for improvement" way.
But: We don't support ALB yet because we haven't actually found a compelling use-case for it. Ingress on Kubernetes seems to do everything ALB can, but without the limitations. At least that's what we've thought so far, so if you have a use case do open an issue explaining it, and we can look at adding it :-)
- buckhx 10y agoGRPC requires http2 which is only supported by ALB and not ELB. Our services are mostly GRPC so lack of ALB means we can't use k8s out of ths box on AWS if that adds any fuel to the fire.
- jhspaybar 10y agoAs a heavy grpc user, I don't think ALB supports it due to a lack of trailer support. You're probably going to just use a TCP load balancer if you want grpc services behind a load balancer.
- justinsb 10y agoI also want GRPC for my own stuff; ELB will work fine (in TCP mode), but I also want it to work through ingress. My understanding is HTTP2/GRPC support is coming to ingress - that aledbf has already implemented it, and it will be coming to the "official" repo soon; ingress is becoming a top-level project and there's some reshuffling that has to happen, but then aledbf has some great stuff in the pipeline.
- gtaylor 10y agoWhen you say "ingress", are you talking about the contrib nginx ingress controller?
- aledbf 10y agoYou can use ELB in TCP mode and use the nginx ingress controller (http2 works ootb) https://github.com/kubernetes/contrib/tree/master/ingress/controllers/nginx https://github.com/kubernetes/contrib/tree/master/ingress/co...
- Rapzid 10y agoI'm not sure the last time the issue was looked at, but I could consolidate some of the benefits that have brought up here: * Websockets support * Http/2 support * Layer 7 routing + Route to specific ports(stop sending all traffic to all nodes and preserve source ip) * Request tracing(recently added to ALB) I hope this doesn't sound too negative, and I KNOW you do a TON of work on this stuff, but there often seems a disconnect between the people working on the kubernetes integrations and the feedback coming through from people trying to run businesses on AWS. Which happens; it's tough to be in both roles if your business isn't infrastructure.
- aledbf 10y agoPlease check the nginx ingress controller (you can use https://github.com/kubernetes/kops/blob/master/addons/ingress-nginx/v1.4.0.yaml https://github.com/kubernetes/kops/blob/master/addons/ingres... in aws) The only missing piece is "Request tracing(recently added to ALB)"
- Rapzid 10y agoThese are advantages over ELBv1. We have no desire to move away from AWS's load balancing services at this time.
- alexnewman 10y agoI am not sure why we need anything but the last one. You should be able to do that with k8s
- meddlepal 10y agoIt seems like it would be possible to write a k8s ALB Ingress controller. Prolly a days worth of work for someone that wants it.
- smarterclayton 10y agoWe've discussed doing it for OpenShift - the best reason someone has articulated so far is the automatic SSL cert handling that ALB offers. It's definitely not complex to prototype, so I'm hoping someone does get to it.