Nick Fox

> Yes, one things that we have started to brainstorm is that we need a more clean section about "control planes" entities, as they can be many per cluster (isolated,...

> @nrfox Perhaps this deserves separate issues for the config views and the graph. With respect to the graph, is there an easy way to identify a workload node as...

Based on the conversation above I'm going to split this issue into separate issues as was suggested to better divide the work that needs to be done. 1. WorkloadEntry workload...

Does this epic cover scalability improvements or is it only for testing? If it includes improvements then there's basically two parts to this epic: 1. Measuring performance and getting some...

> The only possible blocker: Is there anything coming upstream that would make us again want to query the Istio API? We still scrape the istiod debug endpoints to get...

It's not urgent... until keycloak 21+ stops working for some reason. 22 was released relatively recently so I'd still call this "not urgent".

Tracing is still a work in progress for ambient so putting "waiting external" on until there's more clarity there.

cc @yohanb if you want to take a look. Basically this change does 2 things: 1. Removes the use of `external_services.istio.config_map_name` altogether when trying to guess the configmap name. 2....

Closing this since there are many conflicts and changes since this was opened.

This is still relevant but yes it should reference the main epic. I'll update it. It's more of a perf / quality of life improvement.