Display MeshHTTPRoute (tcp route probably as well) tags in outbound view

[slonka]

Description

The below explanation assumes the following MeshHTTPRoute:

apiVersion: kuma.io/v1alpha1
kind: MeshHTTPRoute
metadata:
 name: http-route-1
 namespace: kuma-system
 labels:
   kuma.io/mesh: default
spec:
 targetRef:
   kind: MeshService
   name: frontend_kuma-demo_svc_8080
 to:
   - targetRef:
       kind: MeshService
       name: backend_kuma-demo_svc_3001
     rules:
       - matches:
           - path:
               type: Prefix
               value: /
         default:
           backendRefs:
             - kind: MeshServiceSubset
               name: backend_kuma-demo_svc_3001
               tags:
                 version: "v0"
               weight: 90
             - kind: MeshServiceSubset
               name: backend_kuma-demo_svc_3001
               tags:
                 version: "v1"
               weight: 10

After merging kumahq/kuma#9768 stats for different splits won't get merged so you can view them in Grafana.

The problem is that there is no easy way to figure out which "Destination service" maps to which split. The hash does not tell us much. If a person copies a hash they can see that it matches one of the outbounds.

But they still don't know what's the difference between them.

---

What I suggest is to add the tags used for the split (v0, v1 in this case) and put them next to the service tag:

[slonka]

For now a user can click on the outbound:

click on clusters and associate pod ip with cluster ip: