Migrating to Managed Service for Kubernetes

Managed Service for Kubernetes enables you to migrate your Kubernetes workloads from any environment, without vendor or infrastructure lock-in. The following scenarios are supported:

• Migration from other cloud providers to Yandex Cloud.
• Migration from on-premises infrastructure to Yandex Cloud.
• Hybrid setups with partial workload migration to Yandex Cloud using external nodes or BareMetal servers.

Migration overviewMigration overview

1. Inventory: Audit your workloads, assess API compatibility, and define network requirements.
2. Network connectivity (for on-premises): Establish a connection between the source infrastructure and Yandex Cloud.
3. Yandex Cloud infrastructure: Create VPCs, security groups, IAM resources, a Managed Service for Kubernetes cluster, and node groups.
4. Image migration: Copy your container images to Yandex Container Registry.
5. Stateful workload migration: Migrate your data using Yandex Data Transfer or Velero.
6. Stateless workload migration: Export, adjust, and apply your manifests.
7. Load balancers and DNS: Configure Gwin, Network Load Balancer, and DNS switching.
8. Final steps: Test your new setup, clean up the source infrastructure, and archive backups.

Required time and effortRequired time and effort

The time a migration may take depends on the size of your data, number of services to migrate, and your specific migration path. Here are the general estimates:

These estimates assume a team of two or three engineers. Timelines may increase for complex stateful workloads, non-standard network requirements, or regulatory constraints.

Required toolsRequired tools