Kubernetes Cluster Network Analysis Through Manifest Parsing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The analysis of Kubernetes cluster network topologies is typically done manually by experts, which is time-consuming and prone to errors, with no known methods for automated or semi-automated solutions.

Innovation Solution

A computer-implemented method for analyzing Kubernetes cluster network topologies by parsing manifests to extract pods and other resources, determining communication relationships, and displaying them graphically, while considering network policies to modify and conform to reference relationships.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual analysis by experts is used, then accuracy and reliability of network topology analysis is improved, but time consumption and labor requirements increase

Engineering Contradiction:
Improveaccuracy of network topology analysisVSAvoidtime consumption for analysis
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent replaces manual expert analysis with an automated computer-based system that parses manifests, extracts pods, and determines communication relationships through algorithmic processing. This substitution eliminates human labor while maintaining analytical accuracy through systematic computational methods.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system performs self-service by automatically analyzing its own input (manifests) without requiring external expert intervention. The computer processor independently extracts information, determines relationships, and generates visualizations, making the analysis process autonomous and repeatable.

Inventive Principle:
Principle #25Self-service

2Productivity

If automated analysis method is implemented, then time consumption is reduced, but complexity of the system increases

Engineering Contradiction:
Improvespeed of network topology analysisVSAvoidcomplexity of analysis system
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the complex analysis task into distinct modular steps: receiving manifests, extracting pods, determining communication relationships, and displaying results. Each step is handled by a dedicated component or function, making the overall system manageable and easier to implement despite the complexity of the complete solution.

Inventive Principle:
Principle #1Segmentation

3Loss of information

If comprehensive network topology analysis is performed, then completeness of information is improved, but processing time and computational resources increase

Engineering Contradiction:
Improvecompleteness of network topology informationVSAvoidprocessing time for analysis
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-defining the extraction and analysis logic before actual analysis runs. The computer processor is programmed with specific instructions to extract particular pod information and determine communication relationships in advance, enabling efficient processing when actual analysis is needed without time-consuming on-the-fly decisions.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP4625166A1Exploring the network configuration of kubernetes clusters
Publication Date: 2025.10.01 DYNATRACE LLC
  • EP4625166A1 patent drawingFigure 1a~1d
  • EP4625166A1 patent drawingFigure 1c~3
  • EP4625166A1 patent drawingFigure 4~6a

AI summary

The present disclosure relates to a computer-implemented method for deploying software by analyzing a manifest describing a portion of the network topology in a distributed computing environment. The objective of the disclosure is to find methods for deploying software in the distributed computing environment comprising the automatic or semi-automatic analysis of the network topology in the computing environment. This is solved by receiving the manifest; extracting all pods enumerated in the manifest; for all pods, determining the communication relationship between a given pod and another pod in the manifest; logging the communication relationship between the given pod and the another pod; and displaying the communication relationship between the given pod and the another pod on a display device. (Fig. 1a)