Uploaded image for project: 'Knative Serving'
  1. Knative Serving
  2. SRVKS-225

When running w/ Service Mesh, OpenShift Ingress needs different targetPort name for Routes

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Blocker Blocker
    • TP1
    • None
    • None
    • None
    • Serverless Sprint 171

      Service Mesh RC1 uses a targetPort name of "http2" for the istio ingressgateways. We use a hardcoded port name of "http" at https://github.com/openshift-knative/knative-openshift-ingress/blob/a1ba148e9b5c331e769fc06af8615cc6b5c881a0/pkg/controller/resources/route.go#L128

      I don't know if we can just switch that to always be "http2" or if we need smarter logic here to detect which to use.

      Our generated OpenShift Routes (and thus resolvable domains) will not work w/ Service Mesh RC1 until we update this, which is why I marked as a blocker.

              Unassigned Unassigned
              bbrownin@redhat.com Ben Browning
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: