I'm the core maintainer of Kamaji, an Open-Source project which runs Kubernetes Control Planes as Pods in a management cluster.<p>This approach brings several benefits I tried to emphasize in the README file: the core idea is to take full advantage of the Operator pattern and orchestrate, remediate, and save resources and operations in managing +1,000 Control Planes.<p>If you never heard the Hosted Control Plane term, my partner wrote this blog post (<a href="https://clastix.io/post/the-raise-of-hosted-control-plane-in-kubernetes/" rel="nofollow">https://clastix.io/post/the-raise-of-hosted-control-plane-in...</a>), or you can reference the Red Hat ones about Hypershift which is based on the same principle (pods instead of VMs), as well as with GDCH (Google Distributed Cloud Hosted).<p>Compared to other solutions, such as HyperShift by Red Hat, or k0smotron by Mirantis, Kamaji is offering vanilla clusters, with a strong focus on Day-2 automation: we've adopters using Kamaji offering a public service, as well as others for CI/CD/dev environments, or embedding it in their infrastructure product.<p>Happy to answer all your questions.