As we all know, Kubernetes cluster life cycle management is challenging. Imagine the herculean job of managing 1000s or more clusters on your clouds. Adopting Cluster API solves this problem to an extent by out-sourcing the burden to "management cluster(s)", which are expected to manage their children-workload clusters. However, it raises many new questions, like a) who manages these 100s of "management clusters" on gigantic clouds? b) scale issues on the management clusters c) how to enable multitenancy on the management clusters d) how to prevent management cluster admin from seeing workload cluster secrets e) HA, RBAC, Backup of the management clusters f) K8s version skew between management and workload clusters and so on. Can we get away with this overhead of "Management clusters" but still leverage all the richness of Cluster API? Yes, that is possible by transforming workload clusters into "Self Managing" clusters. Come to our talk and learn more about our journey on how we have productized the concept of "Self-Managing" clusters in our Multi-tenant cloud platform and our success story.