Kubernetes Workload Migration Across Multi-Cloud Clusters
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In a multi-cloud environment, Kubernetes clusters face resource exhaustion issues, making it impossible to scale out, and there is no method to migrate workloads while considering their execution state, leading to potential service interruptions.
Innovation Solution
A method and system that select and migrate workloads from one cluster to another based on a predetermined policy and workload intent, using an application scheduler, migration controller, and placement controller, ensuring resource availability without service disruption by updating IP addresses and using Istio ingress gateways.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If workload distribution is attempted in a multi-cloud environment, then resource utilization is improved, but service interruption occurs during migration
Solution Approach 1:
The patent applies preliminary action by creating a placeholder pod in the destination cluster before migrating the actual workload. This placeholder is configured with the same specifications as the original pod, and traffic routing is updated to point to the placeholder first. Once the placeholder is in place, the actual workload pod is migrated and replaced, ensuring continuous service availability throughout the migration process without interruption.
2Productivity
If cluster scale-out is performed when resources are exhausted, then workload capacity is increased, but node scaling becomes impossible in certain cloud environments
Solution Approach 1:
The patent applies dimensionality change by transitioning from horizontal scaling (adding more nodes to the same cluster) to multi-cluster distribution. When a cluster reaches resource exhaustion and node scaling becomes impossible in a particular cloud environment, the system migrates workloads to other available clusters in different cloud environments, effectively adding the dimension of multi-cloud resource allocation to solve the scaling limitation.
3Speed
If workload migration is performed without considering execution state, then migration speed is increased, but service disruption occurs
Solution Approach 1:
The patent applies preliminary action by first creating a placeholder pod in the destination cluster before migrating the actual workload. This placeholder is configured with the same specifications as the original pod, and traffic routing is updated to point to the placeholder first. Once the placeholder is in place, the actual workload pod is migrated and replaced, ensuring continuous service availability throughout the migration process without interruption.
Data Source
AI summary
A method for managing Kubernetes cluster resources in a multi-cloud environment includes: (a) selecting, when a workload which is impossible to distribute due to lack of resources is detected in a logical cloud including a plurality of clusters which are present in multiple clouds, one or more first workloads to be migrated from a first cluster to another cluster by referring to a predetermined policy, and a workload intent set for workloads executed in the logical cloud; (b) selecting a second cluster to which the one or more first workloads are to be migrated; (c) migrating the one or more first workloads to the second cluster, and deleting the one or more first workloads from the first cluster; and (d) distributing the workload which is impossible to distribute to the first cluster.