feature: APIExports VirtualWorkspace without consumer enhancement

[mjudeikis]

Feature Description

Currently, if you create APIExport, until there is a first consumer (APIBinding), the endpoint is not usable. This means that there are no CRDs, informers can't start and the controllers will not work.

This leads to behaviour where platforms engineers are creating hacks around this by creating fake apibindings to enable controllers to start.
platform engineers create hacks around this by creating fake API bindings

This is not nice DevExerience and we should fix this.

Proposed Solution

We need to investigate:

fake an endpoint until there actually is a CRD. We can decide whether it is technically possible to adopt the existing watches from the real storage, or cut them off.

Alternative Solutions

No response

Want to contribute?

• I would like to work on this issue.

Additional Context

For more info see slack: https://kubernetes.slack.com/archives/C021U8WSAFK/p1734437782238829