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

Removal of ServiceMeshMemberRoll changes kiali CR which should NOT be managed by SMCP

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • OSSM 2.5.2
    • OSSM 2.5.1
    • Maistra
    • None
    • False
    • None
    • False
    • Hide
      1. Create new istio-system namespace
      2. Install basic default SMCP (addons enabled) using OCP console
      3. Wait for SMCP and Kiali to be ready
      4. Create ServiceMeshMemberRoll with one member 'default'
      5. Edit SMCP CR and change spec.addons.kiali.enabled=false and  spec.addons.kiali.name=kiali-old
      6. Wait for Kiali CR to disappear
      7. Create new default Kiali CR directly so it's not controlled by SMCP
      8. Wait for 'Ready'
      9. Remove ServiceMeshMemberRoll
      Show
      Create new istio-system namespace Install basic default SMCP (addons enabled) using OCP console Wait for SMCP and Kiali to be ready Create ServiceMeshMemberRoll with one member 'default' Edit SMCP CR and change spec.addons.kiali.enabled=false and  spec.addons.kiali.name=kiali-old Wait for Kiali CR to disappear Create new default Kiali CR directly so it's not controlled by SMCP Wait for 'Ready' Remove ServiceMeshMemberRoll

      A standalone (not controlled by SMCP) kiali CR is updated when you remove ServiceMeshMemberRoll. This is problematic for 2.x -> 3.0 upgrade scenario.

       

      See steps to reproduce, after removal of ServiceMeshMemberRoll the Kiali CR is updated but it should not be touched as it's not controlled by SMCP.

      Following fields are changed in Kiali CR:

      spec:
        api:
          namespaces:
            exclude: []
        deployment:
          accessible_namespaces: []

      Exclude and accessible_namespaces fields are changed to empty array.

              dgrimm@redhat.com Daniel Grimm
              fbrychta@redhat.com Filip Brychta
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: