Container Pod Communication via VNICs and IPvlan
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current container environments, such as Kubernetes, face inefficiencies in pod communications due to the need for bridging and encapsulation, which increases computation and data overhead and prevents identification of specific sender and recipient information in communication logs, and lack direct pod-to-pod communication capabilities.
Innovation Solution
Creating a container environment with a management component that sets a flag for direct pod communications, using virtualized network interface cards (VNICs) attached to nodes, and custom resources to store IP addresses, allowing pods to communicate directly via IP addresses through virtual communication devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If bridge device encapsulation is used for pod communications, then network isolation and security are improved, but computation overhead and data overhead increase
Solution Approach 1:
The patent extracts the encapsulation function from the communication path by using IPvlan devices that allow direct IP-based communication between pods without requiring bridge device encapsulation. This removes the computational overhead of encapsulation/decapsulation while maintaining network isolation through IP address management and routing controls.
Solution Approach 2:
The patent introduces IPvlan devices as intermediary network interfaces that enable direct pod-to-pod communication at the IP layer without bridge encapsulation. The IPvlan device acts as a mediator that provides L2 networking capabilities over L3 IP addresses, allowing efficient direct communication while maintaining security through IP-based access controls.
2Reliability
If bridge device encapsulation is used for pod communications, then network isolation is improved, but identification of sender and recipient information in communication logs is prevented
Solution Approach 1:
The patent extracts the network isolation function from bridge device encapsulation and implements it through IP address management and routing. This allows communication flow logs to capture actual IP addresses of senders and recipients directly, providing full visibility while maintaining isolation through IP-based security policies and routing tables.
3Loss of energy
If direct pod-to-pod communication is implemented, then data transmission overhead is reduced, but network configuration complexity increases
Solution Approach 1:
The patent makes the network interface universal by implementing IPvlan devices that combine L2 switching capabilities with L3 IP routing in a single interface. This multi-functionality allows direct pod-to-pod communication with standard IP addressing, eliminating the need for complex bridge configurations while maintaining data efficiency.
4Productivity
If virtualized network interface cards are attached to each node, then direct communication capability is improved, but device complexity increases
Solution Approach 1:
The patent merges the network interface card functionality with IPvlan virtualization to create a unified VNIC structure. Each node receives a VNIC that directly provides IP-based communication capabilities, combining physical NIC functions with virtualization in a single attached device, thereby improving communication efficiency without proportionally increasing complexity.
Data Source
AI summary
Techniques are described for creating a container environment that implements direct communications between pods. This includes the creation of a management component (such as a control plane) of the container environment, the creation of nodes within an implementation component (such as a data plane) of the container environment, and the attaching of virtualized network interface cards (VNICs) to each node. This also includes creating a custom resource for each node, where the custom resource stores internet protocol (IP) addresses assigned to the node and stored within the VNICs for the node. Pods implemented within these nodes obtain an IP address from the VNICs for their respective node and communicate with each other utilizing the IP addresses via virtual communication devices and the VNICs.