-
Notifications
You must be signed in to change notification settings - Fork 593
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resolve conflicts in GRPCRoute conformance testing. #6144
Comments
https://github.com/Kong/kubernetes-ingress-controller/actions/runs/9447263257/job/26018780527 |
After a series of attempts, I want to summarize the current situation. The This means routing different methods to different backend services.
According to the instructions in the document, when Kong Gateway is performing gRPC proxying, it needs to create a catch-all route to respond to gRPC Reflection Requests. When creating different catch-all routes for two services, in fact, since they are completely identical except for the service being different, Kong does not define their behavior unless priority is manually added for control. |
Considering these factors, and since it is a traditional mode, I think we can close this issue. For Kongers who want to see more information about this, you can check here: https://kongstrong.slack.com/archives/C03CTMSHP6C/p1718863712895609 |
Is there an existing issue for this?
Does this enhancement require public documentation?
Problem Statement
During the process of implementing the Gateway API GRPCRoute conformance test, I found that if both
tests.GRPCRouteHeaderMatching.ShortName
andtests.GRPCExactMethodMatching.ShortName
are running, there will be conflicts leading to a failure.So in the PR #5776
I temporarily disabled one of them. We need to delve into why they are conflicting and resolve it.
Proposed Solution
Additional information
No response
Acceptance Criteria
tests.GRPCRouteHeaderMatching.ShortName
andtests.GRPCExactMethodMatching.ShortName
to run simultaneously during the GRPCRoute conformance test.The text was updated successfully, but these errors were encountered: