Blocker Issue for Tech Preview

GW API is evolving relatively rapidly, OSSM rebases to a new release some time after it is first released, and this is a time-costly activity. Because of this, we may lag upstream features for more than 4 months until we can align the releases, or shorten the rebase time.

OSSM and OpenShift Gateway API run different Istio images in dev preview release 4.12, but our goal is to use a Red Hat shipped image in tech preview.

Deliver a table that joins work in NE-1035 with the features parity table.

There is discussion on images in https://docs.google.com/document/d/1bRGPbJNAolU6f7pyFOleMD0XKtljj709lou3tJzPibg/edit#heading=h.222auagj42za

"Alignment of OSSM and OpenShift release schedules in order to claim Gateway feature support at a particular level:

• Dev Preview: No release alignment, can use any image, Cluster Ingress operator does nothing
• Tech Preview: No release alignment, must use a Red Hat shipped image, Cluster Ingress operator needs to understand how to configure it and expose it, Unified Control Plane
• GA: No release alignment, must use a Red Hat shipped image, Cluster Ingress operator needs to understand how to configure it and expose it
• GW API as installable component (as optional component): Must have release alignment, must use a Red Hat shipped image, Cluster Ingress operator needs to understand how to configure it and expose it
• GW API as default for Ingress: Must have release alignment, must use a Red Hat shipped image, Cluster Ingress operator needs to understand how to configure it and expose it"