Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-303

Control Openshift Route Creation for ingress Gateways

    XMLWordPrintable

Details

    • OSSM 2.2 - 2, OSSM 2.2 - 3

    Description

      We're currently creating static OpenShift Route resources for every ingress gateway configured in the SMCP. If customers do not want to use those Routes or need a different configuration, they currently have no option to disable their creation. We should add a field that allows this.

      Acceptance Criteria:

      • add a gateway.route boolean field (default: true) that configures static route creation

      Original description:

      With OSSM 2.0 an Openshift http route seems to be created for any Ingress Gateway specified in the SMCP without a way to disable route creation. In previous versions we could just disable the istio-ingressgateway and use our own custom gateway without the http route creation. The majority of the time these need to be secure routes - which can be deployed separately.

      Is there any way to disable route creation for ingress-gateway or additionalIngress?

      Example SMCP: https://github.com/trevorbox/service-mesh-patterns/blob/ossm-2.0-gateways/ossm-2.0/helm/control-plane/templates/servicemeshcontrolplane-basic-install.yaml

      Not sure if this is the chart code that creates the routes:
      https://github.com/maistra/istio-operator/blob/maistra-2.0/resources/helm/overlays/gateways/istio-ingress/templates/istio-ingressgateway-route.yaml

      Attachments

        Activity

          People

            jewertow@redhat.com Jacek Ewertowski
            rhn-gps-tbox Trevor Box
            Votes:
            1 Vote for this issue
            Watchers:
            14 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: