kube-ingress-aws-controller icon indicating copy to clipboard operation
kube-ingress-aws-controller copied to clipboard

Published 20 hours ago • verified publisher icon zalando-incubator

HTTP/2 not enabled for target groups

Open universam1 opened this issue 4 years ago • 4 comments

HTTP/2 is enabled per default for the load balancer, but for the target group!

According to this announcement and the AWS console the target groups do support HTTP/2 as well.

https://aws.amazon.com/blogs/aws/new-application-load-balancer-support-for-end-to-end-http-2-and-grpc/

However, the target groups are always configured to forward to connect via HTTP/1.1

This might have a performance impact

universam1 avatar Jan 14 '21 14:01 universam1

@universam1 normally it should not have an impact because of connection pools. Maybe for frontends it would benefit to do full H2 support. Do you want to work on an option to enable H2 backend? I don't want to have this as default set, but the feature would be great to have!

szuecs avatar Jan 15 '21 19:01 szuecs

pending on Cloudformation support: https://github.com/aws-cloudformation/aws-cloudformation-coverage-roadmap/issues/713

universam1 avatar Jan 18 '21 10:01 universam1

@szuecs Cloudformation support is present in meantime, but the underlying CFN lib fork seems to be unmaintained.

Any idea @mikkeloscar how to continue here, guess that's a project relevant question?

universam1 avatar Jul 05 '21 10:07 universam1

I see. I think we have 2 possible ways:

  • fork the dependency project
  • internal it

szuecs avatar Jul 05 '21 16:07 szuecs