Kubernetes Connectivity Graphs for Minimal Firewall Rules

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing container orchestration systems like Kubernetes face challenges in providing a clear, cluster-wide view of network connectivity due to the distributive nature of network policies, making it difficult to manage and verify allowed connections within and outside the cluster.

Innovation Solution

A method to generate a minimal list of firewall rules from a connectivity graph by iteratively merging rules with commonality, providing a textual representation of allowed connections that simplifies understanding and reduces errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If network policies are implemented in a distributed manner across Kubernetes nodes, then scalability and flexibility are improved, but the complexity of managing and verifying cluster-wide connectivity increases

Engineering Contradiction:
ImprovescalabilityVSAvoidconnectivity management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent extracts the network connectivity information from the distributed network policies and consolidates it into a centralized connectivity graph data structure. This allows the complex distributed connectivity state to be represented as a single manageable object that can be processed and verified centrally, resolving the contradiction between distributed scalability and centralized manageability

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The connectivity graph serves as an intermediary representation between the distributed network policies and the desired cluster-wide connectivity view. It translates the distributed policy statements into a unified graph structure that can be easily processed to generate firewall rules, bridging the gap between distributed implementation and centralized verification

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If detailed network connectivity tracking is implemented, then security and connectivity verification are improved, but the amount of information to process and manage increases

Engineering Contradiction:
Improveconnectivity verification accuracyVSAvoidinformation volume
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent merges multiple network policy statements into a unified connectivity graph structure. Instead of processing individual distributed policy entries separately, the graph consolidates connectivity information into a compact representation where nodes and edges capture the essential connectivity relationships, reducing information volume while maintaining verification accuracy

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The connectivity graph serves multiple functions simultaneously: it represents the current network connectivity state, enables verification of connectivity policies, generates firewall rules, and provides a basis for troubleshooting. This multi-functionality reduces the need for separate processing systems and minimizes overall information handling requirements

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

Data Source

PatentUS12418508B2Inferring cloud network connectivity as a minimal list of firewall rules
Publication Date: 2025.09.16 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US12418508B2 patent drawing
  • US12418508B2 patent drawing
  • US12418508B2 patent drawing

AI summary

A method, computer system, and a computer program product for determining a cluster connectivity is provided. The present invention may first include receiving as input a connectivity graph. The present invention may then include generating a minimal list of firewall rules from the received connectivity graph by iteratively merging firewall rules with commonality of connectivity attribute.