feature: implement PublishedResourcesEndpointSlices

[mjudeikis]

Feature Description

As per document https://docs.google.com/document/d/18Xh2-VFnH23bDiAHPP_JXm4qAG4QK6GjTKcpszPGApQ/edit?tab=t.0

Proposed Solution

We need to implement VirtualWorkspace & EndpointSlices object for PublishedResources (introduced in #3367 ) to serve published resources via shard aware URLs from cache server.

It should be something like /services/publishedresources/shards//clusters//publishedresource/ type of URL where we serve content based on PublishedResource identity.

Alternative Solutions

No response

Want to contribute?

• I would like to work on this issue.

Additional Context

No response

[gman0]

The GVR reference in CachedResource is a bit too loose. Where does the schema come from, and how can the replication VW ensure that whatever it reads from the CachedObject can be fitted onto the same schema that was used while creating that CachedObject?

A solution: when creating a CachedResource, we should ensure that the GVR reference points to something that can be resolved to APIResourceSchema or core k8s/kcp APIs. WDYT, @mjudeikis ?

[mjudeikis]

Maybe we need to change (I think maybe might be too weak of the statmenet) but CachedResources should be using APIResourceSchema. So the propagation pattern is the same as in normal API Export i using.