Uploaded image for project: 'Network Observability'
  1. Network Observability
  2. NETOBSERV-165

Multicluster aware and support

    • Icon: Epic Epic
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • None
    • Loki
    • multicluster-aware
    • BU Product Work
    • False
    • False
    • To Do
    • OCPSTRAT-635 - Multi-cluster support for network observability
    • OCPSTRAT-635Multi-cluster support for network observability
    • 0% To Do, 0% In Progress, 100% Done
    • XL

      Network Observability supports a single cluster today. However even in a single cluster environment, there are certain things that only Network Observability can do to provide better integration between clusters. For example, traffic destined to one of your clusters will appear as intranet traffic. If it knew about the existence of other clusters, it can categorize it as internet traffic and display it correctly.

      Two high level areas need to be considered:

      1. Better integration with Advanced Cluster Management (ACM) for Kubernetes

      • Provide a way for ACM to be able to select a cluster and then display the same information as if you had logged into that cluster.
      • Provide an API or a way to access data so it can aggregate results across clusters. For example, it can provide a "Top service names" (NETOBSERV-141) of all clusters by collecting this data from each cluster.

      2. HyperShift environment
      Evaluate what additional work needs to be done to support a HyperShift environment.

              kalmanmeth Kalman Meth (Inactive)
              stlee@redhat.com Steven Lee
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: