VMware vSphere
Virtual machinevsphere
ESXi type-1 hypervisor with vCenter Server, clustering, vMotion and optional key-provider-backed VM encryption.
- Provider
- default
- Kind
- Virtual machine
- Category
- Compute
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| clusterServices | enum | none | ha | drs | ha-drs | no | none | inherited |
| diskEncryption | boolean | — | no | — | ▸ false |
| instances | integer | — | no | — | inherited |
| keyProvider | enum | none | native | standard-kms | no | none | inherited |
| managed | boolean | — | no | false | ▸ false |
| memoryGib | integer | — | no | — | inherited |
| os | enum | linux | windows | aix | ibm-i | no | linux | inherited |
| publicIp | boolean | — | no | — | inherited |
| sizeVcpu | integer | — | no | — | inherited |
| vmotion | boolean | — | no | false | inherited |
| vsanStorage | boolean | — | no | false | inherited |
| zoneRedundant | boolean | — | no | — | inherited |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
stateful-node-without-zone-redundancy
A stateful compute node pinned to exactly one availability zone disappears with that zone, and its state goes with it. Nodes inside a cell are exempt, because there the cell is deliberately single-zone and redundancy comes from the other cells.
- — all of these hold:
- — the node's `stateless` is false
- — the node sits inside exactly 1 availability-zone group
- — this does not hold:
- — the node sits inside at least one cell group
nodes:
- { id: "vsphere", component: "vsphere" }Auto Scalingalibaba-auto-scalingElastic Compute Servicealibaba-ecsEdge Node Servicealibaba-ensSimple Application Serveralibaba-simple-application-serverAmazon EC2aws-ec2Amazon EC2 Auto Scalingaws-ec2-auto-scalingAmazon EC2 Dedicated Hostsaws-ec2-dedicated-hostAmazon Elastic VMware Serviceaws-evsAmazon Lightsailaws-lightsailAWS Nitro Enclavesaws-nitro-enclaveAzure BareMetal Infrastructureazure-baremetal-infrastructureAzure Compute Fleetazure-compute-fleetAzure Dedicated Hostazure-dedicated-hostAzure Data Science Virtual Machineazure-dsvmNutanix Cloud Clusters on Azureazure-nutanix-cloud-clustersAzure Virtual Machinesazure-virtual-machineAzure Virtual Machine Scale Setsazure-vm-scale-setAzure VMware Solutionazure-vmware-solutionCrusoe Cloud VMcrusoeFirecrackerfirecrackerMicrosoft Hyper-Vhyper-vKubeVirtkubevirtLambda Cloud instancelambda-labsKVM with libvirtlibvirtNebius AI Cloud VMnebiusNutanix AHVnutanix-ahvOpenStack Novaopenstack-novaoVirtovirtProxmox VEproxmoxRunpod PodrunpodVast.ai instancevast-aiGeneric virtual machinevirtual-machineXCP-ngxcp-ngXenServerxenserverDigitalOcean Bare Metal GPUsdigitalocean-bare-metal-gpuDropletsdigitalocean-dropletDroplet Autoscale Pooldigitalocean-droplet-autoscaleBare Metal Solutiongoogle-bare-metal-solutionCloud TPUgoogle-cloud-tpuCompute Enginegoogle-compute-engine
and 20 more → Virtual machine page# yaml-language-server: $schema=../../schema/component.schema.json # VMware vSphere with ESXi, the type-1 hypervisor plus vCenter Server. Per "vSphere Native Key Provider # Overview" vCenter Server ships with no key provider configured, so virtual machine and vSAN encryption are # off until an administrator sets one up. schemaVersion: "1" type: "component" id: "vsphere" kind: "virtual-machine" provider: "default" docs: "https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/vsphere-security/configuring-and-managing-vsphere-native-key-provider/vsphere-native-key-provider-overview.html" defaults: managed: false diskEncryption: false properties: keyProvider: type: "enum" values: ["none", "native", "standard-kms"] default: "none" clusterServices: type: "enum" values: ["none", "ha", "drs", "ha-drs"] default: "none" vsanStorage: type: "boolean" default: false vmotion: type: "boolean" default: false