GRPC header based consistent hashing

[mistborn17]

Is there support for gRPC header token based consistent hashing ?

[longwuyuan]

Not heard of it. Is the hashing used for sticky sessions or something else ?

[mistborn17]

If the gRPC server is stateful, then the given sequence of RPCs needs to land on the same kubernetes pod.

For ex, RPC1-upload document. RPC2 - index the document, RPC3 - track indexing status, should land on the same pod where the document is uploaded.

[longwuyuan]

This is available for HTTP because of Engine being NGINX but not seen a discussion for backend protocol GRPC. Please check annotations in docs. I don't think the hashing annotation will work for GRPC but I would test, as I don't have the knowledge.

…

On Fri, 7 Feb, 2025, 08:45 kishen suraj p, ***@***.***> wrote: If the gRPC server is stateful, then the given sequence of RPCs needs to land on the same kubernetes pod. For ex, RPC1-upload document. RPC2 - index the document, RPC3 - track indexing status, should land on the same pod where the document is uploaded. — Reply to this email directly, view it on GitHub <#12803 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABGZVWQ4AHDHNYLJ2ZOJV7L2OQQO5AVCNFSM6AAAAABWUZFKG6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBRHAZTKOJRGM> . You are receiving this because you commented.Message ID: ***@***.***>

[longwuyuan]

https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/#custom-nginx-upstream-hashing

[strongjz]

@mistborn17 Can you test if those upstream hashes will also work for your GRPC service? If not, I would say no, and we would potentially not support them as we are working towards getting Ingate up and running. PRs are always welcome, with appropriate e2e tests.

[strongjz]

/triage needs-information