---
title: "POST /projects/{project}/zones/{zone}/instanceGroupManagers/{instanceGroupManager}/abandonInstances"
method: POST
path: "/projects/{project}/zones/{zone}/instanceGroupManagers/{instanceGroupManager}/abandonInstances"
tags: ["instanceGroupManagers"]
---

# POST /projects/{project}/zones/{zone}/instanceGroupManagers/{instanceGroupManager}/abandonInstances

`POST /projects/{project}/zones/{zone}/instanceGroupManagers/{instanceGroupManager}/abandonInstances`

Flags the specified instances to be removed from the
managed instance group. Abandoning an instance does not delete the
instance, but it does remove the instance from any target pools that are
applied by the managed instance group. This method reduces thetargetSize of the managed instance group by the
number of instances that you abandon. This operation is marked asDONE when the action is scheduled even if the instances have
not yet been removed from the group. You must separately verify the
status of the abandoning action with thelistmanagedinstances
method.

If the group is part of a backend
service that has enabled
connection draining, it can take up to 60 seconds after the connection
draining duration has elapsed before the VM instance is removed or deleted.

You can specify a maximum of 1000 instances with this method per request.

## Path parameters

- `project` string, required
- `zone` string, required
- `instanceGroupManager` string, required

## Query parameters

- `requestId` string

## Request body

- InstanceGroupManagersAbandonInstancesRequest
  - `instances` string[] — The URLs of one or more instances to abandon. This can be a full URL or a partial URL, such as zones/[ZONE]/instances/[INSTANCE_NAME].

## Response `200`

Successful response

---

[API](https://skmtc.net/google/apis/compute.md) · [All operations](https://skmtc.net/google/apis/compute/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/google/compute/revisions/6120ed8969d4/schema)