contour icon indicating copy to clipboard operation
contour copied to clipboard

Gateway API: conformance test for behavior of Contour on multiple Route with conflicts in Match

Open lubronzhan opened this issue 1 year ago • 4 comments
trafficstars

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?] Originate from discussion here

When multiple Route objects that have conflict on Match, instead of dropping the whole Route object, Contour should still consider the Route PartiallyInvalid: true, and still add remaining not conflicted sub route to the DAG. This is what upstream expects

lubronzhan avatar Feb 28 '24 22:02 lubronzhan

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[bot] avatar Apr 29 '24 00:04 github-actions[bot]

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[bot] avatar Jul 10 '24 00:07 github-actions[bot]

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[bot] avatar Aug 12 '24 00:08 github-actions[bot]