Service Load Balancer Backend Virtual Network Selection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing load balancers in virtualized computing infrastructures default to the default virtual network interface for sending traffic to pods, leading to inefficiencies and increased configuration management complexity, especially in container-based environments where IP addresses are non-deterministic and pods can be transient.
Innovation Solution
Configure load balancers to use specified virtual network interfaces for backend pods by annotating service definitions, allowing the network controller to identify and utilize the appropriate virtual network interfaces for load balancing, thereby improving scalability and reducing configuration complexity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If load balancers use the default virtual network interface for sending traffic to pods, then configuration is simpler, but scalability and efficiency deteriorate due to increased configuration management complexity and inability to handle multiple virtual networks
Solution Approach 1:
The patent segments the network interface selection by introducing a dedicated field in the service definition that specifies which virtual network interface should be used for each backend pod. This segmentation allows the load balancer to handle multiple virtual networks separately rather than relying on a default interface, thereby improving scalability while maintaining configuration simplicity through structured service definitions.
Solution Approach 2:
The patent applies preliminary action by pre-configuring the service definition with explicit virtual network interface specifications before the load balancer operates. The service definition includes a field that identifies the specific virtual network interface to be used, allowing the network controller to prepare the correct interface mappings in advance, thus enabling scalable multi-network support without increasing operational complexity.
2Adaptability or versatility
If load balancers rely on non-deterministic IP addresses of transient pods, then container flexibility is maintained, but configuration management complexity increases
Solution Approach 1:
The patent introduces an intermediary mechanism in the form of a service definition that acts as a mediator between the load balancer and transient pods. The service definition includes a field that specifies the virtual network interface, serving as a stable reference point that bridges the load balancer and the ephemeral pod instances. This intermediary approach maintains container flexibility while reducing configuration management complexity by providing a structured interface specification layer.
Solution Approach 2:
The patent changes the parameter representation by moving from relying solely on non-deterministic IP addresses to using a structured service definition that includes explicit virtual network interface specifications. This parameter change allows the system to maintain container flexibility through dynamic pod creation while reducing configuration complexity by providing deterministic interface identification through the service definition field.
3Reliability
If load balancers must manage multiple virtual network interfaces for different services, then network segmentation is improved, but management interface burden increases
Solution Approach 1:
The patent segments the network interface management by introducing a dedicated field in the service definition that specifies which virtual network interface should be used for each backend pod. This segmentation allows different services to be associated with different virtual network interfaces, improving network segmentation and reliability while maintaining ease of management through a structured, field-based configuration approach.
Solution Approach 2:
The patent changes the management approach by transforming the interface selection from a complex management task to a simple parameter specification in the service definition. By adding a field that directly specifies the virtual network interface, the system improves network segmentation while reducing the management interface burden, as the interface selection becomes a straightforward configuration parameter rather than a complex management operation.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Techniques are described for specifying a backend virtual network for a service load balancer. An example orchestrator of this disclosure is configured to receive a service definition for a service implemented by load balancing service traffic for the service among a plurality of backend virtual execution elements, wherein the service definition specifies a first virtual network to use as a backend virtual network for the service, to instantiate, in a selected one of the computing devices, a backend virtual execution element for the service, and to configure, based on the service definition specifying the first virtual network to use as the backend virtual network for the service, a network controller for the virtualized computing infrastructure to configure a load balancer to load balance service traffic to a first virtual network interface, of the backend virtual element, for the first virtual network.