vMetal turns a Machine request into a provisioned physical server through a stable API and infrastructure driver. Provisioned Machines can register with the target tenant cluster automatically, and released capacity returns to inventory.
Manual bare metal provisioning creates inconsistent server state and slows capacity delivery.
Unprovisioned GPU servers cannot serve tenant workloads or be offered as available capacity.
Manual PXE, OS, and network steps introduce variation between servers and data centers.
Without a stable Machine model, each new infrastructure driver requires different automation and lifecycle handling.
vMetal provides one stable Machine API above infrastructure-specific drivers. With Metal3, it automates provisioning and can join completed servers to tenant clusters without a manual kubeadm step.
vMetal automates the repeatable Machine lifecycle from request through provisioning, cluster attachment, release, and reclaim.
With Metal3, vMetal provisions registered servers, installs the selected OS image, applies network configuration, and runs startup automation.
Auto Nodes can create and delete Machine requests to maintain Private Node capacity for tenant clusters.
Metal3 and Netris can place separate tenant network environments on hardware-backed L2 boundaries when configured.
Provisioned Machines can join a tenant cluster automatically as Private Nodes. vCluster remains responsible for the tenant cluster itself.
vMetal tracks Machine claims, server inventory, provisioning state, deletion, cleaning, and return to the available capacity pool.
This isn’t a side project. Behind every vCluster deployment is 5+ years of deep K8s engineering, security hardening, and battle-tested infrastructure work at massive scale.
Talk to our team about your stack
Deploy vCluster on your infra in minutes
Go live with a hyperscaler-grade tenant experience in days
Zero-touch bare metal provisioning automates the repeatable steps after servers and credentials have been registered. With Metal3, vMetal drives provisioning, OS installation, network configuration, and startup automation through the Machine lifecycle.
vMetal uses interchangeable drivers behind one Machine API. Current documentation lists Metal3, KubeVirt, BCM for existing installations, Terraform or OpenTofu, and Cluster API mechanisms. Driver capabilities and availability should be checked in their documentation.
vMetal provisions Bare Metal Machines and Virtual Machines. vCluster can then consume those Machines as Private Nodes for managed tenant cluster products.
vMetal supplies the Machine. vCluster supplies the tenant cluster and requests or releases capacity through Private Nodes and Auto Nodes. vCluster Standalone is a separate deployment option for running Kubernetes directly on Linux.
Provisioning time depends on the hardware state, driver, OS image, network setup, and startup automation. vMetal standardizes the workflow and lifecycle model across those inputs.
Network configuration depends on the selected driver and integration. With Metal3 and Netris configured, separate network environments can provide hardware-backed L2 isolation for tenant infrastructure.
See how vMetal automates bare metal provisioning from rack to production-ready inventory.
