Unified Kubernetes VM Lifecycle Management

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current container orchestration systems like Kubernetes lack integration with virtual machines (VMs), limiting the ability to manage and deploy applications uniformly across both containerized and non-containerized workloads within a single paradigm.

Innovation Solution

A virtualized computing system is introduced, featuring a host cluster with a virtualization layer supporting both pod VMs and native VMs, integrated with a Kubernetes orchestration control plane that includes pod VM controllers and native VM controllers to manage the lifecycles of these VMs, enabling unified management and deployment of applications across both containerized and non-containerized environments.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If container orchestration systems like Kubernetes are used to manage containerized applications, then automation and scalability are improved, but the ability to manage non-containerized workloads (VMs) within the same system deteriorates

Engineering Contradiction:

Improveautomation of application deploymentVSAvoidability to manage both containerized and non-containerized workloads

Core Design Contradiction:

Extent of automationVSAdaptability or versatility

Solution Approach 1:

The patent extends Kubernetes orchestration capabilities to manage both pod VMs (containerized workloads) and native VMs (non-containerized workloads) through a unified control plane. The virtualization layer integrates with Kubernetes to provide universal management of diverse workload types, allowing a single system to handle multiple workload paradigms without requiring separate management tools.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Reliability

If separate management systems are used for VMs and containers, then specialized management capabilities are maintained, but system complexity and operational overhead increase

Engineering Contradiction:

Improvespecialized management capabilitiesVSAvoidnumber of management systems

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges VM management and container orchestration into a single integrated system. Kubernetes is extended to work with the virtualization layer, combining previously separate management functions into one unified platform that manages both native VMs and pod VMs through common control plane components.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The unified control plane provides multi-functional capabilities to manage different workload types (containers and VMs) through a single system, reducing the number of separate management tools while maintaining specialized management capabilities for each workload type.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If VMs are integrated into Kubernetes, then unified management paradigm is achieved, but integration complexity and system architecture complexity increase

Engineering Contradiction:

Improveunified management paradigmVSAvoidintegration architecture

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a virtualization layer as an intermediary between the physical hardware and Kubernetes orchestration. This intermediary layer abstracts VM management operations, allowing Kubernetes to manage both pod VMs and native VMs through standardized interfaces without direct complex interactions with underlying virtualization infrastructure.

Inventive Principle:

Principle #24Intermediary (Mediator)

4Productivity

If a unified orchestration system manages both pod VMs and native VMs, then operational efficiency is improved, but controller complexity increases

Engineering Contradiction:

Improveoperational efficiencyVSAvoidcontroller architecture

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the control plane into specialized controllers: a pod VM controller for managing containerized workloads and a native VM controller for managing non-containerized workloads. Each controller handles specific workload types with optimized logic, while both report to the unified Kubernetes control plane, enabling efficient management without requiring a single monolithic controller.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS20230342168A1Declarative VM management for a container orchestrator in a virtualized computing system

Publication Date: 2023.10.26 VMWARE INC

AI summary

An example virtualized computing system includes a host cluster having a virtualization layer executing on hardware platforms of hosts, the virtualization layer supporting execution of virtual machines (VMs), the VMs including pod VMs and native VMs, the pod VMs including container engines supporting execution of containers in the pod VMs, the native VMs including applications executing on guest operating systems; and an orchestration control plane integrated with the virtualization layer, the orchestration control plane including a master server having a pod VM controller to manage lifecycles of the pod VMs and a native VM controller to manage lifecycles of the native VMs.