Navigating the Challenges of Cross-Cluster Migration of Kubernetes Workloads with CloudCasa
Cross-cluster migration of Kubernetes workloads continues to be challenging since workloads are isolated from each other by design. There are several reasons why you may want to separate your workloads, whether it is to reduce complexity or to have the cluster closer to the user base. However, this can be complex as Kubernetes has many components.
In this video, Kamlesh Lad, VP of Engineering & Chief Architect at CloudCasa by Catalogic, sits down with Swapnil Bhartiya to discuss the different scenarios where developers may want cross-cluster migration of Kubernetes workloads and the associated challenges. He also takes a deep dive into the available tools and how CloudCasa is helping simplify cross-cluster migration of Kubernetes workloads for developers.
Key highlights from this video interview are:
- There are several reasons why enterprise Kubernetes deployments have so many clusters. There are also different reasons for why developers may want to separate them. Lad goes into detail about the complexities of dealing with lots of clusters and the different scenarios why you may want to separate them.
- Even if you have on-prem, developers may want to have some clusters on-prem and some in the cloud. Alternatively, they may want clusters with different cloud vendors, or to segregate the clusters by different accounts in a single cloud. Lad describes the different infrastructures where developers may want to separate clusters.
- Lad goes into some of the common use cases he sees in production for data migration across clusters, from wanting to move workloads on a cluster to new storage, to cloning production workloads to the development and QA environments.
- Kubernetes has so many different components, but there are several that you cannot migrate the workload without moving them, such as the metadata and persistent volumes. However, Lad explains which components need to be kept in order to migrate the workload.
- One of the challenges of moving or duplicating workloads across different clusters is that there is not any communication between them, since the storage is not shared. Taking a backup of the persistent volume or the etcd data in a way so it can be moved to a different cluster is challenging. Lad discusses how you might want to navigate these difficulties using Kubernetes backup.
- There are several open source and proprietary tools to help developers migrate workloads including by doing Kuberetes backups.Lad goes into detail about the available tools.
- Lad goes into depth about how CloudCasa is helping to make this easier for developers. He explains their fully managed SaaS service, and its features and benefits.
- Lad gives Swapnil a demonstration of how CloudCasa helps with migrations, taking him through the workflow of migrating a cluster from one AWS account to another AWS account.
Give CloudCasa a try and sign up for our Free Plan (no credit card necessary).
Top 10 Reasons for Using CloudCasa
Immediately benefit from a powerful and easy to use Kubernetes backup service that does all the hard work for you to backup your multi-cluster applications and provide granular or cluster-level recovery including cross-account, cross-cluster, and cross-cloud recovery.
CloudCasa is so easy to use that even developers won’t mind managing backups. It comes with a generous free service plan (no credit card required) and it is a great alternative to using Velero or Kasten.
Here are the Top 10 reasons to use CloudCasa for Kubernetes backup, migration and disaster recovery, vs. these options:
- Do-it-yourself (DIY) products, whether open source like Velero or a product that you have to license, install and maintain like Kasten or Trilio
- Retrofitted enterprise or cloud backup products with container support, that still have all their baggage from the past (you know who they are)
- Cloud vendor or any VM backup that is not Kubernetes aware, or is single cloud only
- Container storage solutions with replication, or that come bundled with a single purpose backup application like PX-backup
- Solutions that don’t offer a free service plan or that charge by the cluster or by worker nodes