Skip to main content
Version: main ๐Ÿšง

Deliver services to tenants

This section covers how one platform serves several organizations. Each organization is a tenant. Inside a tenant, projects group users and teams, and templates decide which clusters, apps, and Stacks they can create. Platform admins, tenant admins, and project admins all work here, each at a different level.

A tenant is the boundary that separates one customer from another inside vCluster Platform, and it sits above projects.

How Platform organizes tenantsvCluster PlatformSystem admininstalls PlatformPlatform admincreates tenantsTenant adminmanages infrastructureand projectsProject adminmanages project accessProject usercreates clustersTenant ยท acmeAssigned infrastructureMachines and networksProject ยท defaultClusterClusterProject ยท researchClusterTenant ยท globexAssigned infrastructureMachines and networksProject ยท defaultClusterClusterProject ยท operationsCluster
Tenant admins use assigned infrastructure and manage projects. Project admins manage access and resources within a project. Project users create clusters.

For an AI cloud operator, a tenant is the customer account. For an internal platform, it's the business unit or the subsidiary. Everything that customer can see, provision, and configure is decided by the platform admin, individually per tenant.

Tenant, not cluster

A tenant is an organization. A cluster is the Kubernetes environment a project user creates. They're different things, and a tenant contains many clusters.

Tenants in the hierarchyโ€‹

Platform hands responsibility down a chain. Each role delegates a narrower boundary to the next.

StepWhoWhat they do
1System adminInstalls Platform onto a Kubernetes cluster. That cluster becomes the control plane cluster.
2Platform adminCreates tenants and grants each one the inventory it may consume.
3Tenant adminUses the tenant's assigned machines and networks, and divides its grant across projects.
4Project adminManages the project's members and resources.
5Project userCreates clusters inside a project.

A platform admin never hands a customer raw infrastructure. They grant a tenant a slice of what the platform already has, and the tenant admin decides how to split that slice across their own teams.

Tenants are optionalโ€‹

A platform with no tenants behaves exactly as it did before tenants existed. Projects remain the organizing unit, and project permissions still scope project admins and members. Platform admins aren't constrained by a tenant boundary.

Create tenants when more than one organization shares your platform and those organizations shouldn't see each other. If you're running a single internal platform where every admin is trusted with the whole inventory, projects alone are enough.

How the tenant boundary worksโ€‹

Every tenant starts with no access to platform inventory. A platform admin grants each one capabilities, such as the control plane clusters, node types, OS images, and templates it may use. They can also assign a resource such as a physical machine or a network environment to one tenant exclusively.

A user's effective access is the intersection of their role, the tenant boundary, and the project boundary. A tenant admin holds broad rights, but those rights stop at the edge of their tenant.

Read the details in What are tenants โ†’

Work in this sectionโ€‹

The rest of this section follows the same handoff. A platform admin creates tenants and sets their boundaries. A tenant admin organizes projects, users, and teams inside one tenant. Project admins then decide what their members can create, through templates, quotas, and project secrets. If you're new to the model, read what projects are and how users and teams work next.