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

Federate my service mesh with a separate mesh in a different OpenShift cluster

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • OSSM 2.1.0
    • None
    • None
    • None
    • Sprint 1, Sprint 2, Sprint 3, Sprint 4

      While this is very similar to OSSM-393, the other mesh to be federated with resides in a separate OpenShift Cluster. This story covers everything that may be different around this story if the mesh is in a separate cluster.

      As an administrator of a single Service Mesh (I may or may not have cluster admin access), I would like to federate my service mesh with a different mesh in a separate OpenShift cluster.

       

      The acceptance criteria for this story will be similar to OSSM-393, with the following exceptions (and possibly more):

      • Provide documentation on options to connect OpenShift Clusters, and how to validate this interconnectivity prior to federating service meshes. This may vary depending on the type of OpenShift cluster, but we should provide guidance, even if that involves referring to other OpenShift docs. Users should validate connectivity prior to federating meshes.
      • Kiali should indicate that the other mesh(s) resides in a separate cluster, with some reference to the identity of that cluster.

              jlongmui@redhat.com Jamie Longmuir
              jlongmui@redhat.com Jamie Longmuir
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: