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

Do not require ingress and egress gateways when `spec.cluster.multiCluster` is enabled

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • OSSM 2.4.5
    • Maistra

      Currently, users cannot disable ingress and egress gateways when multi-cluster is enabled, because setting spec.gateways.enabled is ignored when spec.cluster.multiCluster is enabled. This is because istio-operator overwrites helm values.

      apiVersion: maistra.io/v2
kind: ServiceMeshControlPlane
metadata: 
  name: basic
spec: 
  addons: 
    grafana: 
      enabled: false
    kiali: 
      enabled: false
    prometheus: 
      enabled: false
  cluster: 
    name: east-cluster
    network: east-network
    multiCluster: 
      enabled: true
      meshNetworks: 
        remote-network: 
          endpoints: 
          - fromRegistry: remote-cluster
          gateways: 
          - address: remote-gateway
            port: 15443
  gateways: 
    enabled: false

      Acceptance criteria:
      When the SMCP above is applied, ingress and egress gateways are not deployed.

      This demo may be helpful: https://github.com/jewertow/istio-operator/blob/multi-cluster-research/deploy/examples/multi-cluster/README.md. Please remember that you don't need two clusters to apply this SMCP.

              rh-ee-mamyers Mayleigh Tjapkes
              jewertow@redhat.com Jacek Ewertowski
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: