3 ms·
I'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 supp
by Rapzid 10y ago
I'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.