Abstract: 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.

Abstract: 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.

Abstract: Techniques are described for creating isolated pools of external, failover, and/or floating IP addresses. In one example, this disclosure describes a method including creating a plurality of virtual networks, creating a plurality of pools of external IP addresses, detecting a request to instantiate an object that identifies a specific pool from the plurality of pools of external IP addresses; and instantiating the object and configuring the object with an external IP address drawn from the specific pool. The pools of external IP addresses may be created and isolated on a per-namespace, per-service, or per-ingress basis.

Abstract: In general, the disclosure describes examples where a single software-defined network (SDN) controller is configured to receive an indication of a first cluster identifier for a first cluster of computing devices and receive an indication of a second cluster identifier for a second cluster of computing devices. In response to a determination that first configuration information indicates the first cluster identifier, the SDN controller is configured to configure a first set of virtual routers at the first cluster to connect the first group of workloads to a network using the first configuration information. In response to a determination that second configuration information indicates the second cluster identifier, the SDN controller is configured to configure a second set of virtual routers at the second cluster to connect the second group of workloads to a network using the second configuration information.

Abstract: In general, this disclosure describes techniques for a containerized router operating within a cloud native orchestration framework. In an example, a virtualized cell site router comprises a computing device configured with a containerized router, the computing device comprising: a containerized virtual router configured to execute on the processing circuitry and configured to implement a data plane for the containerized router; a containerized routing protocol process configured to execute on the processing circuitry and configured to implement a control plane for the containerized router; and a pod comprising a containerized distributed unit, wherein the containerized routing protocol process is configured to advertise routing information comprising reachability information for the containerized distributed unit.

Abstract: Techniques are described for creating isolated pools of external, failover, and/or floating IP addresses. In one example, this disclosure describes a method including creating a plurality of virtual networks, creating a plurality of pools of external IP addresses, detecting a request to instantiate an object that identifies a specific pool from the plurality of pools of external IP addresses; and instantiating the object and configuring the object with an external IP address drawn from the specific pool. The pools of external IP addresses may be created and isolated on a per-namespace, per-service, or per-ingress basis.

Abstract: In some examples, a method includes receiving, by an orchestrator for a virtualized computing infrastructure, namespace specification data the specifies a namespace, a first virtual network for the namespace, and a second virtual network for the namespace; sending, by the orchestrator to a network controller for the virtualized computing infrastructure, based on the namespace specification data, at least one request to create, for a virtual execution element to be deployed to the namespace and instantiated in a computing device of the virtualized computing infrastructure, respective virtual network interfaces for the first virtual network and the second virtual network; and send, by the network controller to the computing device, interface configuration data to configure a first virtual network interface for the first virtual network and a second virtual network interface for the second virtual network.

Abstract: A computing device includes processing circuitry coupled to a memory device, and an orchestration agent configured for execution by the processing circuitry. The orchestration agent is an agent of an orchestrator for a computing infrastructure that includes the computing device, wherein the orchestration agent is configured to: detect configuration events from the computing device to determine local configuration state of the computing device; aggregate the local configuration state from the computing device with configuration state from a network controller to generate aggregated configuration state; and store the aggregated configuration state for application to operation of the computing device.

Abstract: Techniques are described for providing a controller to configure, within a given namespace, a virtual network for a pod and an application service address for an application service to enable access to the pod. For example, the controller may configure in each namespace a virtual network for a logically-related group of one or more containers (“pod”) and application service address for an application service that is an abstraction which defines a logical set of pods and a policy by which to access the pods (e.g., load balancing). Techniques are also described for providing a controller to configure controller configures the service chain by configuring the left interface of a service node with a virtual routing and forwarding instance (VRF) identifying the pod of a first namespace and the right interface of the service node with a VRF identifying the application service of a second namespace.

Abstract: In some examples, a method includes receiving, by an orchestrator for a virtualized computing infrastructure, namespace specification data the specifies a namespace, a first virtual network for the namespace, and a second virtual network for the namespace; sending, by the orchestrator to a network controller for the virtualized computing infrastructure, based on the namespace specification data, at least one request to create, for a virtual execution element to be deployed to the namespace and instantiated in a computing device of the virtualized computing infrastructure, respective virtual network interfaces for the first virtual network and the second virtual network; and send, by the network controller to the computing device, interface configuration data to configure a first virtual network interface for the first virtual network and a second virtual network interface for the second virtual network.

Abstract: 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.

Abstract: In some examples, a method includes receiving, by an orchestrator for a virtualized computing infrastructure, namespace specification data the specifies a namespace, a first virtual network for the namespace, and a second virtual network for the namespace; sending, by the orchestrator to a network controller for the virtualized computing infrastructure, based on the namespace specification data, at least one request to create, for a virtual execution element to be deployed to the namespace and instantiated in a computing device of the virtualized computing infrastructure, respective virtual network interfaces for the first virtual network and the second virtual network; and send, by the network controller to the computing device, interface configuration data to configure a first virtual network interface for the first virtual network and a second virtual network interface for the second virtual network.

Abstract: 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.

Abstract: 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.

Abstract: Techniques are described for creating multiple virtual network interfaces usable by a logically-related group of one or more containers (“pod”) for communicating on respective virtual networks of a network infrastructure. In some examples, a control flow for pod network interface configuration on a host includes obtaining, by a CNI instance, a list of multiple virtual network interfaces from an agent of a network controller that is executing on the host. The single CNI instance processes the list of multiple virtual network interfaces to create corresponding virtual network interfaces for the pod and, for each of the virtual network interfaces, to attach the virtual network interface to the pod and to the virtual router or bridge for the host. In this way, the single CNI enables packetized communications by containers of the pod over multiple networks using the multiple virtual network interfaces configured for the pod.

Abstract: Techniques are disclosed for a unified control plane in a nested cluster environment. In one example, an underlay orchestrator for a virtualized computing infrastructure is configured to provision, in an underlay cluster of one or more servers, an overlay cluster of one or more overlay nodes. Each of the overlay nodes is a workload of one of the servers and has a virtual network interface. Further, each server executes a virtual router and a virtual router agent for the virtual router for routing packets among virtual network interfaces of the overlay nodes executed by the server. A network controller is configured to configure virtual network sub-interfaces for workloads of the overlay nodes to enable communications among workloads executing in different overlay nodes. Each of the sub-interfaces is a virtual network sub-interface of one of the virtual network interfaces.

Abstract: In some examples, a method includes receiving, by an orchestrator for a virtualized computing infrastructure, namespace specification data the specifies a namespace, a first virtual network for the namespace, and a second virtual network for the namespace; sending, by the orchestrator to a network controller for the virtualized computing infrastructure, based on the namespace specification data, at least one request to create, for a virtual execution element to be deployed to the namespace and instantiated in a computing device of the virtualized computing infrastructure, respective virtual network interfaces for the first virtual network and the second virtual network; and send, by the network controller to the computing device, interface configuration data to configure a first virtual network interface for the first virtual network and a second virtual network interface for the second virtual network.

Abstract: Techniques are described for creating multiple virtual network interfaces usable by a logically-related group of one or more containers (“pod”) for communicating on respective virtual networks of a network infrastructure. In some examples, a control flow for pod network interface configuration on a host includes obtaining, by a CNI instance, a list of multiple virtual network interfaces from an agent of a network controller that is executing on the host. The single CNI instance processes the list of multiple virtual network interfaces to create corresponding virtual network interfaces for the pod and, for each of the virtual network interfaces, to attach the virtual network interface to the pod and to the virtual router or bridge for the host. In this way, the single CNI enables packetized communications by containers of the pod over multiple networks using the multiple virtual network interfaces configured for the pod.

Abstract: A network device may receive first qualification indicators, for a first signal, from all line cards of the network device. The network device may, in response to the first qualification indicators, transmit instructions to all of the line cards to use the first signal. The network device may further receive second qualification indicators, for a second signal, from all of the line cards. In response to the second qualification indicators, the network device may store information for the second signal in order to use the second signal as a backup signal.