Migrating containers to the ru-central1-d availability zone
Written by
Updated at April 26, 2024
Note
We are gradually deprecating the ru-central1-c
availability zone. For more information about development plans for availability zones and migration options, see this Yandex Cloud blog post.
If you created subnets for Cloud Functions functions, Serverless Containers containers, or API Gateway API gateways and submitted a request to use them to technical support, follow the steps below to migrate resources from the ru-central1-c
availability zone:
-
In the cloud network hosting the subnets, create a new subnet.
The requirements are as follows:
- The subnet must be in the
ru-central1-d
availability zone. - Make sure the subnet is the same for all functions, containers, and API gateways.
- It must not contain any resources except functions, containers, and API gateways.
- The subnet must be in the
-
Contact technical support
and provide them with the new subnet's ID.
The support team will migrate the resources to the specified subnet.