kcp
kcp copied to clipboard
Kubernetes-like control planes for form-factors and use-cases beyond Kubernetes and container workloads.
### Feature Description As a service provider, I want to scope down/minimize the permissions I am claiming in consumer workspaces. This should require no explicit action from the consumer. ###...
### Feature Description As a service provider, I determine that my monolithic service definition in an `APIExport` can be split into N independent exports, each to be consumed separately (or...
### Feature Description A company providing some service through some `APIExport` is acquired by another company. The acquiring company would like to continue providing the same service, but move the...
### Feature Description As a service provider, I would like to restructure the set of controllers I use to provide API functionality. To that end, I would like to move...
### Feature Description As a service provider owning an `APIExport`, I want to remove an `APIResourceSchema` from my exported set of resources, as I will no longer support the functionality...
Service providers (owners of `APIExports`) need to be able to mutate and evolve their offerings. Tasks for this epic are tracked in [this](https://github.com/orgs/kcp-dev/projects/1/views/45) project view.
### Feature Description A service provider / controller against `kcp` needs to see "all" objects of a certain GVR across "all" shards, or "all" shards in a region. We need...
### Feature Description We need to handle the creation of new shards, the removal of existing shards, etc. for their data in the caching server. ### Proposed Solution To be...
### Feature Description Reading directly from the caching server should be a highly privileged (`system:masters`) task. Writing to it should only be possible by a shard, and shards can only...
We now own `kcp.io`. This epic is concerned with the mechanical process(es) of getting a website published there and setting up the framework/workflow for adding user-facing documentation. Tasks for this...