# US 2022/0035651 A1 · Distributed network plugin agents for container networking

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2022/0035651 A1
- Document ID: US20220035651A1
- Status: Published application
- Kind: A1
- Application number: 17/072,115
- Filed: 2020-10-16
- Published: 2022-02-03
- Earliest claimed: 2020-07-29
- Assignees: VMware, Inc.
- Applicants: VMware, Inc.
- Inventors: Alok Kumar Maurya; Nilesh Suryavanshi; Kalyan Maddipatla
- Web page: https://patentgrep.com/patent/US20220035651A1

## CPC

- G06F 9/45558: {Hypervisor-specific management and integration aspects}
- G06F 9/5072: {Grid computing}
- G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications}
- G06F 9/547: {Remote procedure calls [RPC]; Web services}
- H04L 41/042: comprising distributed management centres cooperatively managing the network
- H04L 41/046: comprising network management agents or mobile agents therefor
- H04L 41/0816: the condition being an adaptation, e.g. in response to network events
- H04L 41/122: of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
- H04L 63/0272: {Virtual private networks}
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- G06F 2009/4557: {Distribution of virtual machine instances; Migration and load balancing}
- G06F 2009/45595: {Network integration; Enabling network access in virtual machine instances}
- H04L 41/40: using virtualisation of network functions or resources, e.g. SDN or NFV entities
- H04L 43/0817: by checking functioning
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Some embodiments of the invention provide a method for connecting deployed machines in a set of one or more software-defined datacenters (SDDCs) to a virtual private cloud (VPC) in an availability zone (AZ). The method deploys network plugin agents (e.g. listening agents) on multiple host computers and configures the network plugin agents to receive notifications of events related to the deployment of network elements from a set of compute deployment agents executing on the particular deployed network plugin agent's host computer. The method, in some embodiments, is performed by a network manager that receives notifications from the deployed network plugin agents regarding events relating to the deployed machines and, in response to the received notifications, configures network elements to connect one or more sets of the deployed machines.

## Claims

### Claim 1

A method for connecting deployed machines to a virtual private cloud (VPC) in an availability zone (AZ):
deploying a plurality of network plugin agents on a plurality of host computers executing a plurality of machines that are deployed by a plurality of compute deployment agents;
configuring each particular deployed network plugin agent to receive notifications of events from a set of compute deployment agents executing on the particular deployed network plugin agent's host computer;
receiving notifications from the deployed network plugin agents regarding events relating to the deployed machines; and
in response to the received notifications, configuring network elements to connect one or more sets of the deployed machines.

### Claim 2 (depends on 1)

The method of claim 1, wherein configuring network elements to connect one or more sets of the deployed machines comprises directing a network controller to configure the network elements to connect the one or more sets of the deployed machines.

### Claim 3 (depends on 1)

The method of claim 1, wherein configuring each particular deployed network plugin agent to receive notifications of events from a set of compute deployment agents comprises registering the particular network plugin agent with a set of application programming interface (API) processors of the set of compute deployment agents executing on the particular deployed network plugin agent's host computer that receives requests to deploy machines.

### Claim 4 (depends on 3)

The method of claim 3, wherein the set of API processors and the network plugin agent communicate over a network that connects the set of API processors to the network plugin agent.

### Claim 5 (depends on 3)

The method of claim 3, wherein the compute deployment agent is a master worker node of a Kubernetes worker node cluster that receives requests to modify a set of machines in the Kubernetes worker node cluster.

### Claim 6 (depends on 5)

The method of claim 5, wherein the request to modify the set of machines in the Kubernetes cluster comprises at least one of (1) a request to add a machine in the set of machines, (2) a request to remove a machine in the set of machines, and (3) a request to modify a deployed machine, the set of machines comprising at least one of a container, and a pod that requires a connection to the VPC.

### Claim 7 (depends on 6)

The method of claim 6, wherein configuring network elements to connect one or more sets of the deployed machines comprises (1) assigning a set of network addresses to the machines in the sets of the deployed machines and (2) updating a set of forwarding elements of the VPC to use at least one network address in the set of network addresses to connect to the sets of the deployed machines.

### Claim 8 (depends on 5)

The method of claim 5, wherein a particular master worker node of a particular Kubernetes cluster monitors a set of other worker nodes in the particular Kubernetes cluster and the API processor receives requests based on at least one of the monitoring of the set of other worker nodes and an instruction received from outside the particular Kubernetes cluster.

### Claim 9 (depends on 8)

The method of claim 8, wherein a request received at the API processor is based on detecting, at the master worker node of the Kubernetes cluster, that a machine in the Kubernetes cluster has failed and determining that a replacement machine should be deployed, wherein the request received at the API processor is a request to deploy the replacement machine.

### Claim 10 (depends on 1)

The method of claim 1, wherein the network plugin agent is an instance of a distributed network plugin agent (DNPA), each instance of the DNPA comprising:
a request queue for storing requests related to notifications received by the network plugin agent;
a cluster manager plugin that processes requests relating to cluster-level requests stored in the request queue, wherein a cluster-level request is a request relating to a worker node cluster in a plurality of worker node clusters executing on the plurality of host computers;
a pod manager plugin that processes requests related to pod-level requests relating to worker nodes executing on the host computer that are stored in the request queue; and
a communication agent that communicates requests processed by the cluster manager plugin and pod manager plugin to a network manager, wherein the network manager configures the network elements in the availability zone based on the requests processed by the cluster manager and pod manager.

### Claim 11 (depends on 10)

The method of claim 10, wherein,
one DNPA instance in the plurality of DNPA instances executing on the plurality of host computers is designated as a master DNPA instance for the DNPA, and
the master DNPA instance (1) receives data regarding a number of pending requests stored in a request queue associated with a DNPA instance executing on each of the plurality of host computers, (2) determines a maximum rate for processing requests at the network manager, (3) determines the total number of pending requests related to the deployment of machines, (4) calculates, for each DNPA instance in the plurality of DNPA instances, a rate limit specifying a rate at which the DNPA instance is allowed to communicate requests related to the deployment of machines to the network manager, and (5) distributes the rate limit calculated for each particular DNPA instance to the particular DNPA instance.

### Claim 12 (depends on 11)

The method of claim 11, wherein the master DNPA instance calculates the rate limit for each particular DNPA instance based on (1) the number of pending requests associated with the particular DNPA instance, (2) the maximum rate for processing requests at the manager, and (3) the total number of pending requests related to the deployment of machines.

### Claim 13 (depends on 11)

The method of claim 11, wherein the master DNPA instance selects a cluster manager of a particular DNPA instance to be a master cluster manager plugin for at least one worker node cluster in the plurality of worker node clusters, the master cluster manager plugin of each particular worker node cluster being the only cluster manager plugin to process cluster-level requests related to the particular worker node cluster.

### Claim 14 (depends on 13)

The method of claim 13, wherein the master DNPA instance receives data regarding resources available on each of the plurality of host computers, and the master cluster manager plugin for each worker node is selected based on the received data regarding the resources available on each of the plurality of host computers.

### Claim 15 (depends on 13)

The method of claim 13, wherein
the DNPA is associated with a set of Kubernetes clusters comprising worker nodes,
each Kubernetes cluster has a master worker node that receives API requests related to the Kubernetes cluster,
the master worker node of each Kubernetes cluster in the set of Kubernetes clusters connects to a logical network that connects the master worker nodes to network plugin agents deployed on the plurality of host computers, and
each network plugin agent executing on each host computer in the plurality of host computers receives notifications from each master worker node and determines whether to add a related request to a request queue on the same host computer as the network plugin agent based on whether the notification relates to either (1) a cluster-level request related to a cluster for which a cluster manager on the same host computer has been designated a master cluster manager or (2) a pod-level request related to a worker node executing on the same host computer.

### Claim 16 (depends on 10)

The method of claim 10, wherein the notification comprises a forwarded intent-based application programming interface (API) request to modify a set of machines received at an API processor, and the network plugin agent parses the forwarded API request to generate at least one of a first set of cluster-level requests and a second set of pod-level requests to identify at least one of a cluster-level request and a pod-level request to store in the request queue on the host computer.

### Claim 17 (depends on 10)

The method of claim 10, wherein the notification comprises a forwarded CRUD (Create, Read, Update and Delete) request to modify a set of machines received at a worker node executing on the host computer and the network plugin agent parses the forwarded CRUD request to identify at least one of a cluster-level request and a pod-level request to store in the request queue on the host computer.

### Claim 18 (depends on 11)

The method of claim 11, wherein each DNPA instance processes requests stored in a request queue of the host computer on which the DNPA instance executes in an order in which they were stored in the request queue on the host computer at a rate that is no greater than the rate limit received from the master DNPA instance.

### Claim 19 (depends on 11)

The method of claim 11, wherein the data regarding a number of pending requests comprises data regarding a number of pending cluster-level requests and a number of pending pod-level requests, the rate limit is a first rate limit specifying a rate at which the DNPA instance is allowed to communicate cluster-level requests related to the deployment of machines to the network manager and the master DNPA instance calculates, for each DNPA instance in the plurality of DNPA instances, a second rate limit specifying a rate at which the DNPA instance is allowed to communicate pod-level requests related to the deployment of machines to the network manager.

### Claim 20 (depends on 11)

The method of claim 11, wherein the DNPA is associated with a set of Kubernetes clusters comprising worker nodes and each worker node on a host computer connects to a hyperbus on the host computer that connects the worker nodes to the network plugin agent, wherein notification sent from each worker node to the network plugin agent are sent using the hyperbus.
