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

Federate my service mesh with a separate mesh in the same OpenShift cluster.

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • OSSM 2.1.0
    • None
    • None
    • None
    • Sprint 4

      As a mesh administrator (not necessarily a cluster admin - If cluster admin rights are required for any steps, that should be noted), I would like to federate my service mesh with one or more other service mesh(es) residing on the same OpenShift cluster. 

      For the purposes of this story, we can assume that I have full access to the service meshes (SMCP and other CRDs) that are to be federated (or am co-operating with another admin).

      Acceptance Criteria:

      This should apply to all service mesh control planes that are federated:

      • The ability to validate that the two or more meshes are federated through "oc" commands and kiali.
      • Kiali should represent that the two or more meshes are federated from both my mesh's view and the "other" federated mesh's view. As no services are federated at this point, this will likely not be part of the service graph, but should be something I can validate.
      • By default, there should be no visibility between service meshes. I should not be able to see any services in the "other" mesh, and they should not be able to see any services within my mesh. I should not be able to connect to any service in the "other" mesh.

      There are other aspects not dealt with, such as root certificates and identity - that may drive splitting this story out further.

              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: