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

Support named routes and propagate the route name to the Gateway #6582

Open
2 of 3 tasks
mlavacca opened this issue Oct 30, 2024 · 0 comments
Open
2 of 3 tasks

Support named routes and propagate the route name to the Gateway #6582

mlavacca opened this issue Oct 30, 2024 · 0 comments
Labels
area/gateway-api Relating to upstream Kubernetes SIG Networking Gateway API release/required it is required that this be resolved before releasing
Milestone

Comments

@mlavacca
Copy link
Member

Is there an existing issue for this?

  • I have searched the existing issues

Does this enhancement require public documentation?

  • I have added an Acceptance Criteria item for adding and/or adjusting public documentation (if applicable)

Problem Statement

Gateway API 1.2 released named route rules as a GA feature. this means that now route rules can have their name, to be properly referenced inside a broader route. We can leverage this feature to propagate the rule name to the DataPlane, with the goal of improving observability.

Proposed Solution

No response

Additional information

No response

Acceptance Criteria

  • The route rule name is propagated to the DataPlane.
@mlavacca mlavacca added the area/gateway-api Relating to upstream Kubernetes SIG Networking Gateway API label Oct 30, 2024
@randmonkey randmonkey added this to the KIC v3.4.x milestone Oct 30, 2024
@lahabana lahabana added the release/required it is required that this be resolved before releasing label Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/gateway-api Relating to upstream Kubernetes SIG Networking Gateway API release/required it is required that this be resolved before releasing
Projects
None yet
Development

No branches or pull requests

3 participants