Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-960

Multi-protocol front end support for same route


    • Icon: Feature Feature
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • None
    • Networking
    • 67% To Do, 0% In Progress, 33% Done
    • 0

      1. Proposed title of this feature request

      Multi-protocol [HTTP and HTTPS] support for same 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 same route by specifying on a port by port basis what the expected protocol is.

      We would allow two routes with same hosts with different protocols to be supported while handling the conflict resolution in the backend. 

      Ideally we would like to keep one route object for one protocol for clean implementation.



      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

            mcurry@redhat.com Marc Curry
            ddharwar@redhat.com Deepthi Dharwar
            Miciah Masters Miciah Masters
            Ashley Hardin Ashley Hardin
            Deepthi Dharwar Deepthi Dharwar
            0 Vote for this issue
            4 Start watching this issue