• Migrating applications to a modern platform likeVMware vSphere Kubernetes Service (VKS)is rarely a “one-size-fits-all” operation • Whether you are moving from a generic Kubernetes provider (like OpenShift, EKS, or GKE), migrating from virtual machines, or repatriating cloud services, the strategy you choose depends heavily on your current automation maturity and workload requirements • In this post, we discuss the primary migration patterns:re-platforming (“lift and shift”)versusre-deploying (pipeline-driven) • The following guide can help you choose the right path for your organization • Strategy 1: The “Lift and Shift” (Re-platforming) Best for:Organizations with little to no automation or deployment pipelines If your team is hand-deploying applications or lacks mature GitOps practices, the most viable path is often a “backup and restore” approach using tools like Velero • How it works Backup source state: Velero queries the source Kubernetes API to grab all objects (deployments, secrets, config maps, services) and bundles them into an S3-compatible storage bucket

Article Summaries:

  • Migrating applications to a modern platform like VMware vSphere Kubernetes Service (VKS) is rarely a “one-size-fits-all” operation. Whether you are moving from a generic Kubernetes provider (like OpenShift, EKS, or GKE), migrating from virtual machines, or repatriating cloud services, the strategy you choose depends heavily on your current automation maturity and workload requirements. In this post, we discuss the primary migration patterns: re-platforming (“lift and shift”) versus re-deploying (pipeline-driven). The following guide can help you choose the right path for your organization. Str

Sources: