Sole-tenant node group
Physical Compute Engine servers in one zone dedicated to a single project's VMs.
- Provider
- gcp
- Kind
- Virtual machine
- Category
- Compute
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| autoscaling | boolean | — | no | false | inherited |
| cpuOvercommit | boolean | — | no | false | inherited |
| dedicatedHardware | boolean | — | no | true | inherited |
| diskEncryption | boolean | — | no | — | ▸ true |
| instances | integer | — | no | — | inherited |
| maintenancePolicy | enum | default | restart-in-place | migrate-within-node-group | no | default | 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 |
| zoneRedundant | boolean | — | no | — | ▸ false |
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: "sole-tenant-node", component: "google-sole-tenant-node" }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-machineVMware vSpherevsphereXCP-ngxcp-ngXenServerxenserverDigitalOcean Bare Metal GPUsdigitalocean-bare-metal-gpuDropletsdigitalocean-dropletDroplet Autoscale Pooldigitalocean-droplet-autoscaleBare Metal Solutiongoogle-bare-metal-solutionCloud TPUgoogle-cloud-tpu
and 20 more → Virtual machine page# yaml-language-server: $schema=../../schema/component.schema.json # Compute Engine sole-tenant node group: a homogeneous set of physical Compute Engine servers in one # zone dedicated to a single project's VMs ("Sole-tenant nodes"). The default host maintenance policy # is the same live-migration behaviour as non-sole-tenant VMs; node group autoscaling and vCPU # overcommit are both opt-in. schemaVersion: "1" type: "component" id: "google-sole-tenant-node" kind: "virtual-machine" provider: "gcp" docs: "https://cloud.google.com/compute/docs/nodes/sole-tenant-nodes" defaults: managed: false diskEncryption: true zoneRedundant: false properties: dedicatedHardware: type: "boolean" default: true maintenancePolicy: type: "enum" values: ["default", "restart-in-place", "migrate-within-node-group"] default: "default" autoscaling: type: "boolean" default: false cpuOvercommit: type: "boolean" default: false