Stay organized with collections Save and categorize content based on your preferences.
This document describes how to create resize requests in a managed instance group (MIG) of virtual machine (VM) instances that have attached GPUs. To learn more about resize requests, see About resize requests in a MIG.
Creating a MIG resize request helps you obtain highly-demanded resources, like GPUs, and optimize costs by creating the exact number of VMs all at once. To create a MIG resize request that can use the features and services available from Cluster Director, see Create a MIG and a resize request in the AI Hypercomputer documentation.
Before you beginSelect the tab for how you plan to use the samples on this page:
ConsoleWhen you use the Google Cloud console to access Google Cloud services and APIs, you don't need to set up authentication.
gcloudInstall the Google Cloud CLI. After installation, initialize the Google Cloud CLI by running the following command:
gcloud init
If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.
Note: If you installed the gcloud CLI previously, make sure you have the latest version by runninggcloud components update
.To use the REST API samples on this page in a local development environment, you use the credentials you provide to the gcloud CLI.
Install the Google Cloud CLI. After installation, initialize the Google Cloud CLI by running the following command:
gcloud init
If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.
For more information, see Authenticate for using REST in the Google Cloud authentication documentation.
To get the permissions that you need to create MIG resize requests, ask your administrator to grant you the Compute Instance Admin (v1) (roles/compute.instanceAdmin.v1
) IAM role on the project. For more information about granting roles, see Manage access to projects, folders, and organizations.
This predefined role contains the permissions required to create MIG resize requests. To see the exact permissions that are required, expand the Required permissions section:
Required permissionsThe following permissions are required to create MIG resize requests:
compute.instanceTemplates.create
on the project compute.instanceGroupManagers.create
on the project compute.instanceGroupManagers.update
on the projectYou might also be able to get these permissions with custom roles or other predefined roles.
Prepare a MIG for resize requestsTo create a MIG resize requests, you must configure an instance template and the MIG as described in the following sections.
Create an instance templateBased on your use case for MIG resize requests, create an instance template by using one of the following methods:
If you want to create VMs as soon as resources are available for workloads that run for up to seven days, then create an instance template by using the flex-start provisioning model.
If you want to create VMs by consuming an auto-created reservation for a future reservation in calendar mode, then create an instance template by using the reservation-bound provisioning model.
Preview — The flex-start provisioning model
This feature is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of the Service Specific Terms. Pre-GA features are available "as is" and might have limited support. For more information, see the launch stage descriptions.
To create an instance template configured for MIG resize requests and for creating VMs as soon as resources are available, you must specify the following in the template:
Use a GPU machine type, except the A4X machine type.
Stop VMs during host maintenance events.
Delete VMs at the end of their run duration by using the maxRunDuration
and instanceTerminationAction
fields.
Use the flex-start provisioning model.
To create an instance template, select one of the following options:
ConsoleIn the Google Cloud console, go to the Instance templates page.
Click Create instance template. The Create an instance template page opens.
In the Name field, enter a name for the instance template.
In the Location section, select one of the following options:
To create a regional instance template, select Regional (recommended), and then select the region in which to create the template.
To create a global instance template, select Global.
In the Machine configuration section, do the following:
Click the GPUs tab.
In the GPU type list, select a GPU type.
In the Number of GPUs list, select the number of GPUs.
Optional: If your chosen GPU type supports NVIDIA RTX Virtual Workstations (vWS) for graphics workloads, and you plan to run graphics-intensive workloads, then select Enable Virtual Workstation (NVIDIA GRID).
In the Machine type section, select a machine type.
In the Provisioning model section, complete the following steps:
In the VM provisioning model field, select Flex-start.
Expand VM provisioning model advanced settings.
Select the Set a time limit for the VM checkbox.
To set a run duration for the VMs created through the instance template, in the Enter number of hours field, enter the number of hours. The value must be between 36 seconds (0.01
) and seven days (168
).
Optional: To change the default value boot disk type or image, in the Boot disk section, click Change. Then, follow the prompts to change the boot disk.
Click Create.
To create an instance template, use the beta instance-templates create
command with the following flags:
The --instance-termination-action
flag set to DELETE
.
The --maintenance-policy
flag set to TERMINATE
.
The --max-run-duration
flag.
The --provisioning-model
flag set to FLEX_START
.
The --reservation-affinity
flag set to none
.
For example, to create a regional instance template, run the following command. If you want to create a global instance template, then use the same command without the --instance-template-region
flag.
gcloud beta compute instance-templates create INSTANCE_TEMPLATE_NAME \
--image-project=IMAGE_PROJECT \
--image-family=IMAGE_FAMILY \
--instance-template-region=REGION \
--instance-termination-action=DELETE \
--machine-type=MACHINE_TYPE \
--maintenance-policy=TERMINATE \
--max-run-duration=RUN_DURATION \
--provisioning-model=FLEX_START \
--reservation-affinity=none
Replace the following:
INSTANCE_TEMPLATE_NAME
: the name of the instance template to create.
IMAGE_PROJECT
: the image project that contains the image; for example, debian-cloud
. For more information about the supported image projects, see Public images.
IMAGE_FAMILY
: an image family. This specifies the most recent, non-deprecated OS image. For example, if you specify debian-12
, the latest version in the Debian 12 image family is used. For more information about using image families, see Image families best practices.
debian-12-bookworm-v20240701
, then replace the --image-family
flag with the --image
flag.REGION
: the region in which to create the instance template.
MACHINE_TYPE
: the GPU machine type to use for the VMs. If you specify an N1 machine type, then you must include the --accelerator
flag to define the number and type of GPUs to attach to your VMs.
RUN_DURATION
: the duration you want the requested VMs to run. You must format the value as the number of days, hours, minutes, or seconds followed by d
, h
, m
, and s
respectively. For example, specify 30m
for 30 minutes or 1d2h3m4s
for one day, two hours, three minutes, and four seconds. The value must be between 10 minutes and seven days.
To create an instance template, make a POST
request to one of the following methods:
To create a regional instance template: beta regionInstanceTemplates.insert
method
To create a global instance template: beta instanceTemplates.insert
method
In the request body, include the following fields:
The reservationAffinity.consumeReservationType
field set to NO_RESERVATION
.
The scheduling.instanceTerminationAction
field set to DELETE
.
The scheduling.maxRunDuration
field.
The scheduling.onHostMaintenance
field set to TERMINATE
.
The scheduling.provisioningModel
field set to FLEX_START
.
For example, to create a regional instance template, make a request as follows:
POST https://compute.googleapis.com/compute/beta/projects/PROJECT_ID/regions/REGION/instanceTemplates
{
"name": "INSTANCE_TEMPLATE_NAME",
"properties": {
"disks": [
{
"boot": true,
"initializeParams": {
"sourceImage": "projects/IMAGE_PROJECT/global/images/IMAGE"
}
}
],
"machineType": "MACHINE_TYPE",
"networkInterfaces": [
{
"network": "global/networks/default"
}
],
"reservationAffinity": {
"consumeReservationType": "NO_RESERVATION"
},
"scheduling": {
"instanceTerminationAction": "DELETE",
"maxRunDuration": {
"seconds": RUN_DURATION
},
"onHostMaintenance": "TERMINATE",
"provisioningModel": "FLEX_START"
}
}
}
Replace the following:
PROJECT_ID
: the ID of the project in which to create the instance template.
REGION
: the region in which to create the instance template.
INSTANCE_TEMPLATE_NAME
: the name of the instance template to create.
IMAGE_PROJECT
: the image project that contains the image; for example, debian-cloud
. For more information about the supported image projects, see Public images.
IMAGE
: specify one of the following:
A specific version of the OS image—for example, debian-12-bookworm-v20240617
.
An image family, which must be formatted as family/IMAGE_FAMILY
. This specifies the most recent, non-deprecated OS image. For example, if you specify family/debian-12
, the latest version in the Debian 12 image family is used. For more information about using image families, see Image families best practices.
MACHINE_TYPE
: the GPU machine type to use for the VMs. If you specify an N1 machine type, then you must include the guestAccelerators
field to define the number and type of GPUs to attach to your VMs.
RUN_DURATION
: the duration, in seconds, you want the requested VMs to run. The value must be between 600
, which is 600 seconds (10 minutes), and 604800
, which is 604,800 seconds (seven days).
For more information about creating an instance template, see Create instance templates.
Use the reservation-bound provisioning modelTo create an instance template configured for MIG resize requests and for consuming a reservation, you must specify the following in the template:
Use an A4 or A3 Ultra machine type as specified in the reservation.
Stop VMs during host maintenance events.
Delete VMs at the end of the reservation period by using the instanceTerminationAction
field.
Use the reservation-bound provisioning model.
To create an instance template, select one of the following options:
ConsoleIn the Google Cloud console, go to the Instance templates page.
Click Create instance template. The Create an instance template page opens.
In the Name field, enter a name for the instance template.
In the Location section, select one of the following options:
To create a regional instance template, select Regional (recommended), and then select the region in which to create the template.
To create a global instance template, select Global.
In the Machine configuration section, do the following:
Click the GPUs tab.
In the GPU type list, select one of the following options as specified in the reservation that you want to consume:
To use A4 VMs: NVIDIA B200 180GB
To use A3 Ultra VMs: NVIDIA H200 141GB
This action automatically sets the provisioning model of the instance template to Reservation-bound.
In the Number of GPUs list, select the number of GPUs.
Optional: If your chosen GPU type supports NVIDIA RTX Virtual Workstations (vWS) for graphics workloads, and you plan to run graphics-intensive workloads, then select Enable Virtual Workstation (NVIDIA GRID).
In the Machine type section, select a machine type.
In the Provisioning model section, complete the following steps:
Expand VM provisioning model advanced settings.
In the On VM termination list, select Delete.
Optional: To change the default value boot disk type or image, in the Boot disk section, click Change. Then, follow the prompts to change the boot disk.
Expand the Advanced options section, and then do the following:
Expand the Management section.
In the Reservations section, select Choose a reservation, and then click Choose reservation. In the pane that appears, follow the prompts to select the reservation that you want to consume.
Click Create.
To create an instance template, use the instance-templates create
command with the following flags:
The --instance-termination-action
flag set to DELETE
.
The --maintenance-policy
flag set to TERMINATE
.
The --provisioning-model
flag set to RESERVATION_BOUND
.
The --reservation-affinity
flag set to specific
.
The --reservation
flag.
For example, to create a regional instance template, run the following command. If you want to create a global instance template, then use the same command without the --instance-template-region
flag.
gcloud compute instance-templates create INSTANCE_TEMPLATE_NAME \
--image-project=IMAGE_PROJECT \
--image-family=IMAGE_FAMILY \
--instance-termination-action=DELETE \
--instance-template-region=REGION \
--machine-type=MACHINE_TYPE \
--maintenance-policy=TERMINATE \
--provisioning-model=RESERVATION_BOUND \
--reservation-affinity=specific \
--reservation=RESERVATION_URL
Replace the following:
INSTANCE_TEMPLATE_NAME
: the name of the instance template to create.
IMAGE_PROJECT
: the image project that contains the image; for example, debian-cloud
. For more information about the supported image projects, see Public images.
IMAGE_FAMILY
: an image family. This specifies the most recent, non-deprecated OS image. For example, if you specify debian-12
, the latest version in the Debian 12 image family is used. For more information about using image families, see Image families best practices.
debian-12-bookworm-v20240701
, then replace the --image-family
flag with the --image
flag.REGION
: the region in which to create the instance template.
MACHINE_TYPE
: the A4 or A3 Ultra machine type that is specified in the reservation that you want to consume.
RESERVATION_URL
: the URL of the auto-created reservation for a future reservation in calendar mode that you want to consume. Specify one of the following values:
If the auto-created reservation exists in your project: RESERVATION_NAME
.
If the auto-created reservation exists in a different project: projects/PROJECT_ID/reservations/RESERVATION_NAME
.
To create an instance template, make a POST
request to one of the following methods:
To create a regional instance template: regionInstanceTemplates.insert
method
To create a global instance template: instanceTemplates.insert
method
In the request body, include the following fields:
The reservationAffinity.consumeReservationType
field set to SPECIFIC_RESERVATION
.
The reservationAffinity.key
field set to compute.googleapis.com/reservation-name
.
The reservationAffinity.values
field set to the URL of the auto-created reservation.
The scheduling.instanceTerminationAction
field set to DELETE
.
The scheduling.onHostMaintenance
field set to TERMINATE
.
The scheduling.provisioningModel
field set to RESERVATION_BOUND
.
For example, to create a regional instance template, make a request as follows:
POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/instanceTemplates
{
"name": "INSTANCE_TEMPLATE_NAME",
"properties": {
"disks": [
{
"boot": true,
"initializeParams": {
"sourceImage": "projects/IMAGE_PROJECT/global/images/IMAGE"
}
}
],
"machineType": "MACHINE_TYPE",
"networkInterfaces": [
{
"network": "global/networks/default"
}
],
"reservationAffinity": {
"consumeReservationType": "SPECIFIC_RESERVATION",
"key": "compute.googleapis.com/reservation-name",
"values": [
"RESERVATION_URL"
]
},
"scheduling": {
"instanceTerminationAction": "DELETE",
"onHostMaintenance": "TERMINATE",
"provisioningModel": "RESERVATION_BOUND"
}
}
}
Replace the following:
PROJECT_ID
: the ID of the project in which to create the instance template.
REGION
: the region in which to create the instance template.
INSTANCE_TEMPLATE_NAME
: the name of the instance template to create.
IMAGE_PROJECT
: the image project that contains the image; for example, debian-cloud
. For more information about the supported image projects, see Public images.
IMAGE
: specify one of the following:
A specific version of the OS image—for example, debian-12-bookworm-v20240617
.
An image family, which must be formatted as family/IMAGE_FAMILY
. This specifies the most recent, non-deprecated OS image. For example, if you specify family/debian-12
, the latest version in the Debian 12 image family is used. For more information about using image families, see Image families best practices.
MACHINE_TYPE
: the A4 or A3 Ultra machine type that is specified in the reservation that you want to consume.
RESERVATION_URL
: the URL of the auto-created reservation for a future reservation in calendar mode that you want to consume. Specify one of the following values:
If the auto-created reservation exists in your project: RESERVATION_NAME
If the auto-created reservation exists in a different project: projects/PROJECT_ID/reservations/RESERVATION_NAME
For more information about creating an instance template, see Create instance templates.
Create or update a MIGAfter creating the instance template as described in the previous section, use that instance template to create a MIG as follows, or update a MIG. Additionally, you must do the following to prepare the MIG for resize requests:
Set the MIG's update type to opportunistic (default).
If you've configured autoscaling in the MIG, then delete the autoscaling configuration.
If you're using a regional MIG, then set the target distribution shape to ANY_SINGLE_ZONE
.
To create a MIG that is compatible with resize requests, select one of the following options:
ConsoleIn the Google Cloud console, go to the Instance groups page.
Click Create instance group. The Create instance group page opens.
In the Name field, enter a name for the MIG.
Before you select an instance template, you must delete the autoscaling configuration and turn off repairs as follows:
To delete the autoscaling configuration, do the following:
In the Autoscaling section, click the Autoscaling mode list, and then click Delete autoscaling configuration.
In the confirmation dialog, click Delete.
To turn off repairs, in the VM instance lifecycle section, click the Default action on failure list, and then select No action.
Go back to the Instance template field. In the Instance template list, select the instance template that you created in the previous section. If you select a regional instance template, then the Region list is set to the template's region.
Do one of the following:
To create a resize request when you create the MIG, do the following:
In the Number of instances field, enter the number of VMs that you want to create all at once.
Select the Use resize request to create VMs all at once checkbox.
Optional: If the MIG's instance template specifies a run duration, then you can specify a different run duration. To do so, in the Requested run duration field and Unit lists, specify a run duration. You must specify a duration between one hour and seven days.
To create a resize request after you create the MIG, in the Number of instances field, enter 0
.
In the Location section, specify whether you want to create a zonal or a regional MIG as follows:
To create a zonal MIG, select Single zone. Or, to create a regional MIG, select Multiple zones.
Select the Region and Zones of the MIG.
If you're creating a regional MIG, then do the following:
In the Target distribution shape field, select Any single zone.
In the dialog that appears, click Disable instance redistribution.
Click Create.
Use the instance-groups managed create
command with the --default-action-on-vm-failure
flag set to do_nothing
. If you're creating a regional MIG, then you must also include the --target-distribution-shape
flag set to any-single-zone
, and the --instance-redistribution-type
flag set to none
.
To create a zonal MIG, run the following command:
gcloud compute instance-groups managed create INSTANCE_GROUP_NAME \
--template=INSTANCE_TEMPLATE_URL \
--size=0 \
--zone=ZONE \
--default-action-on-vm-failure=do_nothing
To create a regional MIG, run the following command:
gcloud compute instance-groups managed create INSTANCE_GROUP_NAME \
--template=INSTANCE_TEMPLATE_URL \
--size=0 \
--region=REGION \
--target-distribution-shape=any-single-zone \
--instance-redistribution-type=none \
--default-action-on-vm-failure=do_nothing
Replace the following:
INSTANCE_GROUP_NAME
: the name of the MIG to create.
INSTANCE_TEMPLATE_URL
: the partial URL of the instance template that you created in the previous section. If you want to use a regional instance template to create the MIG, then you can only create the MIG within the template's region. Specify one of the following values:
For a regional instance template: projects/PROJECT_ID/regions/REGION/instanceTemplates/INSTANCE_TEMPLATE_NAME
For a global instance template: INSTANCE_TEMPLATE_NAME
ZONE
: the zone in which to create the MIG.
REGION
: the region in which to create the MIG.
To create a zonal MIG, send a POST
request using the instanceGroupManagers.insert
method as follows:
POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/instanceGroupManagers
{
"versions": [
{
"instanceTemplate": "INSTANCE_TEMPLATE_URL"
}
],
"name": "INSTANCE_GROUP_NAME",
"targetSize": 0,
"instanceLifecyclePolicy": {
"defaultActionOnFailure": "DO_NOTHING"
}
}
To create a regional MIG, send a POST
request using the regionInstanceGroupManagers.insert
method as follows:
POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/regions/REGION/instanceGroupManagers
{
"versions": [
{
"instanceTemplate": "INSTANCE_TEMPLATE_URL"
}
],
"name": "INSTANCE_GROUP_NAME",
"targetSize": 0,
"distributionPolicy": {
"targetShape": "ANY_SINGLE_ZONE"
},
"updatePolicy": {
"instanceRedistributionType": "NONE"
},
"instanceLifecyclePolicy": {
"defaultActionOnFailure": "DO_NOTHING"
}
}
Replace the following:
PROJECT_ID
: the ID of the project where the instance template that you created in the previous section exists.
INSTANCE_TEMPLATE_URL
: the partial URL of the instance template that you created in the previous section. If you want to use a regional instance template to create the MIG, then you can only create the MIG within the template's region. Specify one of the following values:
For a regional instance template: regions/REGION/instanceTemplates/INSTANCE_TEMPLATE_NAME
For a global instance template: global/instanceTemplates/INSTANCE_TEMPLATE_NAME
ZONE
: the zone in which to create the MIG.
REGION
: the region in which to create the MIG.
INSTANCE_GROUP_NAME
: the name of the MIG to create.
Preview — Resize requests in regional MIGs and resize request creation by specifying VM names in zonal and regional MIGs.
This feature is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of the Service Specific Terms. Pre-GA features are available "as is" and might have limited support. For more information, see the launch stage descriptions.
Before you create MIG resize requests, make sure that you've prepared the MIG as described in the previous section.
After you create a resize request and all your requested resources become available, the MIG creates the requested number of VMs all at once. The VMs run until the MIG deletes them after the specified run duration ends, or until you delete them.
To create a resize request in a MIG, select one of the following options. To add VMs with specific names to the MIG through a resize request, use the gcloud CLI or REST API.
ConsoleIn the Google Cloud console, go to the Instance groups page.
In the Name column, click the name of the MIG in which to create the resize request.
The overview page of the MIG opens.
In the Resize requests row, click edit Edit resize requests.
Click add New resize request.
The New resize requests pane appears.
In the Name field, enter the name of the resize request.
In the Number of additional instances needed field, enter the number of VMs to add to the MIG all at once.
Optional: If the MIG's instance template specifies a run duration, then you can specify a different run duration. To do so, in the Requested run duration field and Unit lists, specify a run duration. You must specify a duration between one hour and seven days.
Click Create.
To create a resize request in a zonal MIG, use the instance-groups managed resize-requests create
command.
gcloud compute instance-groups managed resize-requests create INSTANCE_GROUP_NAME \
--resize-request=RESIZE_REQUEST_NAME \
--resize-by=COUNT \
--zone=ZONE
To create a resize request in a regional MIG, use the beta instance-groups managed resize-requests create
command.
gcloud beta compute instance-groups managed resize-requests create INSTANCE_GROUP_NAME \
--resize-request=RESIZE_REQUEST_NAME \
--resize-by=COUNT \
--region=REGION
Replace the following:
INSTANCE_GROUP_NAME
: the name of the MIG configured for creating resize requests in it.
RESIZE_REQUEST_NAME
: the name of the resize request, which must be unique within the specified MIG. Otherwise, creating the resize request fails.
COUNT
: the number of VMs to add to the MIG all at once.
ZONE
: the zone where the MIG exists.
REGION
: the region where the MIG exists.
Optionally, you can do the following:
If the MIG's instance template specifies a run duration, then you can specify a different run duration. To do so, include the --requested-run-duration
flag in the command. You must specify a duration between 10 minutes and seven days.
If your workload requires specific VM names, then you can specify a list of names of VMs to create by using the beta instance-groups managed resize-requests create
command. In the command, replace the --resize-request
flag with the --instances
flag.
To create a resize request in a zonal MIG, send a POST
request using the instanceGroupManagerResizeRequests.insert
method.
POST https://compute.googleapis.com/compute/v1/projects/PROJECT_ID/zones/ZONE/instanceGroupManagers/INSTANCE_GROUP_NAME/resizeRequests
To create a resize request in a regional MIG, send a POST
request using the beta.regionInstanceGroupManagerResizeRequests.insert
method.
In the request body, include the following:
{
"name": "RESIZE_REQUEST_NAME",
"resizeBy": COUNT
}
Replace the following:
PROJECT_ID
: the ID of the project where the specified MIG exists.
ZONE
: the zone where the MIG exists.
REGION
: the region where the MIG exists.
INSTANCE_GROUP_NAME
: the name of the MIG configured for creating resize requests in it.
RESIZE_REQUEST_NAME
: the name of the resize request, which must be unique within the specified MIG. Otherwise, creating the resize request fails.
COUNT
: the number of VMs to add all at once to the MIG.
Optionally, you can do the following:
If the MIG's instance template specifies a run duration, then you can specify a different run duration. To do so, include the requestedRunDuration
field in the request body. You must specify a duration, in seconds, between 10 minutes and seven days.
If your workload requires specific VM names, then you can specify a list of names of VMs to create. To do so, send a POST
request to the beta.regionInstanceGroupManagerResizeRequests.insert
method for a regional MIG, or the beta.instanceGroupManagerResizeRequests.insert
method for a zonal MIG. In the request body, replace the resizeBy
field with the instanceNames
field.
Learn how to view, cancel, or delete resize requests in a MIG.
Learn how to view info about MIGs and managed VMs.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-07 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["This document guides users on creating resize requests in a managed instance group (MIG) for virtual machines (VMs) with attached GPUs to optimize resource allocation."],["Before creating a resize request, users must review how resize requests work, check their GPU quota, and set up authentication for Google Cloud services."],["Users must prepare a MIG for resize requests by configuring an instance template that stops VMs during host maintenance events and does not use reservations."],["To prepare the MIG for resize requests, set the MIG's update type to opportunistic, turn off repairs, delete the autoscaling configuration, and if using a regional MIG, set the target distribution shape to `ANY_SINGLE_ZONE`."],["A resize request involves specifying the number of VMs to add all at once and defining the duration these VMs will run, with a range between 1 hour and 7 days."]]],[]]
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4