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

Kiali operator version 2.17.x does not create kiali-viewer Role and RoleBinding

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • OSSM 2.6.12
    • None
    • Kiali, Maistra
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Release Notes
    • Release Notes
    • Hide
      Previously, when the latest Kiali operator 2.17+ was used with OSSM2.6 and Kiali addon was enabled in SMCP, the Kiali config map contained `cluster_wide_access=true` no matter what mode was selected in SMCP. Now, the `cluster_wide_access` value for Kiali is set according to SMCP mode.
      Show
      Previously, when the latest Kiali operator 2.17+ was used with OSSM2.6 and Kiali addon was enabled in SMCP, the Kiali config map contained `cluster_wide_access=true` no matter what mode was selected in SMCP. Now, the `cluster_wide_access` value for Kiali is set according to SMCP mode.

      From Kiali operator version 2.17.x, it does not create a kiali-veiwer Role and RoleBinding per namespace. Instead, it create a single ClusterRoleBinding for kiali-viewer ClusterRole.

      The earlier version of Kiali Operator, 2.11.x used to create the kiali-viewer Role and RoleBinding per namespace where the Kiali instance is running.

      I'll share the details in the comments.

        1. kiali-resource-2.17.2.yaml
          8 kB
          Akshit Kumawat
        2. kiali-configMap-2.17.2.yaml
          11 kB
          Akshit Kumawat
        3. kiali-configMap-2.11.4.yaml
          11 kB
          Akshit Kumawat
        4. kiali-resource-2.11.4.yaml
          7 kB
          Akshit Kumawat

              jmazzitelli John Mazzitelli
              rhn-support-akumawat Akshit Kumawat
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: