Preemptible VM

Related topics

• managed instance group works with Preemptible VM From the official documentation: “You can create preemptible instances in a [managed instance group](/compute/docs/instance-groups/manager).”
• Preemptible VM is an alternative to Spot VMs From the official documentation: “Preemptible VMs are being replaced by Spot VMs.”
• managed instance group is part of Compute Engine From the official documentation: “Checks if a Compute Engine Managed Instance Group (MIG) is configured as Zonal.”
• managed instance group works with Spot VMs From the official documentation: “This document explains how to create a managed instance group (MIG) that uses Spot VMs.”
• managed instance groups is part of Compute Engine From the official documentation: “Compute Engine provides a straightforward way to implement autoscaling through managed instance groups.”
• Spot VMs is part of Compute Engine From the official documentation: “Spot VMs are virtual machine (VM) instances that are excess Compute Engine capacity.”
• Cluster Autoscaler configures managed instance group From the official documentation: “Cluster autoscaler increases or decreases the size of the node pool automatically by adding or removing virtual machine (VM) instances in the underlying Compute Engine [Managed Instance Group (MIG)](/compute/docs/instance-groups#managed_instance_groups) for the node pool.”
• Cluster Autoscaler works with Spot VMs From the official documentation: “Both the cluster autoscaler and node auto-provisioning support using Spot VMs.”
• Compute Engine works with custom machine type From the official documentation: “This sample demonstrates how to create custom machine types for use with Compute Engine instances.”
• custom machine type works with managed instance group From the official documentation: “You can similarly create [Spot VMs](/compute/docs/instances/spot) and [managed instance groups (MIGs)](/compute/docs/instance-groups) with custom machine types.”
• custom machine type works with Spot VMs From the official documentation: “You can similarly create [Spot VMs](/compute/docs/instances/spot) and [managed instance groups (MIGs)](/compute/docs/instance-groups) with custom machine types.”
• Flex-start configures managed instance group From the official documentation: “- **Flex-start**: Create a [managed instance group (MIG)](/compute/docs/instance-groups#managed_instance_groups) for either A3 High or G4 machine types.”
• Flex-start works with managed instance groups From the official documentation: “When you add Flex-start VMs to a managed instance group (MIG) by using resize requests, the MIG creates the VMs all at once.”
• Flex-start works with Spot VMs From the official documentation: “Using Spot VMs combined with flex-start provides a fallback option when Spot VMs capacity is unavailable.”
• Flex-start is an alternative to Spot VMs From the official documentation: “**Important:** For A3 High VMs, unless you use the `a3-highgpu-8g` machine type, [only Flex-start VMs and Spot VMs are supported](/compute/docs/accelerator-optimized-machines#consumption_option_availability_by_machine_type).”
• managed instance group is part of managed instance groups From the official documentation: “You can build highly available deployments of stateful workloads on VMs using stateful managed instance groups (stateful MIGs).”
• managed instance groups works with Spot VMs From the official documentation: “You can create Spot VMs in a [MIG](/compute/docs/instance-groups/manager) by specifying the spot provisioning model in an [instance template](/compute/docs/instance-templates) before you create or update the group.”