Dynamic Routing of gRPC using Linkerd

[hiteshwani29]

We have a requirement to configure dynamic routing for grpc using linked. But I could not find any reference in the documentation to implement this using Linkerd.

We want to achieve this in a similar way as linked supports the HTTP dynamic routing based on the headers using HttpRoute(https://linkerd.io/2.13/tasks/configuring-dynamic-request-routing/)

I tried to achieve dynamic routing using Gateway and Route as well but currently, it seems that Linked doesn't support these CRDs

Route

Gateway

apiVersion: linkerd.io/v1alpha2 kind: Route metadata: name: grpc-route spec: protocol: grpc routes: - name: backend-a condition: pathRegex: "/backend.BackendService/MethodFromBackend" headers: x-header-key: backend-a client: name: backend-a kind: service - name: backend-b condition: pathRegex: "/backend.BackendService/MethodFromBackend" headers: x-header-key: backend-b client: name: backend-b kind: service

apiVersion: gateway.linkerd.io/v1alpha2 kind: Gateway metadata: name: grpc-gateway spec: http: routes: - name: backend-a condition: pathRegex: "/backend.BackendService/MethodFromBackend" headers: x-header-key: backend-a servers: - name: backend-a port: 50051 - name: backend-b condition: pathRegex: "/backend.BackendService/MethodFromBackend" headers: x-header-key: backend-b servers: - name: backend-b port: 50051 servers: - name: backend-a port: name: grpc number: 50051 - name: backend-b port: name: grpc number: 50051

Would someone from the community be able to help me to achieve this?

[alpeb]

Hi @hiteshwani29 , we still don't support dynamic routing for gRPC, but it's planned. Stay tuned!