Support for Port ParentReference #2946
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
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.
The text was updated successfully, but these errors were encountered: