Smart Management of OpenShift Clusters Across Tenants
We have seen many teams grappling with the primitives to try and achieve multi-tenancy in OpenShift Clusters, so we came up with the idea of Tenant Operator. Tenant Operator brings single-point visibility of teams, members, and workloads to the cluster owners or administrators.
With Tenant Operator, you can:
Share an OpenShift cluster with multiple tenants
Share managed applications with multiple tenants
Configure and manage tenants and their sandboxes
Add other key features of TO
There can be a small infographic that says RedHat certified operator with RedHat logo on top of these bullet points
Runs on OpenShift
Certified operators & images
Continuous vulnerability scans
Optimize your costs and resources
Share a cluster across teams, groups, or departments and save operational efforts
Code and Gitops Ready
No additional management layers, plugins, or customized binaries
Self-Service Namespaces: Manage namespaces, isolate at team or user level, create sandboxed dev namespaces with ease
Configure RBAC with a "least privilege" mindset and keep all rules up-to-date with zero manual effort
Define policies to Self-manage namespaces, quotas, resources, groups, and Limit Ranges
Use templating for predefined templates, define and distribute custom templates and use them on individual namespaces or across tenant-level namespaces.
Integrations with Vault, ArgoCD AppProject, and Slack.
Deploy With Ease
Follow these easy steps to install and use Tenant Operator
Operator installation with OperatorHub
Installing from OperatorHub using the web console
Installing from OperatorHub using the CLI
Ready to Get Started?
Choose a plan that suits your needs
Save upto 25%