Kcp: Kubernetes-Like Control Plane

cloudnativesimplified.substack.com

31 points·erkanerol··7 comments

I'm always curious of the use cases for something like this.

We manage multiple clusters but it's all done using pipelines so we don't traditionally have issues.

> For standard tenants who run standard workloads like Deployments, it is not easy but doable. You need to use RBAC objects, Namespaces, NetworkPolicies, ResourceQuotas, PodSecurityPolicies, etc to limit&isolate the tenants.

Shouldn't you generally use those resources even if you're not on a multi-tenant platform? At a minimum namespaces to segment workloads and other objects to control security.

> When it comes to advanced tenants who want to run their own operators with their own CRDs, it is huge pain. Kubernetes has no mechanism to isolate tenants for CRDs. Many people use a separate cluster per tenant in this case.

At this point aren't you just offering a kubernetes hosting solution?

Cool stuff, a little confused by this quote though:

"The ultimate goal is to be able to use multiple clusters as just compute resources like there is a single big cluster."

- isn't this the point of the underlying K8s nodes?

Layer. Never simplify. Barely abstract. Only layer.

Reminds me of vclusters

Vcluster runs k3s inside k8s to give access to the full API, but isolated from other virtual clusters.

Right, and that appears to solve about the same problem as "workspaces" in this.

Depends on your networking solution. If you’re using something like kilo, connecting the vclusters isn’t that complicated.

Reply on news.ycombinator.com