Azure Compute Fleet
Bulk capacity acquisition across many VM sizes, zones and pricing models in one request.
- Provider
- azure
- Kind
- Virtual machine
- Category
- Compute
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| diskEncryption | boolean | — | no | — | ▸ true |
| fleetMode | enum | managed | launch | no | managed | inherited |
| instances | integer | — | no | — | inherited |
| managed | boolean | — | no | false | ▸ false |
| maxVmCount | integer | — | no | 10000 | inherited |
| memoryGib | integer | — | no | — | inherited |
| mixesSpotAndStandard | boolean | — | no | true | inherited |
| multiRegion | boolean | — | no | false | inherited |
| os | enum | linux | windows | aix | ibm-i | no | linux | inherited |
| publicIp | boolean | — | no | — | inherited |
| sizeVcpu | integer | — | no | — | 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: "compute-fleet", component: "azure-compute-fleet" }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 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-tpuCompute Enginegoogle-compute-engine
and 20 more → Virtual machine page# yaml-language-server: $schema=../../schema/component.schema.json # Azure Compute Fleet: one API call that acquires capacity across many VM sizes and pricing models, # mixing Spot and standard VMs ("Azure Compute Fleet overview"). Managed mode is the default and # keeps the fleet in place; a fleet targets up to 10,000 VMs and one region unless configured wider. schemaVersion: "1" type: "component" id: "azure-compute-fleet" kind: "virtual-machine" provider: "azure" docs: "https://learn.microsoft.com/en-us/azure/azure-compute-fleet/overview" defaults: managed: false diskEncryption: true properties: fleetMode: type: "enum" values: ["managed", "launch"] default: "managed" mixesSpotAndStandard: type: "boolean" default: true maxVmCount: type: "integer" default: 10000 multiRegion: type: "boolean" default: false