Managed instance group
Group of identical VMs created from an instance template, with optional autoscaling and autohealing.
- Provider
- gcp
- Kind
- Virtual machine
- Category
- Compute
- Also known as
- MIG
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| autohealing | boolean | — | no | false | inherited |
| autoscaling | boolean | — | no | false | inherited |
| diskEncryption | boolean | — | no | — | ▸ true |
| instances | integer | — | no | — | inherited |
| managed | boolean | — | no | false | ▸ true |
| maxSize | integer | — | no | 1000 | inherited |
| memoryGib | integer | — | no | — | inherited |
| os | enum | linux | windows | aix | ibm-i | no | linux | inherited |
| publicIp | boolean | — | no | — | inherited |
| scope | enum | zonal | regional | no | zonal | 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: "managed-instance-group", component: "google-managed-instance-group" }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 managed instance group: Compute Engine keeps a group of identical VMs alive from an # instance template ("Instance groups"). A zonal MIG deploys to a single zone and holds up to 1,000 # VMs; a regional MIG spreads across zones of one region and holds up to 2,000. Autoscaling and # autohealing are opt-in. schemaVersion: "1" type: "component" id: "google-managed-instance-group" kind: "virtual-machine" provider: "gcp" docs: "https://cloud.google.com/compute/docs/instance-groups" aliases: ["MIG"] defaults: managed: true diskEncryption: true zoneRedundant: false properties: scope: type: "enum" values: ["zonal", "regional"] default: "zonal" autoscaling: type: "boolean" default: false autohealing: type: "boolean" default: false maxSize: type: "integer" default: 1000