Enabling Http2 on Kong 0.14.1 does not support services running 1.1 (any flag to support transation?)

Questions
1

Thanks for excellent support!

We are using Kong 0.14.1 and enabled and tried enabling the http2 by updating the yaml for kong to enable http2 on both admin and proxy ports. Now we see an issues that service that support http2 are able to talk to kong but not the apps that support http 1.1.

I was under the assumption that enabling http2 means that the proxy is backward compatible…Did I miss anything Or do we need to handle it with some configuration on admin or adding some config data in our yaml for kong?

Kong Configuration change:

Kong values.yaml modification via helm:
containerPort: “8443 http2”
admin:
type: ClusterIP
useTLS: false
@@ +29,36 @@
pullPolicy: IfNotPresent
env:
database: postgres
http2: “on”
admin_http2: “on”

Thanks

Chandra

2

I run Kong proxy port with http2 enabled but do not have any live active http2 traffic but have no issues. Does that impact behavior? If you were to restart your Kong application and not send http2 does the http 1.1 traffic work once again? Are you trying to have the same service+route serve http2 and http 1.1 traffic simultaneously or two separate proxies?

3

@jeremyjpj0916 : We are trying to use both on same port…

https://trac.nginx.org/nginx/ticket/816 says otherwise…

Thanks

Chandra