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

Federation: ServiceMeshPeers's status.discoveryStatus.active.remotes list missing after some time

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Undefined
    • None
    • OSSM 2.3.0, OSSM 2.4.0, OSSM 2.5.0
    • Customer Impact, Maistra
    • None
    • False
    • None
    • False
    • Hide

      Tested on two ARO clusters:

      1. Create federated meshes similar to those described in the federation docs
      2. After creating serviceMeshPeers on each cluster, watch the status block of each
      3. After some time (~10m), the status.discoveryStatus.active.remotes block is missing
      Show
      Tested on two ARO clusters: Create federated meshes similar to those described in the federation docs After creating serviceMeshPeers on each cluster, watch the status block of each After some time (~10m), the status.discoveryStatus.active.remotes block is missing

    Description

      From the federation docs:

      The status.discoveryStatus.active.remotes field shows that istiod in the peer mesh (in this example, the green mesh) is connected to istiod in the current mesh (in this example, the red mesh).

      This field appears when connection between serviceMeshPeers is first established, but disappears after some time (~10m).

      Expected Behaviour

      This field should remain present to allow users to verify that istiod in the remote mesh is connected to istiod in the local mesh. Alternatively, the docs should state that this field is short-lived.

      Attachments

        Activity

          People

            Unassigned Unassigned
            rh-ee-efenness Eoin Fennessy
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: