extended conformance - HTTPRoutePortRedirect
#3681
Labels
area/gateway-api
Relating to upstream Kubernetes SIG Networking Gateway API
kind/conformance
Conformance to upstream Kubernetes SIG Networking Gateway API
nice-to-have
Is there an existing issue for this?
Problem Statement
Support the
HTTPRoutePortRedirect
feature in conformance tests (extended)Acceptance Criteria
HTTPRouteRedirectPort
is successfully ranThe text was updated successfully, but these errors were encountered: