Guest Cluster Pod Deployment Through a Supervisor Kubernetes Layer

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing Kubernetes systems require expertise in both virtualized infrastructure management and application development, creating a gap in knowledge between virtualization administrators and application developers, and there is a need for a system that logically separates these management layers.

Innovation Solution

A virtualized computing system with a host cluster and guest cluster architecture, where the host cluster includes a supervisor cluster integrated with a virtualization layer and orchestration control plane, enabling the deployment of pods through a guest master server that manages pod VMs and first VMs, allowing development teams to deploy applications within resource-constrained supervisor namespaces.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If Kubernetes systems are implemented using traditional virtualized infrastructure management, then infrastructure management capabilities are provided, but the system complexity increases and requires expertise that application developers and virtualization administrators do not possess

Engineering Contradiction:
Improveinfrastructure management capabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system divides the Kubernetes management functionality into two distinct segments: a host cluster for infrastructure management and guest clusters for application deployment. This segmentation allows application developers to interact with simplified guest clusters while the host cluster handles the complex virtualized infrastructure management, thus reducing the complexity burden on developers without sacrificing infrastructure management capabilities.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The host cluster acts as an intermediary between the virtualized infrastructure and guest clusters. It provides the necessary infrastructure management expertise and capabilities while presenting a simplified interface to guest clusters, thereby shielding application developers from complex infrastructure details while maintaining full infrastructure management functionality.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If application developers directly manage Kubernetes clusters, then application deployment flexibility is improved, but the ease of operation decreases due to required infrastructure management expertise

Engineering Contradiction:
Improveapplication deployment flexibilityVSAvoidoperation simplicity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

By segmenting the system into host and guest clusters, application developers can deploy applications with high flexibility in guest clusters while the operation complexity is absorbed by the host cluster. This segmentation maintains deployment flexibility while improving ease of operation for developers.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The host cluster provides self-service capabilities by automatically handling the complex infrastructure management tasks required for Kubernetes operation. Application developers can deploy applications flexibly in guest clusters without needing to perform complex infrastructure management operations themselves, thus improving ease of operation while maintaining deployment flexibility.

Inventive Principle:
Principle #25Self-service

3Productivity

If virtualized infrastructure management and cluster management are integrated, then system integration efficiency is improved, but the difficulty of detecting and measuring system state increases

Engineering Contradiction:
Improveintegration efficiencyVSAvoidsystem state monitoring difficulty
Core Design Contradiction:
ProductivityVSDifficulty of detecting and measuring

Solution Approach 1:

The system segments monitoring and management functions between host and guest clusters. While integration efficiency is maintained through the host-guest relationship, the segmented structure allows for easier detection and measurement of system state by isolating different monitoring concerns to appropriate cluster levels, reducing overall monitoring complexity.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12613725B2Pod deployment in a guest cluster executing as a virtual extension of management cluster in a virtualized computing system
Publication Date: 2026.04.28 VMWARE INC
  • US12613725B2 patent drawing
  • US12613725B2 patent drawing
  • US12613725B2 patent drawing

AI summary

An example virtualized computing system includes a host cluster having hosts and a virtualization layer executing on hardware platforms of the hosts, the virtualization layer supporting execution of virtual machines (VMs), the VMs including pod VMs, the pod VMs including container engines supporting execution of containers in the pod VMs; and an orchestration control plane integrated with the virtualization layer, the orchestration control plane including a master server configured to manage the pod VMs and first VMs of the VMs. The virtualized computing system further includes a guest cluster executing in the first VMs and managed by the orchestration control plane, the guest cluster including a guest master server configured to, in cooperation with the master server, deploy first pods in the pod VMs.