SPOT

Related topics

• flex-start is an alternative to SPOT From the official documentation: “When you create a compute instance, you can specify one of the following provisioning models. If you don't specify a provisioning model, then Compute Engine uses the standard provisioning model by default. - Standard - Spot - Flex-start - Reservation-bound”
• reservations is an alternative to SPOT From the official documentation: “Instance template configurations vary based on the consumption option you use: on-demand, Spot, reservations, or Flex-start.”
• SPOT configures instance template From the official documentation: “The following command creates an instance template that uses the *Spot* consumption option:”
• SPOT depends on Spot VMs From the official documentation: “- `SPOT`: Provisions the node pool using Spot VMs.”
• SPOT is an alternative to standard provisioning model From the official documentation: “When you create a compute instance, you can specify one of the following provisioning models. If you don't specify a provisioning model, then Compute Engine uses the standard provisioning model by default. - Standard - Spot - Flex-start - Reservation-bound”
• instance template configures managed instance group From the official documentation: “Create the MIG using the template.”
• managed instance group depends on instance template From the official documentation: “All MIGs require an instance template.”
• instance template works with managed instance group From the official documentation: “Create a global instance template that you can use to create a managed instance group (MIG) of GPU VMs.”
• instance template is part of Compute Engine From the official documentation: “An instance template is an immutable Compute Engine resource that stores VM configuration.”
• 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.”
• managed instance groups depends on instance template From the official documentation: “Create multiple regional managed instance groups using the instance template.”
• reservations is part of Compute Engine From the official documentation: “Reservations are a Compute Engine feature.”
• Spot VMs is part of Compute Engine From the official documentation: “Spot VMs are virtual machine (VM) instances that are excess Compute Engine capacity.”
• flex-start configures instance template From the official documentation: “The following command creates an instance template that uses the *Flex-start* consumption option:”
• 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 is an alternative to reservations From the official documentation: “Instance template configurations vary based on the consumption option you use: on-demand, Spot, reservations, or Flex-start.”
• 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).”
• instance template is part of managed instance group From the official documentation: “Each VM in a MIG is based on an instance template.”
• instance template configures managed instance groups From the official documentation: “Using the instance template, configure a [managed instance group](/compute/docs/instance-groups/creating-groups-of-managed-instances) with a target size of 1.”
• instance template configures spot provisioning model 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.”
• 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.”
• Spot VMs depends on spot provisioning model From the official documentation: “Specifically, Spot VMs are VMs that use the *spot provisioning model*.”