grpc metadata based routing #3902
Unanswered
Syed-Shahidh-Ilhan
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm working on implementing a canary deployment strategy for a gRPC service using Argo Rollouts and Istio. My goal is to route specific gRPC requests to the canary subset based on gRPC metadata.
Specifically, I want to achieve the following:
Route gRPC requests with a specific metadata (e.g., 'x-canary: true') to the canary subset.
All other gRPC requests should go to the stable subset.
After the rollout is complete, all traffic should be directed to the new stable version, regardless of the metadata.
Can someone provide guidance on how to configure Argo Rollouts to achieve this gRPC metadata-based routing? Is this possible using the built-in features of Argo Rollouts, or would I need to implement any custom logic?
Beta Was this translation helpful? Give feedback.
All reactions