I'm working on improving the stability of rollouts when using Kubernetes as a control plane, specifically around the L3 agent, it seems that I have not found a clear way to detect in the code path where the L3 agent has finished it's initial sync..

Am I missing it somewhere or is the architecture built in a way that doesn't really answer that question?

Thanks

Mohammed
--