Migrating a ru-central1-c instance to a different availability zone

VMs with Managed Service for GitLab instances reside in Yandex Cloud availability zones. If an instance is located in ru-central1-c, you can migrate it to a different zone. To do this:

1. If you do not have a subnet in the target availability zone, create one.

2. If the instance's security group is set up for a subnet in the source availability zone, recongifure the group for the new subnet. To do so, replace the source subnet CIDR with the new subnet CIDR in the security group rules.

3. Change the instance's availability zone:

   Management console

   1. In the management console, go to the folder page and select Managed Service for GitLab.

   2. Click the instance name and select the Migration tab.

   3. If unable to use the migration functionality, request access to it.

      When your request is approved, you will be notified by email. To continue, reload the page in your browser.

   4. Specify the target availability zone and subnet.

   5. Click Move instance.

      The instance will start to upgrade. Wait for the instance to change its status back to Running. This will take a few minutes for a small instance or at least 30 minutes if the instance is over 200 GB in size. After a few more minutes, the GitLab instance will start.

   6. To test the instance's performance, select the Overview tab and click the link in the Domain field.

   7. On the Migration tab:

      • If the instance works properly, click Complete migration.
      • If the instance is inoperable, click Cancel migration to move it back to the initial availability zone, or contact technical support.