support protocol H1 and H2 about nghttpx-ingress-lb HOT 4 CLOSED

It is possible to covert h1 to h2, but converting from h1 to gGRPC is generally not possible with nghttpx.
gRPC might require its own header fields or semantics, and nghttpx does not know that.

from nghttpx-ingress-lb.

the convertion from h1 to grpc is done by my backing service. I don't expect it to be handled by nghttpx or ingress controller.

it's just that I want to merge these two different svc & port

ingress.zlab.co.jp/backend-config:  {"devg-ecdd1595-48ac-4449-bdc1-190d37f99fd4": {"8000": {"proto": "h2"}, "9000": {"proto": "http/1.1"}}}

into one

ingress.zlab.co.jp/backend-config:  {"devg-ecdd1595-48ac-4449-bdc1-190d37f99fd4": {"8000": {"proto": "h2-and-http/1.1"}}}

is it possible?

from nghttpx-ingress-lb.

Ah, sorry I misunderstood that.

So nghttpx should do on the same frontend port:

• if incoming request is h1, pass it to backend in h1.
• if incoming request is h2, pass it to backend in h2.

Choosing backend protocol depending on the frontend protocol is not possible at the moment.
You can mix multiple protocols in backend, but they are chosen in round robin manner.

I'm not sure how h1 request looks like, but if the backend can distinguish the normal HTTP request from gRPC request, then how about just sending all requests to backend in h2, and let backend decide whether the request is genuine gRPC or just h2 converted from h1.

from nghttpx-ingress-lb.

Hi,
I think I manage to work around this for my use case because I can differentiate the url path for grpc & http
Thanks. I'll close this

from nghttpx-ingress-lb.