Describe your problem. Include specific actions and error messages.

We’re trying to install and use the Kubernetes Gateway API in our Openshift clusters with a different controller than the ingress operator.
Gateway API is designed to be multi-controller capable so that you can install separate controllers to manage different gateways.
However, the Openshift Ingress Operator has this (https://github.com/openshift/cluster-ingress-operator/blob/b62dd27c901d495e6e78b11968872c002cc2416f/manifests/01-validating-admission-policy.yaml) policy bundled in its manifest which prevents other controllers from installing Gateway API CRDs.
The Ingress Operator installs some of the gateway api crds, but not all of them. Notably, UDPRoute, TLSRoute, and TCPRoute (from v1alpha2 https://gateway-api.sigs.k8s.io/reference/1.4/spec/#gatewaynetworkingk8siov1alpha2) are missing, and due to the policy cannot be installed by the new controller.

This is blocking us from adopting the gateway api via a separate controller in our clusters. We would propose that the VAP is restricted to only preventing modifications to the specific Gateway API version (v1) that it is installing resources in. Alternatively, installing the remaining CRDs in ingress operator would be acceptable.

Describe the impact to you or the business
This prevents us from standardizing offerings to the customer and will directly prevent customer from using openshift clusters starting in the next year