Gateway API compliance path

[mlavacca]

Problem statement

KIC has been updated and now all the upstream core conformance tests are passing (https://github.com/kubernetes-sigs/gateway-api/tree/main/conformance/tests). Nonetheless, compliance with the Gateway API conformance tests does not automatically imply full compliance with the Gateway API itself. This happens because the Gateway API conformance test suite is not complete yet, and some tests may have flaws or the suite may not test some core functionalities.

This issue's goal is to keep track of our Gateway API compliance debt discovered so far.

Acceptance Criteria

• gateway tests expecting the wrong ListenerConditionReason: conformance: gateway tests expecting wrong ListenerConditionReason kubernetes-sigs/gateway-api#1297. Fixed by Gateway API updated to 0.5.1 #3024.
• set the listener ResolvedRefs status condition as failed with reason InvalidCertificateRef when a nonexistent TLS secret is referenced: conformance: test gateway referencing an unexisting tls secret kubernetes-sigs/gateway-api#1318. Fixed by Gateway API updated to 0.5.1 #3024.
• set the listener ResolvedRefs status condition as failed with reason ListenerReasonInvalidRouteKinds when a listener supports a Route type incompatible with the ProtocolType: conformance: test gateway when an unsupported Route kind is specified by the Listener. kubernetes-sigs/gateway-api#1320. Fixed by Gateway API updated to 0.5.1 #3024.
• Always enforce ResolvedRefs condition in HTTPRoute and Gateway, not only when they are failing
• Convert the core filter RequestRedirect to the proper Kong plugin: Gateway API Integration Kubernetes Cluster Version Support #2848. Fixed by feat: Gateway API RequestRedirect filter translated to combination of kong plugins #3702

[mflendrich]

@mlavacca could you please update the scope & AC to match what is left to be done? Looks like much of this is already completed.

[mlavacca]

closing as completed