Multi-network Service Discovery in Container Orchestration

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Container orchestration platforms that expose pods to only a single network interface are ineffective in handling scenarios like 5G networks, increasing remote VPN users, and multi-tenant networks, as they lack the flexibility to manage multiple network interfaces.

Innovation Solution

Implementing a multi-network/domain service discovery method that allows pods to be exposed to multiple network interfaces by creating a pool of servers with multiple network interface controllers (NICs) defined by network attachment definition objects, generating a virtual service object, and updating the service object's status with the IP address of the virtual service.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a container orchestration platform exposes pods to only a single network interface, then the system structure remains simple, but the platform loses flexibility and cannot handle complex network scenarios like 5G networks, remote VPN users, and multi-tenant networks

Engineering Contradiction:

Improvenetwork scenario handling capabilityVSAvoidmulti-network interface configuration

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the network interface configuration by introducing separate Network Attachment Definitions (NADs) for each network interface. Each NAD independently defines a network interface's properties, allowing pods to be attached to multiple independent network interfaces rather than managing a single complex interface configuration.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent implements a universal service discovery mechanism that works across multiple network interfaces. The service discovery system can discover services attached to any network interface through the unified NAD framework, making the system adaptable to various network scenarios (5G, VPN, multi-tenant) without requiring separate specialized mechanisms for each.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If multiple network interfaces are supported through Network Attachment Definitions, then network flexibility is improved, but the service discovery process becomes more complex

Engineering Contradiction:

Improvemulti-network interface supportVSAvoidservice discovery process

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces Network Attachment Definitions (NADs) as intermediary objects that mediate between the pod networking requirements and the service discovery process. NADs serve as a standardized interface that translates complex multi-network interface configurations into a uniform format that the service discovery system can process consistently.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the parameter representation in service discovery by using NAD objects that standardize network interface information. Instead of handling multiple different network interface types with different parameters, the system uniformly represents all network interfaces through the NAD parameter set, simplifying the service discovery logic.

Inventive Principle:

Principle #35Parameter changes

3Adaptability or versatility

If pods are attached to multiple network interfaces via annotations, then network versatility is enhanced, but the configuration and management complexity increases

Engineering Contradiction:

Improvenetwork interface attachment capabilityVSAvoidconfiguration and management

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent implements preliminary configuration through Network Attachment Definitions that are created and annotated before pods are deployed. The NAD objects pre-define the network interface configurations, and pods simply need to reference these pre-configured NADs through annotations, rather than requiring complex real-time configuration during pod deployment or operation.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS20250097288A1Multi-network/domain service discovery in a container orchestration platform

Publication Date: 2025.03.20 VMWARE INC

AI summary

A computer-implemented method, medium, and system for multi-network/domain service discovery in a container orchestration platform are disclosed. In one computer-implemented method, a pool of servers with a plurality of network interface controllers (NICs) is created in a load balancer and by an operator in a worker node of a container orchestration platform, where each of the plurality of NICs is defined by a corresponding network attachment definition (NAD) object of a plurality of NAD objects. A virtual service object is generated using an annotation corresponding to the plurality of NAD objects. The virtual service object is associated to the pool of servers with the plurality of NICs. An internet protocol (IP) address of the virtual service object is transmitted to the container orchestration platform to update a status of a service object in the container orchestration platform using the IP address.