Open slonka opened 5 months ago
For now a user can click on the outbound:
click on clusters and associate pod ip with cluster ip:
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
Description
The below explanation assumes the following MeshHTTPRoute:
After merging https://github.com/kumahq/kuma/pull/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: