FYI to Networking: Adding Mesh UID for a Telemetry use case

[djazayeri]

FYI: we are going to add a Mesh UID for the limited use case of aggregating telemetry for multiple meshes, and then being able to query it.

The initial implementation is to have a simple, opaque UID value. Future plans to support cross-mesh networking policy, mesh federation, or to include mesh UID as a part of service/workload identity should be aware of this.

docs[dot]google[dot]com/document/d/1URXkFu2-cSg-g2fJin666M_QJvkumdn-C1NY9XkYgIM/edit

Sorry, my discuss account is too new and I can’t post a proper link. There’s a clickable link in the original proposal post:

Proposal: adding Mesh UID for telemetry

I propose that we add a Mesh UID to Istio. We need this to support the use case of aggregating telemetry from multiple Istio meshes in one place, and then being able to query it, distinguishing which mesh particular entries came from. I know that other approaches to mesh identification have been discussed that are more complex to cover use cases related to identity or admission to multicluster meshes. This proposal is intentionally very simple, hopefully avoids any controversial design choices,…