Unified Container Resource Visualization Across Multiple Clusters

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In container orchestration systems, operators face difficulties in determining deployment issues across multiple clusters, as they need to enter multiple commands into different cluster controllers, which is time-consuming and requires detailed knowledge of resources and clusters, leading to potential service unavailability and user dissatisfaction.

Innovation Solution

A method that obtains deployment information across multiple clusters, generates user interface imagery representing resources with a single representation per resource, and includes group deployment status indicators to visualize the deployment status of resources across clusters, allowing operators to quickly identify issues.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If operators check deployment status across multiple clusters by entering commands into different cluster controllers, then they can obtain detailed deployment information, but the process becomes time-consuming and complex

Engineering Contradiction:
Improvedeployment status informationVSAvoidtime to debug deployment issues
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The patent merges deployment status information from multiple clusters into a single unified user interface. The system collects deployment status from multiple cluster controllers and presents them together in one consolidated view, allowing operators to see all deployment information across clusters without needing to query each cluster separately. This combining approach resolves the contradiction by providing complete information while dramatically reducing the time required.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent introduces an intermediary component that acts as a mediator between multiple cluster controllers and the operator. This intermediary collects deployment status information from various clusters, processes it, and presents it in a unified manner. The intermediary layer abstracts the complexity of multiple clusters behind a single interface, resolving the contradiction by providing comprehensive information access without requiring operators to interact with each cluster individually.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If operators monitor deployment status across multiple clusters individually, then they can track each resource's status, but the interface complexity increases and becomes difficult to manage

Engineering Contradiction:
Improvedeployment status trackingVSAvoiduser interface complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent combines multiple individual resource representations from different clusters into a single unified representation in the user interface. Instead of showing separate entries for the same resource type across multiple clusters (which would create complexity), the system merges them into one consolidated view that displays the resource along with its deployment status across all clusters. This maintains reliability of tracking while eliminating interface complexity.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates a universal resource representation that serves multiple functions simultaneously. A single resource representation in the interface can display deployment status across multiple clusters, show deployment timing information, and provide access to detailed status for each cluster. This multi-functional approach maintains comprehensive tracking capability while keeping the interface simple and manageable.

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

3Loss of information

If the system provides detailed deployment information for each resource across all clusters, then operators can see complete status, but the interface becomes less scalable as cluster numbers increase

Engineering Contradiction:
Improvedeployment status visibilityVSAvoidscalability to multiple clusters
Core Design Contradiction:
Loss of informationVSAdaptability or versatility

Solution Approach 1:

The patent implements a scalable merging approach where resource representations are consolidated across clusters. Instead of creating separate interface elements for each cluster-instance combination, the system merges resources with the same identity into single representations that adaptively display information relevant to the number of clusters. This approach maintains complete visibility of deployment status while ensuring the interface remains scalable regardless of how many clusters are added to the system.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS12112187B2Scalable visualization of a containerized application in a multiple-cluster environment
Publication Date: 2024.10.08 RED HAT LLC
  • US12112187B2 patent drawing
  • US12112187B2 patent drawing
  • US12112187B2 patent drawing

AI summary

Scalable visualization of a containerized application in a multiple-cluster environment is disclosed. Deployment information that identifies a deployment status on a plurality of clusters of a set of resources that compose a containerized application is obtained. User interface imagery that identifies the set of resources, wherein each resource in the set is represented in the user interface imagery by only one corresponding resource representation, irrespective of a number of clusters on which the resource is deployed, is generated. A corresponding group deployment status indicator based on a deployment status of the resource on each cluster on which the resource was to be deployed is determined for at least one resource. The corresponding group deployment status indicator is included in association with the resource representation that corresponds to the resource. The user interface imagery is presented on a display device.