Skip to content
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

Gateway API: handle Route conflicts with GRPCRoute.Matches #6267

Closed
lubronzhan opened this issue Mar 13, 2024 · 1 comment · Fixed by #6566
Closed

Gateway API: handle Route conflicts with GRPCRoute.Matches #6267

lubronzhan opened this issue Mar 13, 2024 · 1 comment · Fixed by #6566
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@lubronzhan
Copy link
Contributor

Please describe the problem you have
[A clear, concise, description of the problem you are facing. What is the problem that feature X would solve for you?]
Follow up on #3608
Now HTTPRoute has match conflict check but GRPCRoute is process later, so it could overwrites the route defined in HTTPRoute. But what we want is what is processed first should take precedance over other routes.

@lubronzhan lubronzhan added kind/feature Categorizes issue or PR as related to a new feature. lifecycle/needs-triage Indicates that an issue needs to be triaged by a project contributor. labels Mar 13, 2024
@lubronzhan lubronzhan self-assigned this Apr 24, 2024
Copy link

The Contour project currently lacks enough contributors to adequately respond to all Issues.

This bot triages Issues according to the following rules:

  • After 60d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, the Issue is closed

You can:

  • Mark this Issue as fresh by commenting
  • Close this Issue
  • Offer to help out with triage

Please send feedback to the #contour channel in the Kubernetes Slack

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 25, 2024
@lubronzhan lubronzhan removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. lifecycle/needs-triage Indicates that an issue needs to be triaged by a project contributor. labels Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant