Scaling of logical router pods
Some embodiments provide a method for configuring logical routers of a logical network. The logical routers are implemented in a Kubernetes cluster as a first set of Pods that each perform logical forwarding operations for the logical routers and a second set of Pods that each perform L7 service operations for a respective logical router. From a Kubernetes control plane component, the method receives a notification that the first set requires scaling to include an additional Pod. The first-set Pods process data messages between the logical network and external networks. Within the network management system, the method defines at least one new interface for processing data messages between the logical network and external networks. The method configures the at least one interface on the additional Pod to communicate with external physical routers to receive traffic from the external networks and send traffic to the external networks.
1 . A method for operating a network management system, the method comprising:
receiving a first notification from a Kubernetes cluster that a first set of Pods requires scaling to include an additional Pod for processing data messages between a logical network and external networks, the Kubernete cluster comprising a first set of Pods and a second set of Pods, the first set of Pods being associated with forwarding operations of the logical network, the second set of Pods being association with service operations;
providing configuration data to the additional Pod; and
configuring an interface of the additional Pod to communicate with an external router of the external network.
2 . The method of claim 1 , further comprising defining at least a new interface for processing data messages between the logical network and external networks.
3 . The method of claim 1 , wherein each of the first set of Pods is configured to perform logical forwarding operations for logical routers of the Kubernetes cluster.
4 . The method of claim 1 , wherein each of the second set of Pods is configured to perform layer 7 (L7) service operations.
5 . The method of claim 1 , wherein the additional Pod is configured to send traffic to external network via the external router.
6 . The method of claim 1 , wherein the Kubernete cluster comprises a Kubernete control component configured to send the notification.
7 . The method of claim 6 , wherein the Kubernetes control plane component is an orchestrator defined to monitor the first and second sets of Pods.
8 . The method of claim 7 , wherein the orchestrator receives metrics reported by the Pods relating to processing load and determines when additional Pods are needed for the first and second sets of Pods.
9 . The method of claim 1 , wherein the additional comprises is a first additional Pod, the method further comprising:
receiving a second notification that the second set of Pods requires scaling to include a second additional Pod for a particular L7 service for a particular logical router; and
modifying a span of configuration data for the particular L7 service for the particular logical router to include the second additional Pod.
10 . The method of claim 9 , further comprising distributing the configuration data for the particular L7 service for the particular logical router to the second additional Pod.
11 . The method of claim 9 , further comprising modifying redirection rules for the first set of Pods to redirect data messages requiring the particular L7 service for the particular logical router to include the second additional Pod in addition to previously instantiated Pods for the particular L7 service for the particular logical router.
12 . The method of claim 1 , wherein the additional Pod initiates a routing protocol sessions with the external router.
13 . The method of claim 1 , configuring the additional Pod to redirect data messages to Pods in the second set of Pods for the second set of Pods to perform L7 service operations on the redirected data messages.
14 . The method of claim 1 , further comprising:
receiving a notification that the first set of Pods requires reduction of a number of Pods in the first set of Pods and that a particular Pod from the first set of Pods will be deleted; and
removing definition of interfaces associated with the particular Pod in the network management system.
15 . The method of claim 1 , further comprising receiving a notification that the first set of Pods requires reduction of a number of Pods in the first set of Pods and that a particular Pod from the first set of Pods will be deleted; and
removing definition of interfaces associated with the particular Pod in the network management system.
16 . A non-transitory machine-readable medium storing a program which when executed by at least one processing unit implements a network management system for configuring a plurality of logical routers of a logical network, the program comprising sets of instructions for:
receiving a first notification from a Kubernetes cluster that a first set of Pods requires scaling to include an additional Pod for processing data messages between the plurality of logical routers of the logical network and external networks, the Kubernete cluster comprising a first set of Pods and a second set of Pods, the first set of Pods being associated with forwarding operations of the logical network, the second set of Pods being association with service operations;
providing configuration data to the additional Pod; and
configuring an interface of the additional Pod to communicate with an external router of the external network.
17 . The non-transitory machine-readable medium claim 16 , wherein each of the first set of Pods is configured to perform logical forwarding operations for logical routers of the Kubernetes cluster.
18 . The non-transitory machine-readable medium claim 16 , wherein each of the second set of Pods is configured to perform layer 7 (L7) service operations.
19 . The non-transitory machine-readable medium claim 16 , wherein the additional Pod is configured to send traffic to external network via the external router.
20 . The non-transitory machine-readable medium claim 16 , wherein the Kubernete cluster comprises a Kubernete control component configured to send the notification.