Sidecar resources are key to scaling Istio in large clusters, but configuring Sidecars requires a detailed registry of every given workload’s peers. What do you do if your org maintains no such registry? What if service names are dynamic? This is the story of how we used NetworkPolicies to auto-generate Sidecars for hundreds of services, spanning many technical orgs and teams.