Cluster migration between availability zones
All clusters that used the availability zone GZ1 must be moved to another availability zone (for example PA2), as GZ1 is being decommissioned.
Cluster migration between availability zones takes place in three steps:
-
Determine whether the migration will affect the workload of your clusters. To do this, check whether the availability zone is specified:
-
in the pod's scheduling rules:
- in the
nodeAffinity,topologySpreadConstraints, ornodeSelectorparameters; - in the labels
topology.kubernetes.io/zone,failure-domain.beta.kubernetes.io/zone, andtopology.cinder.csi.openstack.org/zone.
- in the
-
in the storage class (
StorageClass) for StatefulSet pods.
If the availability zone is not specified, migrating to a different availability zone will not affect your workload in any way, and no additional migration actions will be required from you.
-
-
If the cluster workload depends on the availability zone, migrate it yourself either before the VK Cloud starts migrating the cluster resources, or after.
During self-migration, the workload will have to be stopped.
-
Wait until the VK Cloud employees migrate the cluster resources:
- master nodes,
- worker node groups,
- VMs,
- disks,
- load balancers.
The cluster will remain available during the works; the migration is performed as a live migration. The VK Cloud employees will notify you by email about the start and timeline of the works.