feature: Virtual Resources: fallback to VW discovery in AggregatingVersionDiscoveryAPIServer

[gman0]

Feature Description

AggregatingVersionDiscoveryAPIServer resolves version discovery in /apis/<Group>/<Version>. If a resource in its APIResourceList response happens to be a VR, the server looks into a lookup table for types it knows about and serves discovery info from that. If the type is not in the table, an error is returned. Currently, this table has only a single entry (one that is defined for CachedResources).

We should support discovery for dynamically added VRs.

Proposed Solution

Add a fallback option for types that are not in the lookup table and do proper discovery against the VW of the virtual resource.

Consider getting rid of the lookup table to have only a single code path to do the discovery.

Alternative Solutions

No response

Want to contribute?

• [ ] I would like to work on this issue.

Additional Context

No response