Feature Request: support gRPC over plaintext (non-TLS)

[dawnbreaks]

Since NGINX does support gRPC over plaintext (non-TLS), and why ingress-nginx does not support it? Ingress-nginx can listen on a new http2 port, and proxy grpc requests to grpc backend services.

[aledbf]

NGINX does not support HTTP/1.x and HTTP/2 at the same time on a cleartext (non-TLS) port.
Because of that we cannot support gRPC over port 80. Closing.

[aledbf]

That said, we could add a new annotation where we enable http2 in the listen section of port 80 but that means all the ingresses/paths for that server will not be available for HTTP/1.x clients

[dawnbreaks]

I know that NGINX does not support HTTP/1.x and HTTP/2 at the same time on a cleartext (non-TLS) port, and it would be great if we can listen on a new port (e.g. 8080).

[aledbf]

and it would be great if we can listen on a new port (e.g. 8080).

Sorry but no, Ingress is about port 80 and 443. If we add this feature it will be as described in the previous comment.

[parsnips]

@aledbf This would be a good compromise. We'd like to be able to use http2 non-tls ingress and have no need for 1.1.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[ThreeFx]

Has there been any development here? We would also like to support both GRPC (HTTP/2) and HTTP/1.1 plaintext on the same port.

[vainyksi]

Hi all, any news for this topic?