WO2023184925A1 - Load balancer and implementation method therefor, load balancing method, and gateway system - Google Patents

Abstract

The present application discloses a load balancer and an implementation method therefor, a load balancing method, and a gateway system. The implementation method for a load balancer comprises: a proxy agent controller sends, to a load balancing gateway proxy on a target host, a creation request comprising creation configuration information, wherein the target host refers to any one of a plurality of hosts; the load balancing gateway proxy creates a proxy envoy container according to the creation configuration information, generates and mounts a configuration file of the proxy envoy container, and starts the proxy envoy container by using the network of a Docker container engine; the proxy envoy container pulls up the latest target service configuration on the basis of an address of a configuration service XDS server in the configuration file for carrying out load balancing on a request of an application.

Description

Load balancer and its implementation method, load balancing method, gateway system

This application requires the priority of the Chinese patent application submitted to the China Patent Office on March 29, 2022, with the application number 202210317360.9, and the invention name is "Load balancer and its implementation method, load balancing method, gateway system", all of which The contents are incorporated into this application by reference.

Technical field

This application relates to the field of load balancing technology, and in particular to a load balancer and its implementation method, a load balancing method, and a gateway system.

Background technique

In order to provide network data processing capabilities, increase throughput, improve network availability and flexibility, current systems usually load balance access requests.

Currently, for pulling images from the mirror warehouse, LVS+keepalived is usually used on the front end to achieve automatic switching of virtual IPs, and Nginx or HAProxy is used on the back end to achieve layer 7 load balancing, so that traffic and access load balancing can be performed on the back-end nodes. .

However, load balancing implemented using Nginx or HAProxy is configured based on files. Therefore, when nodes are added to the backend or there are other convenient updates, the configuration file must be modified or generated, and then the configuration file must be reloaded to take effect. The backend also needs to be restarted, so it is very inconvenient.

Contents of the invention

Based on the shortcomings of the above-mentioned existing technologies, this application provides a load balancer and its implementation method, a load balancing method, and a gateway system to solve the existing problem of being too cumbersome when making changes.

In order to achieve the above objectives, this application provides the following technical solutions:

The first aspect of this application provides a method for implementing a load balancer, which is applied to a gateway system. The gateway system at least includes a gateway control service and multiple hosts. The gateway control service includes an agent controller Agent Controller and a configuration service XDS. server, each host is deployed with a container engine Docker and a load balancing gateway agent. The implementation method of the load balancer includes:

The agent controller Agent Controller sends a creation request to the load balancing gateway agent on the target host; wherein the creation request includes creation configuration information; the target host refers to any one of the multiple hosts;

The load balancing gateway proxy on the target host creates a proxy container envoy container based on the creation configuration information, and generates and mounts the configuration file of the proxy container envoy container;

The load balancing gateway proxy service uses the network of the container engine Docker to start the proxy container envoy container;

The proxy container envoy container pulls the latest target service configuration from the configuration service XDS server based on the address of the configuration service XDS server in the configuration file for load balancing application requests.

Optionally, in the above load balancer implementation method, the gateway system also includes a high availability service keepalived. After the agent controller Agent Controller sends a creation request to the load balancing gateway agent on the target host, it also include:

The load balancing gateway agent on the target host calls the high-availability service keepalived to generate corresponding IPs for the target host and other backup hosts.

Optionally, in the above load balancer implementation method, before the load balancing gateway proxy service uses the network of the container engine Docker to start the proxy container envoy container, it also includes:

The container engine Docker responds to the network creation operation and creates the MACVLAN network of the container engine Docker for the proxy container envoy container;

Among them, the load balancing gateway proxy service uses the network of the container engine Docker to start the proxy container envoy container, including:

The load balancing gateway proxy service calls the MACVLAN network of the container engine Docker to allocate a network address to the proxy container envoy container, and starts the proxy container envoy container based on the network address.

Optionally, in the above implementation method of the load balancer, the proxy container envoy container pulls the latest target from the configuration service XDS server based on the address of the configuration service XDS server in the configuration file. Service configuration, used to load balance the application's requests, including:

The proxy container envoy container monitors the address of the configuration service XDS server in the configuration file through the corresponding discovery mechanism; wherein the discovery mechanism includes monitoring dynamic discovery, cluster dynamic discovery, service endpoint dynamic discovery, and routing rule dynamics. Discover;

When monitoring the target service configuration update at any address of the configuration service XDS server in the configuration file, the proxy container envoy container pulls the latest target service configuration for requests to the application. Perform load balancing.

The second aspect of this application provides a load balancing method, which is applied to a load balancer. The load balancer is a proxy container envoy container created in the gateway system. The load balancing method includes:

Get the request sent by the application;

The request is load balanced based on the latest target service configuration pulled from the configuration service XDS server of the gateway system; wherein the target service configuration is based on the proxy container envoy container after it is started. The address of the configuration service XDS server in the configuration file is pulled from the configuration service XDS server; the configuration file of the proxy container envoy container is created by the load balancing gateway proxy on the target host based on the creation configuration information in the creation request. When the proxy container envoy container is generated and mounted according to the creation configuration information; the target host refers to any one of the multiple hosts; the creation request is controlled by the proxy in the gateway system Sent by Agent Controller; the proxy container envoy container is started by the load balancing gateway proxy service using the network of the container engine Docker in the gateway system.

The third aspect of this application provides a gateway system, including:

Gateway control services and multiple hosts;

The gateway control service includes the agent controller Agent Controller and the configuration service XDS server;

Each host is deployed with the container engine Docker and the load balancing gateway agent;

The agent controller Agent Controller is used to send a creation request to the load balancing gateway agent on the target host; wherein the creation request includes creation configuration information; the target host refers to any one of the multiple hosts tower;

The load balancing gateway proxy is used to create a proxy container envoy container based on the creation configuration information, generate and mount the configuration file of the proxy container envoy container, and use the network of the container engine Docker to start the proxy container envoy container; wherein, after startup, the proxy container envoy container pulls the latest target service configuration from the configuration service XDS server based on the address of the configuration service XDS server in the configuration file, which is used to configure the application The requests are load balanced.

Optionally, the gateway system provided above also includes:

The high availability service keepalived is used to generate corresponding IPs for the target host and other backup hosts.

Optionally, in the gateway system provided above, the container engine Docker is also used for:

In response to the network creation operation, create the MACVLAN network of the container engine Docker for the proxy container envoy container;

Wherein, when the load balancing gateway proxy service uses the network of the container engine Docker to start the proxy container envoy container, it is used for:

Call the MACVLAN network of the container engine Docker to allocate a network address to the proxy container envoy container, and start the proxy container envoy container based on the network address.

Optionally, in the gateway system provided above, the proxy container envoy container pulls the latest target service configuration from the configuration service XDS server based on the address of the configuration service XDS server in the configuration file, When used to load balance an application's requests, it is used to:

Monitor the address of the configuration service XDS server in the configuration file through the corresponding discovery mechanism; wherein the discovery mechanism includes monitoring dynamic discovery, cluster dynamic discovery, service endpoint dynamic discovery, and routing rule dynamic discovery;

When the target service configuration update in any address of the configuration service XDS server in the configuration file is monitored, the latest target service configuration is pulled for load balancing of application requests.

The fourth aspect of this application provides a load balancer. The load balancer is a proxy container envoy container created in the gateway system. The load balancer includes:

Acquisition unit, used to obtain requests sent by the application;

A load balancing unit, configured to load balance the request based on the latest target service configuration pulled from the configuration service XDS server of the gateway system; wherein the target service configuration is configured by the proxy container envoy After the container is started, it is pulled from the configuration service XDS server based on the address of the configuration service XDS server in its configuration file; the configuration file of the proxy container envoy container is created by the load balancing gateway proxy on the target host according to the creation request When creating the proxy container envoy container, it is generated and mounted according to the creation configuration information; the target host refers to any one of the multiple hosts; when the creation request is made, the gateway system The agent controller in Agent Controller sends; the agent container envoy container is started by the network of the load balancing gateway agent service using the container engine Docker in the gateway system.

This application provides a load balancer implementation method, which is applied to a gateway system. The gateway system at least includes a gateway control service and multiple hosts. The gateway control service includes an agent controller Agent Controller and a configuration service XDS server. Each host is deployed There is the container engine Docker and the load balancing gateway agent. When a load balancer needs to be created, the Agent Controller sends a creation request to the load balancing gateway agent on the target host. The creation request includes creation configuration information, and the target host refers to any one of the multiple hosts. The load balancing gateway proxy on the target host creates the proxy container envoy container based on the creation configuration information, generates and mounts the configuration file of the proxy container envoy container, and then uses the network of the container engine Docker to start the proxy container envoy container. The started proxy container envoy container pulls the latest target service configuration from the configuration service XDS server based on the address of the configuration service XDS server in the configuration file, which is used to load balance application requests. Therefore, when adding new nodes or making other changes, you only need to perform dynamic configuration through the configuration service XDS server, and the configuration can be pulled for load balancing without restarting.

Description of drawings

In order to explain the embodiments of the present application or the technical solutions in the prior art more clearly, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings in the following description are only These are embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on the provided drawings without exerting creative efforts.

Figure 1 is a schematic architectural diagram of a gateway system provided by an embodiment of the present application;

Figure 2 is a flow chart of a load balancer implementation method provided by an embodiment of the present application;

Figure 3 is a flow chart of another load balancer implementation method provided by another embodiment of the present application;

Figure 4 is a flow chart of a load balancing method provided by another embodiment of the present application;

Figure 5 is a schematic structural diagram of a load balancer provided by another embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the scope of protection of this application.

In this application, relational terms such as first, second, etc. are only used to distinguish one entity or operation from another entity or operation and do not necessarily require or imply the existence of any such entity or operation. an actual relationship or sequence. Furthermore, the terms "comprises," "comprises," or any other variation thereof are intended to cover a non-exclusive inclusion, such that a process, method, article or apparatus including a list of elements includes not only those elements, but also those not expressly listed Other elements, or elements inherent to the process, method, article or equipment. Without further limitation, an element defined by the statement "comprises a..." does not exclude the presence of additional identical elements in a process, method, article, or apparatus that includes the stated element.

This application provides a method for implementing a load balancer, which is applied to a gateway system. That is, the load balancer needs to be implemented through the gateway system to solve the existing problem of being too cumbersome when making changes.

Optionally, in order to implement the load balancer implementation method provided in the embodiment of this application, another embodiment of this application provides a gateway system, as shown in Figure 1, including:

Gateway controls services as well as multiple hosts.

Gateway control services include agent controller Agent Controller and configuration service XDS server.

Each host is deployed with the container engine Docker and the load balancing gateway agent.

Agent Controller Agent Controller is used to send a create request to the load balancing gateway agent on the target host. Among them, the creation request includes creation configuration information. The target host refers to any one of multiple hosts.

The load balancing gateway proxy is used to create a proxy container envoy container based on the creation configuration information, generate and mount the configuration file of the proxy container envoy container, and use the network of the container engine Docker to start the proxy container envoy container.

Among them, the proxy container envoy container pulls the latest target service configuration from the configuration service XDS server based on the address of the configuration service XDS server in the configuration file after startup, which is used to load balance application requests.

Optionally, the gateway system provided by another embodiment of the present application also includes:

The high-availability service keepalived is used to generate corresponding IPs for the target host and other backup hosts.

Optionally, in the gateway system provided by another embodiment of this application, the container engine Docker is also used for:

In response to the network creation operation, create the MACVLAN network of the container engine Docker for the proxy container envoy container.

Among them, when the load balancing gateway proxy service in the embodiment of this application uses the network of the container engine Docker to start the proxy container envoy container, it is used for:

Call the MACVLAN network of the container engine Docker to assign a network address to the proxy container envoy container, and start the proxy container envoy container based on the network address.

Optionally, in the gateway system provided by another embodiment of the present application, the proxy container envoy container pulls the latest target service configuration from the configuration service XDS server based on the address of the configuration service XDS server in the configuration file for use in When application requests are load balanced, they are used to:

Monitor the address of the configuration service XDS server in the configuration file through the corresponding discovery mechanism. Among them, the discovery mechanism includes dynamic discovery of listeners, dynamic discovery of clusters, dynamic discovery of service endpoints, and dynamic discovery of routing rules.

When the target service configuration update in any address of the configuration service XDS server in the configuration file is monitored, the latest target service configuration is pulled for load balancing of application requests.

Based on the gateway system provided above, embodiments of the present application provide a load balancer implementation method, which is specifically applied to the above gateway system. According to the above, it can be seen that the gateway system at least includes a gateway control service and multiple hosts. The gateway control service includes Agent Controller and configuration service XDS server. Each host is deployed with container engine Docker and load balancing gateway agent.

As shown in Figure 2, the implementation method of the load balancer provided by the embodiment of this application includes the following steps:

S201. The agent controller Agent Controller sends a creation request to the load balancing gateway agent on the target host.

Among them, the creation request includes creation configuration information. The target host refers to any one of multiple hosts.

Specifically, when a load balancer needs to be created, developers can create configuration information based on the created demand configuration, including the corresponding configuration information about the load balancer, and then send it to the load balancing gateway on a host through the Agent Controller. The agent sends a create request that includes this configuration information to request the load balancing gateway agent to create the load balancer. This enables dynamic creation of containers.

It should be noted that in the embodiment of this application, the proxy container envoy container is used to implement a load balancer (software gateway), so the load balancer in the embodiment of this application is the proxy container envoy container. The Envoy proxy itself supports dynamic routing rules, and can dynamically start listening ports without restarting. It also supports traffic mirroring, and can dynamically update routing rules, backend addresses, etc. through the XDS protocol.

S202. The load balancing gateway proxy on the target host creates the proxy container envoy container based on the creation configuration information, and generates and mounts the configuration file of the proxy container envoy container.

Optionally, after receiving the creation request, the load balancing gateway proxy on the target host can create multiple proxy container envoy containers based on the creation configuration information on multiple hosts including the target host. Then generate the configuration file of the proxy container envoy container based on the created configuration information. The configuration file includes the address of the configuration service XDS server to be monitored by the proxy container envoy container, so that the proxy container envoy container can monitor dynamic discovery, cluster dynamic discovery, and server-side dynamics. Discovery and dynamic discovery of routing rules, etc., that is, it can monitor updates of the target service configuration to pull the latest target service configuration for load balancing.

Optionally, in order to better achieve high availability, the gateway system can further include a high-availability service keepalived. Correspondingly, in the embodiment of the present application, after executing step S201, while executing step S202, it may further include:

The load balancing gateway agent on the target host calls the high-availability service keepalived to generate corresponding IPs for the target host and other backup hosts.

Among them, the backup host refers to the host that has also created the same proxy container envoy container as the target host. It should be noted that the way the high-availability service keepalived implements high availability is an existing technology, so it will not be described again here.

S203. The load balancing gateway proxy service uses the network of the container engine Docker to start the proxy container envoy container.

Specifically, the Docker network is dynamically created through the container engine Docker. Specifically, it can be a three-layer network Docker MACVLAN or a two-layer network Docker IPVLAN, and then the proxy container envoy container is associated with the created network, thereby starting the proxy container envoy container.

S204. The proxy container envoy container pulls the latest target service configuration from the configuration service XDS server based on the address of the configuration service XDS server in the configuration file, which is used to load balance application requests.

Optionally, after the proxy container envoy container is started for the first time, the target service configuration can be pulled from the configuration service XDS server based on the address of the configuration service XDS server in the configuration file. Among them, the target service configuration may include discovery-related service configurations such as monitoring dynamic discovery, cluster dynamic discovery, service endpoint dynamic discovery, routing rule dynamic discovery, etc.

Optionally, the subsequent proxy container envoy container can periodically pull the target service configuration from the configuration service XDS server based on the address of the configuration service XDS server in the configuration file. It can also be the address of the configuration service XDS server in the configuration file that is monitored in real time. When it is found that there is a configuration update under the monitored address, the updated target service configuration is pulled.

Specifically, after the proxy container envoy container pulls the target service configuration, since the target service configuration includes routing rules, load balancing rules, etc., when it receives a request sent by the application, it can based on the routing rules, load balancing rules, etc. The target service configuration load balances the request.

The implementation method of a load balancer provided by the embodiment of this application is applied to a gateway system. The gateway system at least includes a gateway control service and multiple hosts. The gateway control service includes an agent controller Agent Controller and a configuration service XDS server. Each server The host is deployed with the container engine Docker and the load balancing gateway agent. When a load balancer needs to be created, the Agent Controller sends a creation request to the load balancing gateway agent on the target host. The creation request includes creation configuration information, and the target host refers to any one of the multiple hosts. The load balancing gateway proxy on the target host creates the proxy container envoy container based on the creation configuration information, generates and mounts the configuration file of the proxy container envoy container, and then uses the network of the container engine Docker to start the proxy container envoy container. The started proxy container envoy container pulls the latest target service configuration from the configuration service XDS server based on the address of the configuration service XDS server in the configuration file, which is used to load balance application requests. Therefore, when adding new nodes or making other changes, you only need to perform dynamic configuration through the configuration service XDS server, and the configuration can be pulled for load balancing without restarting.

Another embodiment of the present application provides another load balancer implementation method, which is also applied to the above-mentioned gateway system. As shown in Figure 3, the implementation method of the load balancer provided by the embodiment of this application includes the following steps:

S301. The agent controller Agent Controller sends a creation request to the load balancing gateway agent on the target host.

Among them, the creation request includes creation configuration information. The target host refers to any one of multiple hosts.

It should be noted that in the embodiment of the present application, the specific implementation of step S301 may refer to the corresponding steps in the above method embodiment, and will not be described again here.

S302. The load balancing gateway proxy on the target host creates the proxy container envoy container based on the creation configuration information, and generates and mounts the configuration file of the proxy container envoy container.

It should be noted that in the embodiment of the present application, the specific implementation of step S301 may refer to the corresponding steps in the above method embodiment, and will not be described again here.

S303. The container engine Docker responds to the network creation operation and creates the MACVLAN network of the container engine Docker for the proxy container envoy container.

In the embodiment of this application, the proxy container envoy container is started through the dynamically created MACVLAN network of Docker. Of course, other networks can also be used.

S304. The load balancing gateway proxy service calls the MACVLAN network of the container engine Docker to allocate a network address to the proxy container envoy container, and starts the proxy container envoy container based on the network address.

S305. The proxy container envoy container monitors the address of the configuration service XDS server in the configuration file through the corresponding discovery mechanism.

Among them, the discovery mechanism includes dynamic discovery of listeners, dynamic discovery of clusters, dynamic discovery of service endpoints, and dynamic discovery of routing rules.

In the embodiment of this application, the address of the configuration service XDS server in the configuration file is monitored through the discovery mechanism, so that when a file update occurs under the configured address, the latest target service configuration can be pulled in time for load balancing.

S306. When listening to the target service configuration update at any address of the configuration service XDS server in the configuration file, the proxy container envoy container pulls the latest target service configuration for load balancing of application requests.

Another embodiment of the present application provides a load balancing method, which can be applied to the load balancer implemented by the load balancer implementation method provided in any of the above embodiments. According to the above, in the embodiment of this application, the load balancer is the proxy container envoy container created in the gateway system. As shown in Figure 4, the load balancing method provided by the embodiment of the present application includes:

S401. Obtain the request sent by the application.

Specifically, the user can initiate a request to the backend through the application. At this time, the proxy container envoy container acting as the load balancer will obtain the request sent by the application, and then perform step S402.

S402. Load balance the request based on the latest target service configuration pulled from the configuration service XDS server of the gateway system.

Among them, the target service configuration specifically includes routing rules and load balancing rules. Therefore, the proxy container envoy container performs routing and forwarding based on the pulled target service configuration, that is, load balancing.

Among them, the target service configuration is pulled from the configuration service XDS server by the proxy container envoy container based on the address of the configuration service XDS server in its configuration file after startup. The configuration file of the proxy container envoy container is generated and mounted based on the creation configuration information when the proxy container envoy container is created by the load balancing gateway proxy on the target host based on the creation configuration information in the creation request. The target host refers to any one of multiple hosts. The creation request is sent by the Agent Controller in the gateway system. The proxy container envoy container is started by the load balancing gateway proxy service using the Docker container engine in the gateway system.

It should be noted that according to the specific implementation method of the proxy container envoy container, the implementation method of the load balancer can be provided by referring to any of the above method embodiments, which will not be described again here.

The embodiment of this application provides a load balancer, which is a proxy container envoy container created in the gateway system. As shown in Figure 5, the load balancer provided by this embodiment of the application includes:

The obtaining unit 501 is used to obtain the request sent by the application program.

The load balancing unit 502 is configured to load balance the request based on the latest target service configuration pulled from the configuration service XDS server of the gateway system.

Among them, the target service configuration is pulled from the configuration service XDS server by the proxy container envoy container based on the address of the configuration service XDS server in its configuration file after startup. The configuration file of the proxy container envoy container is generated and mounted based on the creation configuration information when the proxy container envoy container is created by the load balancing gateway proxy on the target host based on the creation configuration information in the creation request. The target host refers to any one of multiple hosts. The creation request is sent by the Agent Controller in the gateway system. The proxy container envoy container is started by the load balancing gateway proxy service using the Docker container engine in the gateway system.

Those skilled in the art may further realize that the units and algorithm steps of each example described in connection with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of both. In order to clearly illustrate the possible functions of hardware and software, Interchangeability, in the above description, the composition and steps of each example have been generally described according to functions. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered beyond the scope of this application.

The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be practiced in other embodiments without departing from the spirit or scope of the application. Therefore, the present application is not to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (10)

1. A load balancer implementation method, characterized in that it is applied to a gateway system. The gateway system at least includes a gateway control service and multiple hosts. The gateway control service includes an agent controller Agent Controller and a configuration service XDS server. Each The host is deployed with a container engine Docker and a load balancing gateway agent. The implementation method of the load balancer includes:

   The agent controller Agent Controller sends a creation request to the load balancing gateway agent on the target host; wherein the creation request includes creation configuration information; the target host refers to any one of the multiple hosts;

   The load balancing gateway proxy on the target host creates a proxy container envoy container based on the creation configuration information, and generates and mounts the configuration file of the proxy container envoy container;

   The load balancing gateway proxy service uses the network of the container engine Docker to start the proxy container envoy container;

   The proxy container envoy container pulls the latest target service configuration from the configuration service XDS server based on the address of the configuration service XDS server in the configuration file for load balancing application requests.
2. The method according to claim 1, characterized in that the gateway system also includes a high-availability service keepalived. After the agent controller Agent Controller sends a creation request to the load balancing gateway agent on the target host, it also includes:

   The load balancing gateway agent on the target host calls the high-availability service keepalived to generate corresponding IPs for the target host and other backup hosts.
3. The method according to claim 1, characterized in that before the load balancing gateway proxy service uses the network of the container engine Docker to start the proxy container envoy container, it also includes:

   The container engine Docker responds to the network creation operation and creates the MACVLAN network of the container engine Docker for the proxy container envoy container;

   Among them, the load balancing gateway proxy service uses the network of the container engine Docker to start the proxy container envoy container, including:

   The load balancing gateway proxy service calls the MACVLAN network of the container engine Docker to allocate a network address to the proxy container envoy container, and starts the proxy container envoy container based on the network address.
4. The method according to claim 1, characterized in that the proxy container envoy container pulls the latest target service configuration from the configuration service XDS server based on the address of the configuration service XDS server in the configuration file. , used to load balance application requests, including:

   The proxy container envoy container monitors the address of the configuration service XDS server in the configuration file through the corresponding discovery mechanism; wherein the discovery mechanism includes monitoring dynamic discovery, cluster dynamic discovery, service endpoint dynamic discovery, and routing rule dynamics. Discover;

   When monitoring the target service configuration update at any address of the configuration service XDS server in the configuration file, the proxy container envoy container pulls the latest target service configuration for requests to the application. Perform load balancing.
5. A load balancing method, characterized in that it is applied to a load balancer, and the load balancer is a proxy container envoy container created in the gateway system. The load balancing method includes:

   Get the request sent by the application;

   The request is load balanced based on the latest target service configuration pulled from the configuration service XDS server of the gateway system; wherein the target service configuration is based on the proxy container envoy container after it is started. The address of the configuration service XDS server in the configuration file is pulled from the configuration service XDS server; the configuration file of the proxy container envoy container is created by the load balancing gateway proxy on the target host based on the creation configuration information in the creation request. When the proxy container envoy container is generated and mounted according to the creation configuration information; the target host refers to any one of the multiple hosts; the creation request is controlled by the proxy in the gateway system Sent by Agent Controller; the proxy container envoy container is started by the load balancing gateway proxy service using the network of the container engine Docker in the gateway system.
6. A gateway system, characterized by including:

   Gateway control services and multiple hosts;

   The gateway control service includes agent controller Agent Controller and configuration service XDS server;

   Each host is deployed with the container engine Docker and the load balancing gateway agent;

   The agent controller Agent Controller is used to send a creation request to the load balancing gateway agent on the target host; wherein the creation request includes creation configuration information; the target host refers to any one of the multiple hosts tower;

   The load balancing gateway proxy is used to create a proxy container envoy container based on the creation configuration information, generate and mount the configuration file of the proxy container envoy container, and use the network of the container engine Docker to start the proxy container envoy container; wherein, after startup, the proxy container envoy container pulls the latest target service configuration from the configuration service XDS server based on the address of the configuration service XDS server in the configuration file, which is used to configure the application The requests are load balanced.
7. The gateway system according to claim 6, further comprising:

   The high availability service keepalived is used to generate corresponding IPs for the target host and other backup hosts.
8. The gateway system according to claim 6, characterized in that the container engine Docker is also used for:

   In response to the network creation operation, create the MACVLAN network of the container engine Docker for the proxy container envoy container;

   Wherein, when the load balancing gateway proxy service uses the network of the container engine Docker to start the proxy container envoy container, it is used for:

   Call the MACVLAN network of the container engine Docker to allocate a network address to the proxy container envoy container, and start the proxy container envoy container based on the network address.
9. The gateway system according to claim 6, wherein the proxy container envoy container pulls the latest target service from the configuration service XDS server based on the address of the configuration service XDS server in the configuration file. Configuration, used when load balancing requests to an application, is used to:

   Monitor the address of the configuration service XDS server in the configuration file through the corresponding discovery mechanism; wherein the discovery mechanism includes monitoring dynamic discovery, cluster dynamic discovery, service endpoint dynamic discovery, and routing rule dynamic discovery;

   When the target service configuration update in any address of the configuration service XDS server in the configuration file is monitored, the latest target service configuration is pulled for load balancing of application requests.
10. A load balancer, characterized in that the load balancer is a proxy container envoy container created in the gateway system, and the load balancer includes:

    Acquisition unit, used to obtain requests sent by the application;

    A load balancing unit, configured to load balance the request based on the latest target service configuration pulled from the configuration service XDS server of the gateway system; wherein the target service configuration is configured by the proxy container envoy After the container is started, it is pulled from the configuration service XDS server based on the address of the configuration service XDS server in its configuration file; the configuration file of the proxy container envoy container is created by the load balancing gateway proxy on the target host according to the creation request When creating the proxy container envoy container, it is generated and mounted according to the creation configuration information; the target host refers to any one of the multiple hosts; when the creation request is made, the gateway system The agent controller in Agent Controller sends; the agent container envoy container is started by the network of the load balancing gateway agent service using the container engine Docker in the gateway system.

Images