---
title: "Migration to Managed Kubernetes FAQ"
sidebar_label: "Migration to Managed Kubernetes FAQ"
sidebar_position: 99
description: "Frequently asked questions about migration to Managed Kubernetes"
---
import Formbricks from '@theme/MDXComponents/Formbricks'
import MoreVerticalIcon from '@selectel/docux/icons/more-vertical';
import CopyIcon from '@selectel/docux/icons/copy';
# Migration to Managed Kubernetes FAQ
## How to migrate your Kubernetes cluster to Selectel? \{#how-to-migrate-kubernetes-cluster}
Use the instructions:
* [Migrate to Managed Kubernetes using Velero](/migrations/migrate-to-managed-kubernetes/migrate-to-managed-kubernetes-velero.mdx);
* [Migrate volume data between Kubernetes clusters](/migrations/migrate-to-managed-kubernetes/migrate-kubernetes-volumes-data-between-clusters-with-k8up.mdx).
## Can I create a fault-tolerant cluster? \{#how-to-create-fault-tolerant-cluster}
Yes, when creating a cluster, you can select the Fault-Tolerant or Multi-Zone Fault-Tolerant cluster type.
We recommend creating Multi-Zone Fault-Tolerant clusters because in such clusters master nodes are located in different segments of a [multi-zone pool](/infrastructure/locations.mdx#multi-az-pool) — the nodes will be hosted in different data centers that are geographically remote from each other. A single point of failure for a multi-zone pool is failures across all data centers where cluster nodes are hosted.
For more information, see the [Cluster types](/managed-kubernetes/about/about-managed-kubernetes.mdx#cluster-types) subsection of the [Managed Kubernetes product overview](/managed-kubernetes/about/about-managed-kubernetes.mdx) guide.
## What to do if an error occurs when creating or modifying the configuration of a Managed Kubernetes cluster or node group? \{#actions-if-cluster-in-error}
Errors when creating or modifying the configuration of a Managed Kubernetes cluster or node groups can occur for various reasons, including insufficient resources in the location.
We recommend following these steps:
1. Check up-to-date information about Managed Kubernetes operation and resource availability in locations in the [Control Panel](https://my.selectel.ru/mks/) or on the [status page](https://selectel.live/).
2. If there is no information about an incident or resource unavailability, retry creating or modifying the cluster or node group configuration. Try changing the configuration and replacing local disks with network drives.
3. If there is information about resource unavailability, try creating a cluster in a different location.
4. If the previous steps did not help and you could not determine the cause on your own, [submit a ticket](https://my.selectel.ru/tickets/create/). In the ticket, specify:
* Managed Kubernetes cluster UUID. You can copy it in the [Control Panel](https://my.selectel.ru/mks/): in the top menu, click **Products** → **Managed Kubernetes** → cluster page → copy the UUID under the cluster name, next to the region and pool.;
* Project ID. You can copy it in the [Control Panel](https://my.selectel.ru/): in the top menu, click **IAM** → **Projects** → in the project row, in the **ID** column, click ;
* [pool](/infrastructure/locations.mdx#pool) where the cluster was created.
## How to delete a Managed Kubernetes cluster stuck in ERROR or PENDING_CREATE status if deletion via the Control Panel or API does not work? \{#delete-cluster-in-error}
If you cannot delete the Managed Kubernetes cluster via the Control Panel or API, [submit a ticket](https://my.selectel.ru/tickets/create/) and specify in it:
* Managed Kubernetes cluster UUID. You can copy it in the [Control Panel](https://my.selectel.ru/mks/): in the top menu, click **Products** → **Managed Kubernetes** → cluster page → copy the UUID under the cluster name, next to the region and pool.;
* Project ID. You can copy it in the [Control Panel](https://my.selectel.ru/): in the top menu, click **IAM** → **Projects** → in the project row, in the **ID** column, click ;
* [pool](/infrastructure/locations.mdx#pool) where the cluster was created.
## How to increase project quotas and limits? \{#quotas-and-limits}
Each project has quotas and limits configured:
* limits — the maximum number of resources that can be created in a project. Limits are set automatically when a project is created and may vary by [pools and pool segments](/infrastructure/locations.mdx#pool);
* quotas — constraints within limits used to control costs. When creating a project, quotas equal to the limits are allocated for each resource. When the resource count reaches the quota value, you will not be able to create new resources.
If there are not enough quotas to create resources, you can [change them](/access-control/projects/quotas.mdx#change-quotas) yourself. The quota value cannot exceed the project limit.
If creating resources requires more quotas than defined by the project limit, increase the limits. To do this, [submit a ticket](https://my.selectel.ru/tickets/create/) and specify in it:
* Project ID. You can copy it in the [Control Panel](https://my.selectel.ru/): in the top menu, click **IAM** → **Projects** → in the project row, in the **ID** column, click ;
* [pool](/infrastructure/locations.mdx#pool) where the limit needs to be increased;
* new limit value.
After a Selectel specialist increases the limit, [change the quotas](/access-control/projects/quotas.mdx#change-quotas) yourself in the Control Panel.
## Are there availability guarantees for a Managed Kubernetes cluster? \{#cluster-availability-guarantees}
Selectel guarantees the availability of Managed Kubernetes clusters only for Fault-Tolerant and Multi-Zone Fault-Tolerant types. Their guaranteed availability is 99.98%. For more information, see the document [Terms of Use for Individual Services: Kubernetes Cluster](https://files.selectel.ru/docs/ru/conditions-kubernetes-cluster.pdf) .
## How is a Managed Kubernetes cluster backed up? \{#how-does-backup-work}
In a Managed Kubernetes cluster, you can use persistent volume snapshots ([VolumeSnapshots](https://kubernetes.io/docs/concepts/storage/volume-snapshots/#volumesnapshots)) to back up data — point-in-time copies of persistent volume (PersistentVolume) content. You can [create a snapshot](/managed-kubernetes/volumes/volume-snapshots.mdx#create-snapshot) and then [restore a persistent volume from it](/managed-kubernetes/volumes/volume-snapshots.mdx#restore-persistent-volume-from-snapshot).
Snapshots can also be used to transfer data to another resource without the need to create a new disk.
## How to work with Managed Kubernetes after migration? \{#how-to-work-with-managed-kubernetes}
For more information about how Managed Kubernetes works, its versions, and limitations, see the [Managed Kubernetes product overview](/managed-kubernetes/about/about-managed-kubernetes.mdx) guide. Product guides are available in the [Managed Kubernetes](/managed-kubernetes/) section.
We also recommend taking the course on working with Managed Kubernetes [Product Dive: Managed Kubernetes](https://stack.selectel.ru/courses/cmsx2bgxw001k01iujqnyybtj) on the Selectel.Stack learning platform.