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 for Port ParentReference #2946

Open
mpstefan opened this issue Dec 23, 2024 · 0 comments
Open

Support for Port ParentReference #2946

mpstefan opened this issue Dec 23, 2024 · 0 comments
Labels
area/httproute/extended Relates to all extended features of HTTPRoute enhancement New feature or request highlight Relates to features that should be promoted despite not being an epic
Milestone

Comments

@mpstefan
Copy link
Collaborator

mpstefan commented Dec 23, 2024

As a user of NGF
I want to reference a port as my parent reference on my route
So that I have a simple way to direct all traffic for a particular port to my application.

Acceptance

  • The Port parentRef functionality is implemented as specified in the Gateway API spec:

    Port is the network port this Route targets. It can be interpreted differently based on the type of parent resource.

    When the parent resource is a Gateway, this targets all listeners listening on the specified port that also support this kind of Route(and select this Route). It’s not recommended to set Port unless the networking behaviors specified in a Route must apply to a specific port as opposed to a listener(s) whose port(s) may be changed. When both Port and SectionName are specified, the name and port of the selected listener must match both specified values.

    Implementations MAY choose to support other parent resources. Implementations supporting other types of parent resources MUST clearly document how/if Port is interpreted.

    For the purpose of status, an attachment is considered successful as long as the parent resource accepts it partially. For example, Gateway listeners can restrict which Routes can attach to them by Route kind, namespace, or hostname. If 1 of 2 Gateway listeners accept attachment from the referencing Route, the Route MUST be considered successfully attached. If no Gateway listeners accept attachment from this Route, the Route MUST be considered detached from the Gateway.

  • The HTTPRouteDesinationPortMatching and HTTPRouteParentRefPort conformance tests are enabled and pass.

@mpstefan mpstefan added highlight Relates to features that should be promoted despite not being an epic enhancement New feature or request area/httproute/extended Relates to all extended features of HTTPRoute labels Dec 23, 2024
@mpstefan mpstefan added this to the v2.2.0 milestone Dec 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/httproute/extended Relates to all extended features of HTTPRoute enhancement New feature or request highlight Relates to features that should be promoted despite not being an epic
Projects
Status: 🆕 New
Development

No branches or pull requests

1 participant