-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
http2 option for http server #4630
Comments
@stamm there is no support for autodetection of http1.x and http2 in nginx itself. Please check With this change, we break http1 without tls. (I posted the same comment in the PR). |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
If the backend-protocol annotation specifies GRPC, would it make sense to force it to http2 in that case? |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
NGINX Ingress controller version: 0.26.1
I use ingress as balancer for grpc without tls, and before this version I was able to patch nginx.tmpl to add http2 flag to listen option
{{ if $all.Cfg.UseHTTP2 }} http2{{ end }}
But now this block is generated by go code.
The text was updated successfully, but these errors were encountered: