Clastix blog

News about Kubernetes, Cloud-Native and Multi-Tenancy.

With the accelerating adoption of Kubernetes the dilemma of multi-tenancy is gaining more traction and being more hot and relevant. Implementing a multi-tenancy architecture is proving to be one of the more strategic decisions that need to be considered when implementing Kubernetes-based infrastructure, as it has long term implications to operational efficiency, scale velocity and costs.

From experience with our customer base, adopting a multi-tenancy architecture results in deploying 70% fewer clusters, with greater operational agility and lower costs. And adding multi-tenancy to a kubernetes cluster can take less than 10 minutes!

The Cloud-Native methodology has been widely adopted, with Kubernetes, acting as the framework for achieving it. Start-ups and mid-size companies began using it mostly to achieve horizontal scaling to serve traffic spikes. Now, the enterprise world has crossed the adoption chasm, selecting Kubernetes as the de-facto standard for the Cloud. That is good news!

Unfortunately, the rapid and effortless adoption of Kubernetes, with its “one tenant one cluster” architecture, has resulted in many cases with cluster sprawl problems, where large amounts of clusters get deployed as each organization needs their own tenant. This sprawl then causes significant operational challenges as well as poor infrastructure utilization, driving up costs.