Feature Description

kcp has multiple virtual workspaces. One of them is the ´APIExport` virtual workspace (for which we already have a provider in this repository), but there is also the virtual workspace for initializers (see kcp docs for more details).

The initializingworkspaces virtual workspace has slightly different semantics, most notably it allows full access to a workspace that is initializing. This means that each cluster has potentially a different set of resources (and thus, its own REST mapper, etc) as long as it's "in scope" for a certain initializer, and then goes away completely.

Proposed Solution

Build a new initializingworkspaces provider. Maybe that could share some code with the existing provider, to be determined.

Alternative Solutions

No response

Want to contribute?

• I would like to work on this issue.

Additional Context

No response