Properly support extended, experimental field Spec.CommonRouteSpec.ParentRefs[*].Port in TCPRoute & UDPRoute

[programmer04]

Is there an existing issue for this?

• I have searched the existing issues

Problem Statement

Currently only field Spec.CommonRouteSpec.ParentRefs[*].SectionName is properly supported, see

• fix: set proper destination port for TCPRoute and UDPRoute #4928

that fixes

• TCPRoute & UDPRoute: destination port taken from backendRef and not from listener config #4864

Setting Spec.CommonRouteSpec.ParentRefs[*].Port does not have any effect. It should work as described in the specification.

Proposed Solution

Implement support for Port field as described in the gateway-api spec.

Additional information

Conformance tests in gateway-api repo for checking this doesn't exist when it was been written. Ensure that is properly tested, consider adding such test to the upstream.

Acceptance Criteria

• field Spec.CommonRouteSpec.ParentRefs[*].Port works as described in spec for TCPRoute & UDPRoute
• it is properly tested

[pangruoran]

Could you please assign this to me? thanks!