LOGO-KubernetesSee how easy it is for developers to enable and share a Kubernetes multi-tenant cluster and share it with others outside the organization (e.g. customers, produce demo users).

Kubernetes provides several features to manage multi-tenant clusters, such as Access Control, network policies, resource quota, etc. Roost not only provides these features but provides you the control and ease-of-use with a simple one single-click method to enable multi-tenancy as per your use case.

With Roost SaaS Control Plane, you can create a multi-node Kubernetes cluster on GCP, AWS, Azure, or on-prem. Furthermore, you can inject your scripts at various launch stages to prepare your multi-tenant environments. One such way is to create a namespace-based multi-tenant environment, where isolation is provided based on the namespaces. Users/demo customers can connect to their respective namespaces using the Roost Desktop app, which provides a unified Kubernetes cluster analytics view. In addition, an admin role can compare various Namespaces on Roost Desktop’s Dashboard.

 
blog-kubernetes-multi-tenancy1

Figure 1. With Roost SaaS Control Plane, you can create a
multi-node Kubernetes cluster on GCP, AWS, Azure, or on-prem.

 

The other such user could be around creating repeatable demo clusters. Demo users can work on these Kubernetes clusters with your custom installs to demo your product features.

As a development lead, you can create a team k8s cluster. Then, your team members can share the cluster. Suppose a specific user wants to test services on the cluster without worrying about other dependent services/app being changed by someone else; the user can acquire an exclusive lock to ensure that.

With multi-tenancy Kubernetes cluster, sharing a cluster means less overhead. Still, at the same time, it increases security risks as RBAC features are still evolving. With Roost, you have the flexibility to enable it in a way you want it, as you have an option to create and destroy repeatable k8s clusters on-demand while having complete control on the cluster through Roost API or hooks.

 

Other ways to use Kubernetes multi-tenant cluster

  1. Share a policy-based team cluster within a team with an added exclusive lock feature.

  2. Create repeatable demo environments for your product demos on top of Roost K8s clusters. You can access demo environments from the Roost EaaS Control Plane.

  3. Build a namespace-based multi-tenancy as per your need and access details from the Roost EaaS Control Plane or Roost Desktop.

 

GoogleAd-728x90 Build Faster

 

 


WATCH VIDEO DEMO >>Laptop-DemoVideo 500

Roost provides a production-like environment to developers to ensure services are interoperable between environments. Developers can certify that services are working together prior to release ensuring absolute consistency between environments.
See how Roost helps developers validate the interoperability of microservices avoiding service integration issues discovered prior to release.

 

Sudhir Jangir

About Sudhir Jangir

Sudhir is the CTO and Co-Founder of Roost. He has 20 years of experience developing enterprise applications and leading technology teams.

Please Share this Blog

You may find these blog posts of interest too.

Ephemeral Test Environment Improve the Functionality of a Pull Request
Ephemeral Test Environment Improve the Functionality of a Pull Request
November 1, 2021

What is a Pull Request? In its simplest form, a pull request is a mechanism that allows a developer to notify other deve...

Learn why Roost is better than Docker
Learn why Roost is better than Docker
November 1, 2021

Roost Enhances the Power of Docker Here at Roost we are frequently asked how our platform compares with Docker, and sinc...

New & Unique Way to do CI so Code Changes are Always Production-Ready
New & Unique Way to do CI so Code Changes are Always Production-Ready
November 1, 2021

So, what really is the primary purpose of continuous integration (CI)? The primary purpose of CI is to integrate code/se...