Template on a vSphere Supervisor setting reservations, memory and CPU for VKS cluster nodes and VMs. DevOps users can only pick it once it has been added to their vSphere Namespace.
Read more: Broadcom TechDocs
In the Ultra Transcenders books
Each book explains VM class in context, with comparison tables and the common traps.
Terms in this definition
- Template
A golden image for deploying VMs that cannot itself be started or edited; to change one, turn it back into a VM, update it and convert again, or clone it.
- vSphere Supervisor
Formerly known as vSphere with Tanzu. It gives vSphere clusters a Kubernetes API, declarative in style, through which VKS clusters, vSphere Pods and VMs are run inside namespaces; it underpins VCF Automation.
- CPU
The processor that runs a VM's workload (central processing unit); while B-series VMs run under their baseline, they accumulate CPU credits.
- VKS
Supervisor service, previously the Tanzu Kubernetes Grid Service, that deploys and looks after VMware-supported upstream Kubernetes clusters inside vSphere Namespaces.
- Virtual machines
Infrastructure-as-a-service compute giving complete control of the operating system, making it a fit for lift-and-shift moves and for software relying on OS-level pieces like COM.
- vSphere Namespace
An area on a Supervisor, with caps on CPU, memory, storage and Kubernetes objects, in which VMs, vSphere Pods, VKS clusters and Supervisor Services run. VCF Automation creates them within a project, drawing on the organisation's region quota.
Related terms
- Best-effort VM class
Unlike a guaranteed class, which reserves its full request, this kind of vSphere Supervisor VM class sets no reservation for memory or CPU, which permits overcommitment.
- Guaranteed VM class
Suitable for production, this vSphere Supervisor VM class edition sets aside all of the memory and CPU it asks for, unlike best-effort classes, which reserve none and can be overcommitted.