Centralized Kubernetes Orchestration via Platform-Specific Microservices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional Kubernetes cluster management systems lack the ability to centrally manage external Kubernetes clusters, preventing IT administrators from scaling infrastructure, updating Kubernetes versions, and utilizing platform-specific features due to a lack of infrastructure knowledge.
Innovation Solution
A centralized Kubernetes orchestration system with platform-specific knowledge that enables IT administrators to manage Kubernetes deployments and underlying cluster infrastructure through automation, using platform-specific tooling and microservices to connect with managed platforms like VMware Tanzu, GKE, EKS, AKS, and Red Hat OpenShift, allowing for tasks such as scaling nodes and updating Kubernetes versions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If conventional Kubernetes management systems are used, then users can manage Kubernetes deployments and container workloads, but IT administrators cannot centrally manage external cluster infrastructure
Solution Approach 1:
The patent introduces a centralized management system that acts as an intermediary between IT administrators and external Kubernetes clusters. This system includes platform-specific adapters that translate generic management requests into platform-specific operations, enabling centralized control while maintaining compatibility with various managed Kubernetes platforms (AWS EKS, Azure AKS, Google GKE, etc.). The intermediary layer provides infrastructure information to administrators and executes management tasks without requiring direct access to each cluster.
Solution Approach 2:
The management system is segmented into multiple components: a centralized control plane, platform-specific adapters, and cluster agents. Each adapter handles specific platform requirements (AWS, Azure, Google, etc.), allowing the system to manage diverse Kubernetes platforms through standardized interfaces. This segmentation enables the system to provide centralized management while adapting to platform-specific features and constraints.
2Adaptability or versatility
If vendor-specific Kubernetes implementations are used, then platform-specific features are available, but unique logic and tooling are required for each platform
Solution Approach 1:
The centralized management system implements a universal control plane that can manage multiple vendor-specific Kubernetes platforms through standardized interfaces. The system provides multi-functional capabilities to handle provisioning, monitoring, scaling, and upgrading across AWS EKS, Azure AKS, Google GKE, and other platforms. Platform-specific adapters translate universal management operations into vendor-specific commands, reducing the need for separate tooling for each platform.
Solution Approach 2:
Platform-specific adapters serve as intermediaries between the universal control plane and vendor-specific Kubernetes implementations. These adapters handle platform-specific logic and tooling requirements, translating generic management requests into platform-appropriate operations. This intermediary layer abstracts the complexity of managing multiple vendor-specific platforms, presenting a unified interface to administrators while maintaining platform-specific capabilities.
3Productivity
If the hosting platform is treated as a black box, then Kubernetes software maintains portability, but administrators cannot scale infrastructure or perform version updates
Solution Approach 1:
The management system implements feedback mechanisms where cluster agents continuously report infrastructure information (node status, resource utilization, version details) to the centralized control plane. This feedback loop provides administrators with visibility into cluster infrastructure without compromising Kubernetes portability. The system uses this information to enable automated scaling decisions, version update planning, and infrastructure optimization while maintaining the black box nature of the underlying platform from Kubernetes' perspective.
Solution Approach 2:
The system performs preliminary actions by pre-configuring infrastructure resources and preparing version updates before Kubernetes software needs them. The centralized management system can proactively scale infrastructure, pre-stage Kubernetes version updates, and configure platform-specific features before they are needed by the applications. This preliminary action enables efficient infrastructure management while maintaining Kubernetes portability and abstraction.
Data Source
AI summary
A method for managing remote Kubernetes clusters employs a central orchestrator with cluster integration interfaces for one or more managed Kubernetes platforms. A cluster of interest is selected via one of the interfaces and a connection with the applicable platform is registered. The registered connection may include platform account credentials and cluster admin role information to an authenticated cluster-admin role defined for the platform. A platform-specific microservice (PSM), provisioned with platform-specific logic and tooling, is instantiated. The PSM retrieves an administrative manifest including one or more administrative pods enabling the central orchestrator to communicate securely with the platform and deploy and manage application workloads on the cluster. The cluster of interest is then imported into the central orchestrator enabling administrators to perform platform-specific management tasks, including cluster infrastructure configuration tasks such as scaling nodes, updating Kubernetes versions, and modifying access/permission roles.