kcp
kcp copied to clipboard
kcp-dev
README still starts out weak
Describe the bug I do not yet have a good understanding of what kcp is, or perhaps more importantly, what is the vision of what it is becoming. But it clearly is more than the stripped-down apiserver & controller-set that is described in the introductory paragraphs of the README. Clearly kcp includes the transparent multi-cluster functionality too. I suspect the people on this project consider the title "kcp provides a true multi-tenant Kubernetes control plane for workloads on many clusters" to say less than the repo is about too. I myself tend to interpret the term "control plane" more broadly, to include interface type definitions and controllers as well as the API service. But this community seems to use the term "control plane" to mean just the API service; with that understanding, the existing title falls well short of describing everything this repo is about.
Perhaps something like "kcp provides massively multi-tenant kubernetes" is a good title, with the first paragraph mentioning the division between the api service layer and the physical clusters, as well as the factoring that reveals an api service that can be used for other purposes?
To Reproduce Read the README
Expected behavior I expected the title to be a good summary of the repo, and the introductory paragraphs to give the next level of detail about the whole thing.
Additional context
Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close
@kcp-ci-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopen. Mark the issue as fresh with/remove-lifecycle rotten./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.