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

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.


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: