1. Proposed title of this feature request

Multi-protocol [HTTP and HTTPS] support for single route

2. What is the nature and description of the request?

We'd like to be able to support both HTTPS and HTTP using a single route by specifying on a port by port basis what the expected protocol is.

For example, if the Route API was expanded to allow us to express expectations around front end ports, then it should be technically possible for us to achieve the desired behavior. This could be achieved with something like a TargetPorts list

apiVersion: route.openshift.io/v1
kind: Route
metadata:   name: default-ingress-passthrough-route-gwhpvl898k
spec:   host: data.apps.vossel1.apps.dvossel-test80.devcluster.openshift.com
  targetPorts: 
    - port: 80
      protocol: HTTP
    - port: 443
      protocol: HTTPS
  tls:     termination: passthrough
  to:     kind: Service
    name: default-ingress-passthrough-service-gwhpvl898k
    weight: 100
  wildcardPolicy: Subdomain

That resulting API could then result in a port 80 entry in the HAPRoxy `frontend public` config and an entry for port 443 in the `frountend public_ssl` config.

3. Why does the customer need this? (List the business requirements here)

The HyperShift KubeVirt platform is using a wildcard route to direct the default ingress [*apps] traffic to OCP nodes hosted in KubeVirt VMs. Since a route is currently only capable of routing either HTTP or HTTPS but not both, the KubeVirt platform is unable to provide HTTP [*apps] ingress for the default ingress controller.

More information about this use case can be found here, https://hypershift-docs.netlify.app/how-to/kubevirt/ingress-and-dns/

The inability to route HTTP and HTTPS using a single route was originally thought to be a bug. The bug report that resulted in this feature request can be found here, https://issues.redhat.com/browse/OCPBUGS-13966

4. List any affected packages or components.

OCP Router