Feature Request: Support for GRPCRoute

[darkn3rd]

Is your feature request related to a problem? Please describe.

Please support for GRPCRoute ASAP.

There are no workarounds, except to use an alternative solution that is non-Consul. I have been able to implement something similar with non-Consul solutions such as NGINX service mesh with NGINX Kubernetes ingress controller.

Feature Description

For ingress traffic into the service mesh, I would like to support gRPC traffic, as this protocol is highly performant, especially for solutions like Dgraph, a distributed graph database.

Use Case(s)

Dgraph, a distributed graph database, can communicate through a mixture of HTTP and gRPC using its own language, DQL, a superset of GraphQL. Through HTTP, it supports administrative operations (REST or GraphQL) or queries and mutations (GraphQL or DQL). The optimal method for queries and mutations is through gRPC. This is especially true for clients with large databases, especially in the billions of predicates. When offering a managed solution with Dgraph Cloud, both interfaces (gRPC and HTTP) need to be supported, so lack of gRPC is a show stopper or non-solution for us and our customers.

For an ingress/gateway solution to be considered, it would need to support both gRPC and HTTP, terminate public CA TLS at the edge, and encrypt/auth traffic between the ingress and service-mesh.

Contributions

I work in the role of platform engineer, so I can help with testing (QA) the solution, as well as any documentation and tutorials.

[nathancoleman]

Hi @darkn3rd, GRPCRoute hasn't been release upstream yet, but we're anticipating its inclusion in the v0.6.0 release of kubernetes-sigs/gateway-api some time in the near future. We're keeping an eye on the release milestone here.

[bfg111]

The upstream release is closed (Jan 31)? Any updates? https://github.com/kubernetes-sigs/gateway-api/milestone/6