# US 2025/0097102 A1 · Scaling for split-networking datapath > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2025/0097102 A1 - Document ID: US20250097102A1 - Status: Published application - Kind: A1 - Application number: 18/962,856 - Filed: 2024-11-27 - Published: 2025-03-20 - Earliest claimed: 2021-07-23 - Assignees: VMware, Inc. - Applicants: VMware LLC - Inventors: Yong Wang; Cheng-Chun Tu; Sreeram Kumar Ravinoothala; Yu Ying - Web page: https://patentgrep.com/patent/US20250097102A1 ## CPC - H04L 41/0816: the condition being an adaptation, e.g. in response to network events - H04L 41/0897: by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or entities - H04L 41/0876: {Aspects of the degree of configuration automation} - 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 implementing an edge device that handles data traffic between a logical network and an external network. The method monitors resource usage of a node pool that includes multiple nodes that each executes a respective set of pods. Each of the pods is for performing a respective set of data message processing operations for at least one of multiple logical routers. The method determines that a particular node in the node pool has insufficient resources for the particular node's respective set of pods to adequately perform their respective sets of data message processing operations. Based on the determination, the method automatically provides additional resources to the node pool by instantiating at least one additional node in the node pool. ## Claims ### Claim 1 A method comprising: providing a plurality of nodes, the plurality of nodes comprising a first node and a second node; executing a first set of pods by the first node, the first set of pods comprising a first L4 pod; processing a first data message for a first logical router by executing a run-to-completion thread by the first L4 pod; assigning a first core of the first node for processing data traffic between a logical network and an external network; determining that the first node has reached a predetermined threshold limit in response to a resource request; and adding a third node to the plurality of nodes for providing resources associated with the resource request. ### Claim 2 (depends on 1) The method of claim 1, wherein the first node comprises a set of hardware for executing a first virtual machine. ### Claim 3 (depends on 1) The method of claim 1, wherein the second node is configured to a second set of pods. ### Claim 4 (depends on 1) The method of claim 1, further comprising rescheduling the third node. ### Claim 5 (depends on 1) The method of claim 1, further comprising allocating resources associated with the second node to the third node. ### Claim 6 (depends on 1) The method of claim 1, wherein the predetermined threshold limit comprises a predetermined number of resource requests. cm 7. The method of claim 1, further comprising scheduling a second pod for the plurality of nodes after adding the third node to the plurality of nodes. ### Claim 8 (depends on 7) The method of claim 7, wherein the second pod is configured to perform stateless data message processing operations. ### Claim 9 (depends on 7) The method of claim 7, wherein the second pod is configured to perform layer 5 service operations. ### Claim 10 (depends on 1) The method of claim 1, wherein the first plurality of nodes is associated with a Kubernetes cluster for implementing an edge device. ### Claim 11 A non-transitory machine readable medium storing a program for execution by a set of processing units, the program comprising sets of instructions for: providing a plurality of nodes, the plurality of nodes comprising a first node and a second node; executing a first set of pods by the first node, the first set of pods comprising a first L4 pod; processing a first data message for a first logical router by executing a run-to-completion thread by the first L4 pod; assigning a first core of the first node for processing data traffic between a logical network and an external network; determining that the first node has reached a predetermined threshold limit in response to a resource request; and adding a third node to the plurality of nodes for providing resources associated with the resource request. ### Claim 12 (depends on 11) The non-transitory machine readable medium of claim 11, wherein the first node comprises a set of hardware for executing a first virtual machine. ### Claim 13 (depends on 11) The non-transitory machine readable medium of claim 11, wherein the second node is configured to a second set of pods. ### Claim 14 (depends on 11) The non-transitory machine readable medium of claim 11, further comprising a set of instructions for rescheduling the third node. ### Claim 15 (depends on 11) The non-transitory machine readable medium of claim 11, further comprising a set of instructions for allocating resources associated with the second node to the third node. ### Claim 16 (depends on 13) The non-transitory machine readable medium of claim 13, wherein the predetermined threshold limit comprises a predetermined number of resource requests. ### Claim 17 (depends on 11) The non-transitory machine readable medium of claim 11, further comprising a set of instructions for scheduling a second pod for the plurality of nodes after adding the third node to the plurality of nodes. ### Claim 18 (depends on 17) The non-transitory machine readable medium of claim 17, wherein the second pod is configured to perform stateless data message processing operations. ### Claim 19 (depends on 17) The non-transitory machine readable medium of claim 17, wherein the second pod is configured to perform layer 5 service operations. ### Claim 20 (depends on 13) The non-transitory machine readable medium of claim 13, wherein the first plurality of nodes is associated with a Kubernetes cluster for implementing an edge device.