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

[KIALI][OSSM3] Kiali clusterting doesn't seem to be working as expected even though Istio multicluster is

XMLWordPrintable

    • Icon: Ticket Ticket
    • Resolution: Not a Bug
    • Icon: Normal Normal
    • None
    • OSSM 3.1.0
    • Kiali
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      Kiali multicluster configuration doesn't seem to be working as expected based on what I see here  [1][2] in the upstream documentation.

      The upstream documentation is also not very helpful since they use helm charts for deployment, but upon trying multiple options in Kiali CR the same output is still not visible, with traffic on the remote cluster not being visible in its complete form and both mesh appear but not as a multicluster Istio.

      Multicluster multi primary on different networks deployment is working as expected in istio and Services from both mesh and clusters are interconnected as expected.

      Even using the gateway to expose istiod still doesn't change anything in Kiali. 

      One thing that seems to be missing in our deployment is the clusterrole and clusterrolebinding in the remote cluster where kiali server is not deployed, since we set --process-remote-resources to false. But even creating this objects in that cluster, still  doesn't change anything. I can see basic data like envoy config, logs and kubernetes related objects.

      [1] https://kiali.io/docs/features/multi-cluster/#graph-view-cluster-and-namespace-boxing

      [2] https://kiali.io/docs/features/multi-cluster/#mesh-view-cluster-istio-and-data-plane-boxing

      Let me know what information from my cluster is useful to share

              rhn-support-pmarek Pavel Marek
              rhn-support-andcosta Andre Costa
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: