Skip to content

feature: Extend kcp's cache-server to allow caching arbitratry resources #3

@xmudrii

Description

@xmudrii

Feature Description

As explained in #2, we need a way to cache FilteredAPIExportEndpointSlices so we can watch them across shards. At the moment, kcp's cache-server doesn't support this and it should be extended to allow such use case.

Proposed Solution

Extend the kcp's cache-server to allow caching FilteredAPIExportEndpointSlices.

Alternative Solutions

We considered writing a controller to do this, but it's not a trivial because cache-server is an aggregated API server that have a different API structure. We also considered CachedResources, but those are not a good fit for this use case because you have to use the Replication VW, and can't read from the cache-server directly.

Want to contribute?

  • I would like to work on this issue.

Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions