See how easy it is for developers to create a Kubernetes multi-tenant cluster and share it with others
The power behind Kubernetes is the fact it provides features to manage multi-tenant clusters like 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 the Roost platform you can create a multi-node Kubernetes cluster on cloud environments like GCP, AWS, Azure. 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 which provides a unified Kubernetes cluster analytics view. In addition, an admin role can compare various Namespaces on Roost's Admin Dashboard.
With Roost you can instantly create a multi-node Kubernetes
cluster and set the duration of that it runs.
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.
We makes it easy for development leads to create team k8s clusters and easily share the cluster with stakeholders. 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 (Roost calls this an ephemeral pre-production environment) means less overhead. With Roost environment as a service platform, 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 (what Roost calls an ephemeral pre-production environment) and share it with an stakeholder via a custom URL. Stakeholders no longer have to wait to see the change in production!
2. On-demand create ephemeral environments for your sales team to show product demos on top of Roost K8s. Sales teams feel confident they have the latest features and correct version.
3. Build a namespace-based multi-tenancy as per your need.
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.