# Platform v5.0 and vCluster v0.38 enable Private Customer Clouds

Canonical: https://brew.new/templates/vcluster/platform-v5-0-and-vcluster-v0-38-enable-private-customer-clouds

Brand: vcluster.com
Category: promotional

![Preview of Platform v5.0 and vCluster v0.38 enable Private Customer Clouds](https://cdn.brew.new/email-preview-6bb13f61a84cecfa-tracking_r57rfsp0xqa9cp846dtsys8b9n8jgvmz-1795098118398.png)

## Email content

vCluster

Platform v5.0 and vCluster v0.38 enable Private Customer Clouds

Platform v5.0 and vCluster v0.38 enable Private Customer Clouds

Give every customer a private, self-service cloud on hardware you already own. Platform v5.0 brings tenant isolation, customer administration, and infrastructure access into one model. Paired with vCluster v0.38, it connects the boundaries you set for each organization to the clusters its teams create and run.

Why v5.x

AI cloud providers want to build services on top of the capacity they already sell. That requires more than provisioning a cluster. Each customer needs a place to manage its people, machines, networks, and operating system choices within limits the provider controls.

Platform v5.0 introduces a new Tenant boundary that connects those pieces. vMetal turns the rack into inventory. The tenant turns that inventory into a customer's cloud. vCluster and Stacks turn that cloud into services, including Kubernetes, Slurm, Ray, inference, and more.

For AI cloud providers, that means organizing your offering around each customer. For enterprise platform teams, it means giving business units more autonomy within centrally defined policies. Platform admins decide what infrastructure is available. Tenant admins manage their organization's users, projects, and access to assigned infrastructure. Project admins manage access and settings within a project. Project users create clusters within those limits.

i

Platform v5.0 and vCluster v0.38 are limited availability releases, recommended only for new deployments. Work with vCluster Labs to evaluate the new capabilities.

Give each customer a tenant boundary

Platform v5.0 introduces the Tenant resource above projects. Each tenant represents a customer, business unit, or other organization, with its own users, projects, and infrastructure allowances.

That gives you a clear place to delegate. Tenant admins can see the machines and networks available to their organization and manage its teams and projects. Project admins organize work within a project, while platform admins retain control of the resources each tenant can use. Customize the UI per tenant with its own branding and settings.

Diagram titled "How Platform organizes tenants". There are five layers of roles listed along the left side. System admin installs platform, platform admin creates tenants, tenant admin manages infrastructre and projects, project admin manages project access, and a project user creates clusters. The diagram shows a large box for the vCluster Platform. Within that box are two smaller boxes side by side, one for Tenant acme and one for Tenant globex. Each tenant has assigned infrastructure for machines and networks. Each tenant contains two projects. One project of each tenant has two clusters and the other project has a single cluster.

Give each customer its own organizational boundary. Tenant admins manage the organization's infrastructure and projects. Project admins manage individual projects. Project users create clusters.

Give each customer its own organizational boundary. Tenant admins manage the organization's infrastructure and projects. Project admins manage individual projects. Project users create clusters.

You can curate the cluster templates, Stacks, node types, images, and integrations available to each tenant. Teams get a self-service catalog shaped around their needs, and administrators keep the policy decisions that govern it.

Explore tenant administration in Platform v5.0.

Bring NICo capacity into the same workflows

With Platform v5.0, vMetal adds NVIDIA Infrastructure Controller (NICo) as a provisioning driver alongside Metal3. Offer NICo-backed capacity through administrator-defined node types, with machines reserved for a tenant or allocated on demand.

Tenants, network environments, and Platform identity connect that capacity to the same administration model. NICo remains Alpha and may include breaking changes in future releases.

Turn infrastructure into a customer offering

Different customers need different capacity. Reserve machines for a tenant's contract, or offer on-demand allocation from a common capacity pool. vMetal, the infrastructure orchestrator beneath vCluster, brings those choices into one machine inventory across Metal3 and NICo. It orchestrates the provisioning drivers, while Platform connects that capacity to tenant access and self-service.

Start, stop, and reboot bare metal machines from Platform, as you already could with KubeVirt VMs.

Networking and operating system images become part of the offering. Administrators choose the network environments a tenant can use, including networking backed by Netris or NICo. Metal3-backed infrastructure can also use Aviz-backed network environments. Tenants can also bring their own OS images when that capability is enabled, alongside images the provider makes available.

Separate the service from its infrastructure

Node pools are a new Platform resource attached to a cluster. The operator's cluster template defines the managed service. The tenant's node pools define the compute and network choices that support it, using infrastructure the tenant owns or has been assigned.

Set a fixed node count or let a dynamic pool respond to workload demand. The service definition and its capacity can be managed separately, following the node-pool model familiar from hyperscaler services.

Connect your existing inventory with NetBox

The NetBox integration imports selected device records into Platform's machine inventory for Metal3 provisioning. That connects the hardware records your team maintains in NetBox to the capacity you offer through Platform.

See Platform node pools and machine allocation for the workflows and requirements.

Connect capacity to AI workloads

Infrastructure is the foundation of the service. The applications running on it are what teams consume.

Build on Stacks such as NVIDIA Dynamo to give teams a repeatable AI-serving environment. Stacks bring related applications together as one dependency-aware deployment, so teams can start from a defined application offering.

Together, tenant access, infrastructure allocation, and Stacks connect the path from available capacity to an environment teams can use.

Explore Stacks.

Run the clusters behind the offering

vCluster v0.38 supports the new Platform-managed node pools attached to a cluster. It also improves how node claims respond to configuration changes and missing machines, and includes local development, networking, and recovery improvements.

Some supporting improvements also shipped in v0.37 patch releases. What's new in vCluster v0.38 explains the capabilities and requirements. The release notes identify the exact changes and patch-release overlap.

Plan your evaluation

If you are expanding customer self-service, delegating administration across business units, or bringing more infrastructure into a common offering, evaluate how Platform v5.0's tenant and capacity model fits your plans. The goal is a hyperscaler-quality customer experience, with self-service clusters and tenant isolation on infrastructure you control.

Platform v5.0 and vCluster v0.38 are limited availability releases, recommended only for new deployments. If you need the new capabilities on an existing installation, contact vCluster Labs to discuss your use case and plan the upgrade.

Use the Platform v5.0 release notes and vCluster v0.38 release notes to review how the new releases differ from v4.12 and v0.37, including removed features, breaking changes, and known issues.

!

Coming from Platform v4.12? Platform v5.0 removes shared secrets, cost control, the project-level Argo CD integration, and the bundled infrastructure apps, and deprecates project namespaces (spaces). Apps and the example Helm, Bash, and Manifests apps remain available. See the removed features and breaking changes in the release notes.

To our v4.x customers

There's no rush to move to 5.x. Platform v5.0 and vCluster v0.38 are recommended only for new deployments. For upgrade guidance, contact vCluster Labs. Platform v4.12 and vCluster v0.37 form the LTS release set and are supported as a pair. vMetal in Platform v4.12 follows the same lifecycle.

LTS provides 12 months of active support, followed by six months of critical security updates. During active support, you can request backports of fixes, including support for newer Kubernetes versions. Upgrading either product past its LTS version takes that combination off LTS.

See the LTS policy and support dates, and work with vCluster Labs when you are ready to evaluate v5.x.

● vCluster

View Update

vCluster · Unsubscribe

[Open and remix this design](https://brew.new/templates/vcluster/platform-v5-0-and-vcluster-v0-38-enable-private-customer-clouds)

[Browse email designs](https://brew.new/browse/templates)
