Kubernetes Cluster Orchestration Across Multiple Infrastructure Providers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional Kubernetes clusters are constrained to operate within a single infrastructure provider's resources, leading to over-dimensioning and increased costs due to the need to handle all foreseeable workloads, resulting in inefficient resource utilization and waste.

Innovation Solution

A system that coordinates the distribution of resource instances across multiple infrastructure providers, allowing Kubernetes master nodes to dynamically allocate and share resources based on traffic patterns, enabling clusters to span multiple providers and locations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If Kubernetes clusters are deployed on hosts within infrastructure controlled by a single infrastructure provider, then the infrastructure provider can manage all workloads, but the infrastructure becomes over-dimensioned resulting in resource waste and increased cost

Engineering Contradiction:
Improveworkload management capabilityVSAvoidresource waste
Core Design Contradiction:
ReliabilityVSLoss of substance

Solution Approach 1:

The patent segments the Kubernetes cluster management by allowing master nodes to be distributed across multiple infrastructure providers. Each infrastructure provider hosts a portion of the master nodes and associated workloads, dividing the previously centralized resource pool into distributed segments that can be independently managed and optimized.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent enables infrastructure providers to serve multiple functions by hosting Kubernetes master nodes for multiple different Kubernetes clusters. A single infrastructure provider can simultaneously support workloads from multiple cloud providers, increasing resource utilization efficiency and reducing waste through multi-functional deployment.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If infrastructure is dimensioned to handle all foreseeable workloads, then all workloads can be accommodated, but resource utilization becomes inefficient and costs increase

Engineering Contradiction:
Improveworkload accommodation capabilityVSAvoidresource utilization efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent implements dynamic resource allocation where Kubernetes master nodes can be dynamically added or removed from infrastructure providers based on actual workload demands. The system continuously monitors workload patterns and adjusts the distribution of master nodes across infrastructure providers, transitioning from static over-provisioning to dynamic adaptation that matches resources to actual needs.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent changes the parameter of infrastructure provisioning from fixed to variable by allowing the number and distribution of Kubernetes master nodes across infrastructure providers to be adjusted based on workload metrics. This parameter change enables the system to scale resources up or down dynamically, improving both adaptability and resource utilization efficiency.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If multiple Kubernetes master nodes are deployed across multiple infrastructure providers, then resource utilization efficiency improves, but system complexity increases

Engineering Contradiction:
Improveresource utilization efficiencyVSAvoidcluster management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer that manages the complexity of distributed master nodes across multiple infrastructure providers. This intermediary coordination mechanism handles the orchestration, monitoring, and management of master nodes distributed across different providers, abstracting the complexity from the overall system while enabling efficient multi-provider resource utilization.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20230222006A1Container Orchestration System
Publication Date: 2023.07.13 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US20230222006A1 patent drawing
  • US20230222006A1 patent drawing
  • US20230222006A1 patent drawing

AI summary

The present disclosure provides a system for coordinating the distribution of resource instances (e.g. Kubernetes nodes) that belong to different infrastructure providers providing resource instances at different locations. Each infrastructure provider provides one or more resource instances. The resource instances provide by an infrastructure can be spread over multiple locations. Several Kubernetes master nodes are deployed to manage the RIs spread among multiple infrastructure providers and multiple locations.