The controller & webhook are currently both only capable to work for a single-shard kcp instance.
This vwURL := ess.Status.APIExportEndpoints[0].URL only picks up the virtual workspace from the first shard that registers there.
We could look at the implementation of the kcp api-syncagent to not reinvent the wheel. It would also be helpful to "wait" for the kcp envtest update to work with multi shards.
The controller & webhook are currently both only capable to work for a single-shard kcp instance.
This
vwURL := ess.Status.APIExportEndpoints[0].URLonly picks up the virtual workspace from the first shard that registers there.We could look at the implementation of the kcp api-syncagent to not reinvent the wheel. It would also be helpful to "wait" for the kcp envtest update to work with multi shards.