Goals of the project?

[christopherhein]

This seems relatively similar to the virtualcluster project out of Kubernetes Multi-Tenancy working group as that we deploy control planes as tenants on a large cluster… where they differ it seems is the aspects of scheduling. I'd love to learn more about your goals of this project.

[hasheddan]

@christopherhein thanks for opening this issue! I am not familiar with that project but am checking it out now as it seems very relevant for my use case 🙂 My initial impetus for creating this was as a CI tool that we use in crossplane to test out our "tenant cluster" mode where we use the "parent" API server for running our provider controllers, but they actually watch "tenant" API servers that are running in the cluster. This works quite well for our scenario because our provider controllers don't actually ever run anything in the cluster, they just watch CRDs and take actions against external APIs (typically provisioning infrastructure on a cloud provider). I would be more than happy to chat with the virtualcluster and contribute anything upstream that would be useful. Please let me know if I can be of help!

[christopherhein]

Very cool, how are you handling etcd?

[hasheddan]

@christopherhein Here I take the very naive approach of just using a prefix:

kindred/pkg/tenant/tenant.go

Line 77 in db7e49d

fmt.Sprintf("%s-%s/", "--etcd-prefix=/tenant", identifier),

[christopherhein]

Ah perfect, thanks for showing me. That makes a lot of sense and make it pretty easy for test cases. 🙏