[Yandex Cloud documentation](../../index.md) > [Tutorials](../index.md) > [Basic infrastructure](../infrastructure/index.md) > Fault tolerance and scaling > Updating an instance group under load # Updating an instance group under load In this step-by-step tutorial, you will configure an [instance group](../../compute/concepts/instance-groups/index.md) and check how it operates when updating the configuration. Proceed as follows: 1. [Get your cloud ready](#before-you-begin). 1. [Set up your environment](#create-environment). 1. [Create an instance group using a Container Optimized Image](#create-vm-group). 1. [Start VM load testing](#start-load-testing). 1. [Update the instance group under load](#update-spec). 1. [Stop load testing and get the results](#end-load-testing). If you no longer need the resources you created, [delete them](#clear-out). ## Get your cloud ready {#before-you-begin} 1. If you do not have the Yandex Cloud CLI yet, [install it](../../cli/quickstart.md#install). 1. To make sure the scripts from the step-by-step guide run correctly, download and install [jq](https://stedolan.github.io/jq/download/). 1. To check autoscaling, install [wrk](https://github.com/wg/wrk). ### Required paid resources {#paid-resources} The support cost for a Yandex Cloud instance group includes fees for: * [Disks](../../compute/concepts/disk.md) and continuously running [VMs](../../compute/concepts/vm.md) as per [Yandex Compute Cloud pricing](../../compute/pricing.md). * Using a dynamic or static [public IP address](../../vpc/concepts/address.md) as per [Yandex Virtual Private Cloud pricing](../../vpc/pricing.md). ## Set up your environment {#create-environment} 1. Create a [service account](../../iam/concepts/users/service-accounts.md) named `for-load`. To create, update, and delete VM instances in your group, as well as integrate the group with Network Load Balancer, assign the [compute.editor](../../compute/security/index.md#compute-editor) and [load-balancer.editor](../../network-load-balancer/security/index.md#load-balancer-editor) roles to the service account: {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), select the [folder](../../resource-manager/concepts/resources-hierarchy.md#folder) where you want to create your service account. 1. Navigate to **Identity and Access Management**. 1. Click **Create service account**. 1. In the **Name** field, specify `for-load`. 1. Click ![](../../_assets/console-icons/plus.svg) **Add role**. To create, update, and delete VM instances in your group, as well as integrate the group with Network Load Balancer, assign the [compute.editor](../../compute/security/index.md#compute-editor) and [load-balancer.editor](../../network-load-balancer/security/index.md#load-balancer-editor) roles to the service account. 1. Click **Create**. - CLI {#cli} 1. Create a service account: The folder used by default is the one specified when [creating](../../cli/operations/profile/profile-create.md) the CLI profile. To change the default folder, use the `yc config set folder-id ` command. You can also specify a different folder for any command using `--folder-name` or `--folder-id`. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions. ```bash yc iam service-account create --name for-load ``` Result: ```bash id: ajeab0cnib1p******** folder_id: b0g12ga82bcv******** created_at: "2021-02-09T17:31:32.561702Z" name: for-load ``` 1. Assign the `compute.editor` role to the service account: ```bash yc resource-manager folder add-access-binding \ --role compute.editor \ --subject serviceAccount: ``` 1. Assign the `load-balancer.editor` role to the service account: ```bash yc resource-manager folder add-access-binding \ --role load-balancer.editor \ --subject serviceAccount: ``` - API {#api} 1. Create a service account named `for-load`: Use the [create](../../iam/api-ref/ServiceAccount/create.md) REST API method for the [ServiceAccount](../../iam/api-ref/ServiceAccount/index.md) resource or the [ServiceAccountService/Create](../../iam/api-ref/grpc/ServiceAccount/create.md) gRPC API call. 1. To create, update, and delete VM instances in your group, as well as integrate the group with Network Load Balancer, assign the [compute.editor](../../compute/security/index.md#compute-editor) and [load-balancer.editor](../../network-load-balancer/security/index.md#load-balancer-editor) roles to the service account: Use the [setAccessBindings](../../resource-manager/api-ref/Folder/setAccessBindings.md) REST API method for the [Folder](../../resource-manager/api-ref/Folder/index.md) resource or the [FolderService/SetAccessBindings](../../resource-manager/api-ref/grpc/Folder/setAccessBindings.md) gRPC API call. {% endlist %} 1. Create a [network](../../vpc/concepts/network.md#network) named `yc-auto-network` and [subnets](../../vpc/concepts/network.md#subnet) in two [availability zones](../../overview/concepts/geo-scope.md): {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), select the folder where you want to create your network. 1. Navigate to **Virtual Private Cloud**. 1. Click **Create network**. 1. In the **Name** field, specify `yc-auto-network`. 1. Select **Create subnets**. 1. Click **Create network**. - CLI {#cli} 1. Create a network: ```bash yc vpc network create --name yc-auto-network ``` Result: ```bash id: enpabce123hd******** folder_id: b0g12ga82bcv******** created_at: "2021-02-09T17:33:32.561702Z" name: yc-auto-network ``` 1. Create a subnet in the `ru-central1-d` availability zone: ```bash yc vpc subnet create --network-id enpabce123hd******** --range 192.168.1.0/24 --zone ru-central1-d ``` Result: ```bash id: e1lnabc23r1c******** folder_id: b0g12ga82bcv******** created_at: "2021-02-09T17:34:32.561702Z" network_id: enpabce123hd******** zone_id: ru-central1-d v4_cidr_blocks: - 192.168.1.0/24 ``` 1. Create a subnet in the `ru-central1-b` availability zone: ```bash yc vpc subnet create --network-id enpabce123hd******** --range 192.168.2.0/24 --zone ru-central1-b ``` Result: ```bash id: b1csa2b3clid******** folder_id: b0g12ga82bcv******** created_at: "2021-02-09T17:35:32.561702Z" network_id: enpabce123hd******** zone_id: ru-central1-b v4_cidr_blocks: - 192.168.2.0/24 ``` - API {#api} 1. Create a network: Use the [create](../../vpc/api-ref/Network/create.md) REST API method for the [Network](../../vpc/api-ref/Network/index.md) resource or the [NetworkService/Create](../../vpc/api-ref/grpc/Network/create.md) gRPC API call. 1. Create subnets in the `ru-central1-d` and `ru-central1-b` availability zones: Use the [create](../../vpc/api-ref/Subnet/create.md) REST API method for the [Subnet](../../vpc/api-ref/Subnet/index.md) resource or the [SubnetService/Create](../../vpc/api-ref/grpc/Subnet/create.md) gRPC API call. {% endlist %} ## Create an instance group using a Container Optimized Image {#create-vm-group} 1. In this tutorial, you will be creating all instance groups from a [Container Optimized Image](../../cos/concepts/index.md). Each VM will have a Docker container running a web server that emulates the load. {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), select the folder where you want to create an instance group. 1. Navigate to **Compute Cloud**. 1. In the left-hand panel, select ![](../../_assets/console-icons/layers-3-diagonal.svg) **Instance groups**. 1. Click **Create group of virtual machines**. 1. Under **Basic parameters**: * In the **Name** field, specify `group-for-load`. * Select `for-load` for **Service account**. 1. Under **Allocation**, select `ru-central1-d` and `ru-central1-b` in the **Availability zone** field. 1. Under **Instance template**, click **Define** and do the following in the window that opens: * Under **Boot disk image**, select the **Container Solution** tab. * Click **Configure**. * In the **Docker container settings** window: * In the **Name** field, specify `nginx`. * In the **Docker image** field, click **Enter link** and enter `cr.yandex/yc/demo/autoscaling-example-app:v1`. * Click **Apply**. * Under **Disks and file storages**: * For the boot disk, specify `30 GB` for **Size**. * Under **Network settings**: * In the **Network** field, select `for-load`. * Under **Access**: * In the **Service account** field, select `for-load`. * In the **Login** field, enter the name of the user to create on the VM. * In the **SSH key** field, paste the contents of the public key file. * Click **Save**. 1. Under **Changes during creation and updates**: * In the **Reduce below target value** field, enter `4`. 1. Under **Scaling**: * In the **Type** field, select `Fixed`. * Set the **Size** to `6`. 1. Under **Integration with Network Load Balancer**: * Enable **Create target group**. * In the **Name of the target group** field, specify `load-generator`. 1. Click **Create**. - CLI {#cli} 1. Get the ID of the latest version of the [public](../../compute/operations/images-with-pre-installed-software/get-list.md) Container Optimized Image. A Container Optimized Image in [Yandex Container Registry](../../container-registry/index.md) may get updates and modifications that come with new releases. Such modifications will not automatically update the VM image to the latest version. To create an instance group with the latest Container Optimized Image version, manually check whether it is available: ```bash yc compute image get-latest-from-family container-optimized-image --folder-id standard-images ``` Result: ```bash id: fd8iv792kira******** folder_id: standard-images created_at: "2021-01-29T13:30:22Z" ... status: READY os: type: LINUX ``` 1. Save the specification of the instance group with a network load balancer to the `specification.yaml` file: ```yaml name: group-for-load # VM group name, unique within the folder. service_account_id: ajeab0cnib1p******** # Service account ID. allocation_policy: # VM allocation policy for the group. zones: - zone_id: ru-central1-d - zone_id: ru-central1-b instance_template: service_account_id: ajeab0cnib1p******** # ID of the service account to access private Docker images. platform_id: standard-v1 # Platform ID. resources_spec: memory: 2G # Amount of memory (RAM). cores: 2 # Number of processor cores (vCPUs). boot_disk_spec: mode: READ_WRITE # Disk access mode (read and write). disk_spec: image_id: type_id: network-ssd # Disk type. size: 30G # Disk size. network_interface_specs: - network_id: enplhg4nncc7******** # Network ID. subnet_ids: - e1lnabc23r1c******** # Subnet ID. - b1csa2b3clid******** primary_v4_address_spec: { one_to_one_nat_spec: { ip_version: IPV4 # IPv4 specification for public access to the VM. } } metadata: # Values to send to the VM metadata. docker-container-declaration: |- # Key in the VM metadata that is used with the Docker Container specification. spec: containers: - image: cr.yandex/yc/demo/autoscaling-example-app:v1 name: nginx securityContext: privileged: false restartPolicy: Always tty: false stdin: false ssh-keys: | # Parameter for providing an SSH key to the VM. yc-user:ssh-ed25519 ABC...d01 user@desktop.ru # Username for connecting to the VM. deploy_policy: # VM deployment policy for the group. max_unavailable: 4 scale_policy: # Instance scaling policy for the group. fixed_scale: size: 6 load_balancer_spec: # Network load balancer. target_group_spec: name: load-generator ``` {% note info %} You can provide an SSH key in the [VM metadata](../../compute/concepts/vm-metadata.md) using the `ssh-keys` parameter or in the `user-data` key. This tutorial uses the first option. {% endnote %} 1. Create an instance group named `group-for-load` using `specification.yaml`: ```bash yc compute instance-group create --file=specification.yaml ``` Result: ```bash done (2m18s) id: cl0kabcquk1g******** folder_id: b0g12ga82bcv******** ... service_account_id: ajeab0cnib1p******** status: ACTIVE application_load_balancer_state: {} ``` - API {#api} 1. Get the ID of the latest `container-optimized-image` version in the `standard-images` family: Use the [getLatestByFamily](../../compute/api-ref/Image/getLatestByFamily.md) REST API method for the [Image](../../compute/api-ref/Image/index.md) resource or the [ImageService/GetLatestByFamily](../../compute/api-ref/grpc/Image/getLatestByFamily.md) gRPC API call. 1. Create an instance group based on this spec: ```yaml name: group-for-load # VM group name, unique within the folder. service_account_id: ajeab0cnib1p******** # Service account ID. allocation_policy: # VM allocation policy for the group. zones: - zone_id: ru-central1-d - zone_id: ru-central1-b instance_template: service_account_id: ajeab0cnib1p******** # ID of the service account to access private Docker images. platform_id: standard-v1 # Platform ID. resources_spec: memory: 2G # Amount of memory (RAM). cores: 2 # Number of processor cores (vCPUs). boot_disk_spec: mode: READ_WRITE # Disk access mode (read and write). disk_spec: image_id: type_id: network-ssd # Disk type. size: 30G # Disk size. network_interface_specs: - network_id: enplhg4nncc7******** # Network ID. subnet_ids: - e1lnabc23r1c******** # Subnet ID. - b1csa2b3clid******** primary_v4_address_spec: { one_to_one_nat_spec: { ip_version: IPV4 # IPv4 specification for public access to the VM. } } metadata: # Values to send to the VM metadata. docker-container-declaration: |- # Key in the VM metadata that is used with the Docker Container specification. spec: containers: - image: cr.yandex/yc/demo/autoscaling-example-app:v1 name: nginx securityContext: privileged: false restartPolicy: Always tty: false stdin: false ssh-keys: | # Parameter for providing an SSH key to the VM. yc-user:ssh-ed25519 ABC...d01 user@desktop.ru # Username for connecting to the VM. deploy_policy: # VM deployment policy for the group. max_unavailable: 4 scale_policy: # Instance scaling policy for the group. fixed_scale: size: 6 load_balancer_spec: # Network load balancer. target_group_spec: name: load-generator ``` Use the [createFromYaml](../../compute/instancegroup/api-ref/InstanceGroup/createFromYaml.md) REST API method for the [InstanceGroup](../../compute/instancegroup/api-ref/InstanceGroup/index.md) resource or the [InstanceGroupService/CreateFromYaml](../../compute/instancegroup/api-ref/grpc/InstanceGroup/createFromYaml.md) gRPC API call. {% endlist %} 1. Check your instance group: {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), select the folder where you created the instance group. 1. Navigate to **Compute Cloud**. 1. In the left-hand panel, select ![](../../_assets/console-icons/layers-3-diagonal.svg) **Instance groups**. 1. Click `group-for-load`. - CLI {#cli} ```bash yc compute instance-group list-instances group-for-load ``` Result: ```bash +----------------------+---------------------------+-----------------+-------------+----------------------+----------------+ | INSTANCE ID | NAME | EXTERNAL IP | INTERNAL IP | STATUS | STATUS MESSAGE | +----------------------+---------------------------+-----------------+-------------+----------------------+----------------+ ... | fhmab0cfsfd1******** | cl0kabcquk1g********-oxig | 178.154.226.108 | 10.130.0.8 | RUNNING_ACTUAL [49m] | | | epdabchpdef0******** | cl0kabcquk1g********-aqyg | 130.193.40.55 | 10.129.0.20 | RUNNING_ACTUAL [43m] | | +----------------------+---------------------------+-----------------+-------------+----------------------+----------------+ ``` - API {#api} To view a list of the instance groups you created, use the [list](../../compute/instancegroup/api-ref/InstanceGroup/list.md) REST API method for the [InstanceGroup](../../compute/instancegroup/api-ref/InstanceGroup/index.md) resource or the [InstanceGroupService/List](../../compute/instancegroup/api-ref/grpc/InstanceGroup/list.md) gRPC API call. {% endlist %} ### Add a network load balancer to the instance group {#enable-balancer} 1. Create a network load balancer named `load-generator` and add it to the instance group you created: {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), select the folder where you want to create a load balancer. 1. Navigate to **Network Load Balancer**. 1. Click **Create a network load balancer**. 1. In the **Name** field, specify `load-generator`. 1. In the **Public address** field, select `Auto`. 1. Under **Listeners**, click **Add listener**. 1. In the window that opens: * In the **Name** field, specify `http`. * In the **Port** field, enter `80`. The load balancer will listen for inbound traffic on this port. * In the **Target port** field, enter `80`. The load balancer will redirect traffic to this port. * Click **Add**. 1. Under **Target groups**, click **Add target group**. 1. In the **Target group** list, select `load-generator`. 1. Under **Health check**, click **Configure**: * In the window that opens, specify `/hello` for **Path**. The load balancer will use this path to send health check requests to the target group VMs. * Click **Apply**. 1. Click **Create**. - CLI {#cli} 1. Get the ID of the `load-generator` target group: ```bash yc load-balancer target-group get load-generator | grep "^id" ``` Result: ```bash id: enpsa475ej51******** ``` 1. Create a network load balancer: ```bash yc load-balancer network-load-balancer create \ --name load-generator \ --listener external-ip-version=ipv4,name=http,port=80,protocol=tcp,target-port=80 \ --target-group healthcheck-http-port=80,healthcheck-http-path=/hello,target-group-id= ``` Result: ```bash done (14s) id: b0ruab1ccvpd******** folder_id: b1csa2b3clid******** ... healthy_threshold: "2" http_options: port: "80" path: /hello ``` - API {#api} 1. Create a load balancer using the [create](../../network-load-balancer/api-ref/NetworkLoadBalancer/create.md) REST API method for the [NetworkLoadBalancer](../../network-load-balancer/api-ref/NetworkLoadBalancer/index.md) resource or the [NetworkLoadBalancerService/Create](../../network-load-balancer/api-ref/grpc/NetworkLoadBalancer/create.md) gRPC API call. 1. Add a listener to the load balancer using the [addListener](../../network-load-balancer/api-ref/NetworkLoadBalancer/addListener.md) REST API method for the `NetworkLoadBalancer` resource or the [NetworkLoadBalancerService/AddListener](../../network-load-balancer/api-ref/grpc/NetworkLoadBalancer/addListener.md) gRPC API call. 1. Attach the target group to the load balancer using the [attachTargetGroup](../../network-load-balancer/api-ref/NetworkLoadBalancer/attachTargetGroup.md) REST API method for the `NetworkLoadBalancer` resource or the [NetworkLoadBalancerService/AttachTargetGroup](../../network-load-balancer/api-ref/grpc/NetworkLoadBalancer/attachTargetGroup.md) gRPC API call. 1. Add the load balancer to the instance group using the [addTargets](../../network-load-balancer/api-ref/TargetGroup/addTargets.md) REST API method for the [TargetGroup](../../network-load-balancer/api-ref/TargetGroup/index.md) resource or the [TargetGroupService/AddTargets](../../network-load-balancer/api-ref/grpc/TargetGroup/addTargets.md) gRPC API call. {% endlist %} 1. Check the `load-generator` network load balancer and make sure it is linked to the instance group: {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), select the folder where you created the load balancer. 1. Navigate to **Network Load Balancer**. 1. Click `load-generator`. - CLI {#cli} ```bash yc load-balancer network-load-balancer list ``` Result: ```bash +----------------------+----------------+-----------------+----------+----------------+------------------------+--------+ | ID | NAME | REGION ID | TYPE | LISTENER COUNT | ATTACHED TARGET GROUPS | STATUS | +----------------------+----------------+-----------------+----------+----------------+------------------------+--------+ | b0ruab1ccvpd******** | load-generator | ru-central1 | EXTERNAL | 1 | b0r1tabcphde******** | ACTIVE | +----------------------+----------------+-----------------+----------+----------------+------------------------+--------+ ``` - API {#api} Use the [list](../../network-load-balancer/api-ref/NetworkLoadBalancer/list.md) REST API method for the [NetworkLoadBalancer](../../network-load-balancer/api-ref/NetworkLoadBalancer/index.md) resource or the [NetworkLoadBalancerService/List](../../network-load-balancer/api-ref/grpc/NetworkLoadBalancer/list.md) gRPC API call. {% endlist %} ## Start VM load testing {#start-load-testing} 1. Get the IP address of the load balancer you created: {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), select the folder with your load balancer. 1. Navigate to **Network Load Balancer**. 1. Copy the **IP address** of the `load-generator` load balancer. - CLI {#cli} ```bash yc load-balancer network-load-balancer get load-generator | grep "address" ``` Result: ```bash address: 84.252.133.110 ``` - API {#api} Use the [get](../../network-load-balancer/api-ref/NetworkLoadBalancer/get.md) REST API method for the [NetworkLoadBalancer](../../network-load-balancer/api-ref/NetworkLoadBalancer/index.md) resource or the [NetworkLoadBalancerService/Get](../../network-load-balancer/api-ref/grpc/NetworkLoadBalancer/get.md) gRPC API call. {% endlist %} 1. Run this command to start generating load: ```bash wrk -t20 -c20 -d20m --timeout 20s http:///sleep ``` This will start `wrk` to send requests to the load balancer using 20 threads, with 20 connections each, for 20 minutes. The request timeout is 20 seconds. The load balancer will distribute the load it gets across the VM instances in the group. As soon as `wrk` launches, a message about the test start will appear on the screen: ```bash Running 20m test @ http://84.252.133.110/sleep 20 threads and 20 connections ``` Proceed to the next step without waiting for the command to complete. ## Update the instance group under load {#update-spec} {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), select the folder where you created the instance group. 1. Navigate to **Compute Cloud**. 1. In the left-hand panel, select ![](../../_assets/console-icons/layers-3-diagonal.svg) **Instance groups**. 1. Click `group-for-load`. 1. Click ![edit](../../_assets/console-icons/pencil.svg) **Edit**. 1. Under **Instance template**, click ![horizontal-ellipsis](../../_assets/console-icons/ellipsis.svg) and select **Edit**. * Under **Disks and file storages**, specify `35 GB` as the new disk size. * Click **Save**. 1. Click **Save**. 1. Under **Virtual machines**, you will see the disk size modifications for all VM instances in the group, one by one. - CLI {#cli} 1. In `specification.yaml`, enter the new disk size of 35 GB and save the file: ```yaml ... size: 35G ... ``` 1. Update the instance group: ```bash yc compute instance-group update --name=group-for-load --file=specification.yaml ``` Result: ```bash done (9m24s) id: cl10kktrjcn8******** folder_id: b1g7gvsi89m3******** ... name: load-generator service_account_id: ajehbk07uus3******** status: ACTIVE ``` - API {#api} 1. In the spec, enter the new disk size of 35 GB: ```yaml ... size: 35G ... ``` 1. To update the `load-generator` instance group based on the new spec, use the [updateFromYaml](../../compute/instancegroup/api-ref/InstanceGroup/updateFromYaml.md) REST API method for the [InstanceGroup](../../compute/instancegroup/api-ref/InstanceGroup/index.md) resource or the [InstanceGroupService/UpdateFromYaml](../../compute/instancegroup/api-ref/grpc/InstanceGroup/updateFromYaml.md) gRPC API call. {% endlist %} ## Stop load testing and get the results {#end-load-testing} Stop `wrk` by pressing **Ctrl** + **C**. Result: ```bash Thread Stats Avg Stdev Max +/- Stdev Latency 10.00s 1.70ms 10.01s 68.21% Req/Sec 0.00 0.00 0.00 100.00% 1148 requests in 17.47m, 211.89KB read Requests/sec: 1.09 Transfer/sec: 206.94B ``` If the result contains no error line, such as `Socket errors`, it means the system has processed all requests. ## How to delete the resources you created {#clear-out} To delete the created resources: {% list tabs group=instructions %} - Management console {#console} 1. Delete the load balancer: 1. In the [management console](https://console.yandex.cloud), select the folder where you created the load balancer. 1. Navigate to **Network Load Balancer**. 1. To the right of `load-generator`, click ![horizontal-ellipsis](../../_assets/console-icons/ellipsis.svg) and select **Delete**. 1. In the window that opens, click **Delete**. 1. Delete the instance group: 1. In the [management console](https://console.yandex.cloud), select the folder where you created the instance group. 1. Navigate to **Compute Cloud**. 1. In the left-hand panel, select ![](../../_assets/console-icons/layers-3-diagonal.svg) **Instance groups**. 1. To the right of `load-generator`, click ![horizontal-ellipsis](../../_assets/console-icons/ellipsis.svg) and select **Delete**. 1. In the window that opens, click **Delete**. 1. Delete the service account: 1. In the [management console](https://console.yandex.cloud), select the folder where you created the service account. 1. Navigate to **Identity and Access Management**. 1. In the left-hand panel, select ![FaceRobot](../../_assets/console-icons/face-robot.svg) **Service accounts**. 1. In the list that opens, click ![horizontal-ellipsis](../../_assets/console-icons/ellipsis.svg) next to `yc-auto-sa` and select **Delete**. 1. In the window that opens, click **Delete**. 1. Delete the network and the subnets: 1. In the [management console](https://console.yandex.cloud), select the folder where you created the network and the subnets. 1. Navigate to **Virtual Private Cloud**. 1. Select `yc-auto-network`. 1. Under **Subnets**: 1. To the right of `yc-auto-subnet-1`, click ![horizontal-ellipsis](../../_assets/console-icons/ellipsis.svg) and select **Delete**. 1. In the window that opens, click **Delete**. 1. Delete `yc-auto-subnet-2` as well. 1. In the top-right corner, click **Delete**. - CLI {#cli} Run these commands one by one: ```bash yc load-balancer network-load-balancer delete load-generator yc compute instance-group delete load-generator yc iam service-account delete yc-auto-sa yc vpc subnet delete yc-auto-subnet-1 yc vpc subnet delete yc-auto-subnet-2 yc vpc network delete yc-auto-network ``` - API {#api} 1. Delete the `load-generator` load balancer using the [delete](../../network-load-balancer/api-ref/NetworkLoadBalancer/delete.md) REST API method for the [NetworkLoadBalancer](../../network-load-balancer/api-ref/NetworkLoadBalancer/index.md) resource or the [NetworkLoadBalancerService/Delete](../../network-load-balancer/api-ref/grpc/NetworkLoadBalancer/delete.md) gRPC API call. 1. Delete the `load-generator` instance group using the [delete](../../compute/instancegroup/api-ref/InstanceGroup/delete.md) REST API method for the [InstanceGroup](../../compute/instancegroup/api-ref/InstanceGroup/index.md) resource or the [InstanceGroupService/Delete](../../compute/instancegroup/api-ref/grpc/InstanceGroup/delete.md) gRPC API call. 1. Delete the `yc-auto-sa` service account using the [delete](../../iam/api-ref/ServiceAccount/delete.md) REST API method for the [ServiceAccount](../../iam/api-ref/ServiceAccount/index.md) resource or the [ServiceAccountService/Delete](../../iam/api-ref/grpc/ServiceAccount/delete.md) gRPC API call. 1. Delete the `yc-auto-subnet-1` and `yc-auto-subnet-2` subnets using the [delete](../../vpc/api-ref/Subnet/delete.md) REST API method for the [Subnet](../../vpc/api-ref/Subnet/index.md) resource or the [SubnetService/Delete](../../vpc/api-ref/grpc/Subnet/delete.md) gRPC API call. 1. Delete the `yc-auto-network` network using the [delete](../../vpc/api-ref/Network/delete.md) REST API method for the [Network](../../vpc/api-ref/Network/index.md) resource or the [NetworkService/Delete](../../vpc/api-ref/grpc/Network/delete.md) gRPC API call. {% endlist %}