Load balancing method, system, device and medium for cluster

Abstract

The application discloses a cluster load balancing method, system, device and computer readable storage medium, the cluster load balancing method comprises the following steps: controlling a global configuration module to acquire parameter information of each load balancing control end corresponding to a cluster, and controlling the global configuration module to send the parameter information to a linkage module; controlling the linkage module to listen to changes of each container in the cluster; when the container in the cluster changes, controlling the linkage module to create an interface according to the parameter information and state change information corresponding to the container whose state changes, and sending interface information of the interface to the load balancing control end. The application avoids compatibility problems between load balancing control ends provided by different manufacturers.

Description

Technical Field

[0001] This invention relates to the field of load balancing technology, and in particular to a load balancing method, system, device, and computer-readable storage medium for a cluster. Background Technology

[0002] Existing Kubernetes clusters use a Controller driver engine as a proxy to exchange information between the Kubernetes cluster and the load balancer. Because different load balancers have different focuses—for example, some prioritize security, while others prioritize concurrency—it's necessary to use load balancers from different vendors to achieve the desired load balancing effect. Since the Controller driver engines are provided by various vendors, each engine uses specific requirements such as labels, annotations, and configuration maps to ensure compatibility with its corresponding load balancer. Therefore, compatibility between different Controller driver engines is poor. When adding a new load balancer, a separate Controller driver engine needs to be deployed. Vendors define dozens, even nearly a thousand, annotations, each representing a load balancing characteristic. For the Kubernetes cluster to use these characteristics, each deployment adjustment requires selecting from these hundreds or thousands of annotations, and then calling the Controller driver engine. This call process involves calling these hundreds or thousands of combinations, resulting in very complex call relationships. Summary of the Invention

[0003] The main objective of this invention is to provide a load balancing method, system, device, and computer-readable storage medium for clusters, aiming to solve the technical problem of poor compatibility between various controller driver engines in the process of implementing load balancing in existing Kubernetes clusters, which leads to complex controller driver engine call relationships when deploying and adjusting Kubernetes clusters.

[0004] To achieve the above objectives, the present invention provides a load balancing method for a cluster, comprising the following steps:

[0005] The global configuration module obtains parameter information from each load balancer control terminal corresponding to the cluster, and controls the global configuration module to send the parameter information to the linkage module.

[0006] The control and linkage module monitors changes in each container of the cluster;

[0007] When a container in the cluster changes, the control linkage module creates an interface based on the parameter information and the state change information of the container whose state has changed, and sends the interface information of the interface to the load balancer control terminal.

[0008] Optionally, the step of controlling the global configuration module to obtain parameter information of each load balancer control terminal corresponding to the cluster, and controlling the global configuration module to send the parameter information to the linkage module, includes:

[0009] The global configuration module controls the acquisition of the interface key information and load balancer tag information of each load balancer control terminal in the cluster.

[0010] The global configuration module is controlled to send the interface key information and load balancing tag information to the linkage module.

[0011] Optionally, the step of controlling the linkage module to create an interface based on the parameter information and the state change information corresponding to the container whose state has changed, and sending the interface information of the interface to the load balancing control terminal, includes:

[0012] The linkage module is controlled to acquire the state change information corresponding to the container whose state has changed;

[0013] The control module creates an interface based on the interface key information and the state change information;

[0014] The control linkage module sends the interface information of the interface to the load balancing control terminal corresponding to the container whose state has changed.

[0015] Optionally, the step of controlling the linkage module to send the interface information of the interface to the load balancing control terminal corresponding to the container whose state has changed includes:

[0016] The control linkage module generates interface information for the interface that conforms to the dynamic parameter format based on the dynamic parameter format in the interface key information and the state change information.

[0017] The interface information of the interface is sent to the load balancing control terminal corresponding to the container whose state has changed.

[0018] Optionally, the interface information includes at least the registration URL, request method, request headers, and status change information.

[0019] Optionally, the step of the control linkage module monitoring changes in each container in the cluster includes:

[0020] The control and linkage module monitors the IP address, port information, load balancing tenant label, cluster name, and container status of each container in the cluster.

[0021] Optionally, the step of the control linkage module monitoring changes in each container in the cluster includes:

[0022] The control linkage module calls the List / Watch interface to monitor changes in each container in the cluster.

[0023] Furthermore, to achieve the above objectives, the present invention also provides a cluster system, comprising:

[0024] The global configuration module is used to control the global configuration module to obtain parameter information of each load balancer control terminal corresponding to the cluster, and to control the global configuration module to send the parameter information to the linkage module.

[0025] The linkage module is used to control the linkage module to monitor changes in each container in the cluster;

[0026] When a container in the cluster changes, the control linkage module creates an interface based on the parameter information and the state change information of the container whose state has changed, and sends the interface information of the interface to the load balancing control terminal.

[0027] In addition, to achieve the above objectives, the present invention also provides a cluster device, which includes a memory, a processor, and a cluster load balancing program stored in the memory and executable on the processor. When the cluster load balancing program is executed by the processor, it implements the steps of the cluster load balancing method described above.

[0028] In addition, to achieve the above objectives, the present invention also provides a computer-readable storage medium storing a cluster load balancing program, which, when executed by a processor, implements the steps of the cluster load balancing method described above.

[0029] This invention adds a global configuration module and a linkage module to existing clusters and multiple load balancer control terminals to enable communication between the cluster and the load balancer control terminals. The global configuration module sends parameter information from the load balancer control terminals to a linkage device. This linkage device monitors changes in each container within the cluster. When a state change occurs, it generates an interface based on the parameter information and the dynamic state change, and sends the new mechanism to the corresponding load balancer control terminal. This allows the load balancer control terminal to dynamically register Pod members based on the interface. This avoids compatibility issues between load balancer control terminals from different vendors when using the Controller driver engine. When adjusting the cluster deployment, changes to containers can be addressed by sending interface information to the load balancer control terminal, allowing the load balancer control terminal to adjust synchronously according to the cluster deployment. Attached Figure Description

[0030] Figure 1 This is a schematic diagram of the terminal / device structure of the hardware operating environment involved in the embodiments of the present invention;

[0031] Figure 2 This is a flowchart illustrating the first embodiment of the load balancing method for clusters according to the present invention.

[0032] Figure 3 This is a flowchart illustrating step S30 in the first embodiment of the load balancing method for the cluster of the present invention.

[0033] Figure 4 This is a flowchart illustrating step S10 in the second embodiment of the load balancing method for the cluster of the present invention.

[0034] Figure 5 This is a schematic diagram of the overall architecture of the cluster system of the present invention;

[0035] Figure 6 This is a schematic diagram of the system architecture of the cluster system of the present invention.

[0036] The objectives, features, and advantages of this invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0037] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0038] like Figure 1 As shown, Figure 1 This is a schematic diagram of the terminal structure of the hardware operating environment involved in the embodiments of the present invention.

[0039] In this embodiment of the invention, the terminal is a cluster device.

[0040] like Figure 1As shown, the terminal may include: a processor 1001, such as a CPU; a network interface 1004; a user interface 1003; a memory 1005; and a communication bus 1002. The communication bus 1002 is used to enable communication between these components. The user interface 1003 may include a display screen and an input unit such as a keyboard. Optionally, the user interface 1003 may also include a standard wired interface or a wireless interface. The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface). The memory 1005 may be high-speed RAM or non-volatile memory, such as a disk drive. Optionally, the memory 1005 may also be a storage device independent of the aforementioned processor 1001.

[0041] Optionally, the terminal may also include a camera, RF (Radio Frequency) circuitry, sensors, audio circuitry, a WiFi module, and so on. These sensors may include light sensors, motion sensors, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor. The ambient light sensor can adjust the brightness of the display screen according to the ambient light level, while the proximity sensor can turn off the display screen and / or backlight when the terminal device is moved to the ear. Of course, the terminal device may also be equipped with other sensors such as a gyroscope, barometer, hygrometer, thermometer, and infrared sensor, which will not be elaborated upon here.

[0042] Those skilled in the art will understand that Figure 1 The terminal structure shown does not constitute a limitation on the terminal and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0043] like Figure 1 As shown, the memory 1005, which serves as a computer storage medium, may include an operating system, a network communication module, a user interface module, and a cluster load balancing program.

[0044] exist Figure 1 In the terminal shown, network interface 1004 is mainly used to connect to the backend server and communicate with it; user interface 1003 is mainly used to connect to the client (user terminal) and communicate with it; while processor 1001 can be used to call the cluster load balancing program stored in memory 1005 and perform the following operations:

[0045] The global configuration module obtains parameter information from each load balancer control terminal corresponding to the cluster, and controls the global configuration module to send the parameter information to the linkage module.

[0046] The control and linkage module monitors changes in each container of the cluster;

[0047] When a container in the cluster changes, the control linkage module creates an interface based on the parameter information and the state change information of the container whose state has changed, and sends the interface information of the interface to the load balancer control terminal.

[0048] Reference Figure 2 This invention provides a cluster load balancing method. In a first embodiment of the cluster load balancing method, the cluster load balancing method includes the following steps:

[0049] Step S10: Control the global configuration module to obtain the parameter information of each load balancer control terminal corresponding to the cluster, and control the global configuration module to send the parameter information to the linkage module;

[0050] The load balancing method for clusters provided in this invention is applied to Kubernetes clusters. A Kubernetes cluster consists of multiple hosts, all of which are containerized. Kubernetes (k8s) is an open-source container cluster management system used to manage containerized applications across multiple hosts, making the deployment of containerized applications simple and efficient. Kubernetes provides a complete set of functions including resource scheduling, deployment management, service discovery, scaling up and down, monitoring, and maintenance, becoming a platform for automatic deployment, scaling, and running of application containers across host clusters. Within the Kubernetes cluster, multiple load balancers from different vendors are configured to achieve load balancing throughout the entire Kubernetes cluster operation, for example, increasing throughput, enhancing network data processing capabilities, and improving network flexibility and availability.

[0051] The load balancing control terminal is a load balancing device provided by various manufacturers. This device supports protocols such as IPv6, HTTP (Hypertext Transfer Protocol), and HTTPS (Hypertext Transfer Protocol over Secure Socket Layer), and also supports various load balancing algorithms, such as round-robin, random, source-address hashing, weighted random, and least-connections methods. In this invention, the global configuration module interacts with each load balancing control terminal, and can call each load balancing control terminal through an API (Application Programming Interface). Simultaneously, the global configuration module also interacts with the linkage module, enabling it to collect parameter information such as load balancing flags from each load balancing control terminal and send this parameter information to the linkage device. Those skilled in the art will understand that the parameter information of the load balancing control terminal may specifically include interface key information (API KEY) and load balancing flags. The load balancing flags may specifically include manufacturer information, brand information, and model information of the load balancing control terminal.

[0052] When adding a container (Add Pod) in a Kubernetes cluster, the addition request can be submitted by calling the corresponding interface; when modifying a container (Mod Pod) in a Kubernetes cluster, the modification request can be submitted by calling the corresponding interface; or when deleting a container (Del Pod) in a Kubernetes cluster, the deletion request can be submitted by calling the corresponding interface. At the same time, the global configuration module sends the interface key information to the linkage device to realize API key registration.

[0053] Step S20: Control the linkage module to monitor changes in each container in the cluster;

[0054] Step S20 specifically includes:

[0055] The control linkage module calls the List / Watch interface to monitor changes in each container in the cluster.

[0056] The Kubernetes container orchestration engine itself has List and Watch functionalities. The List function uses a short HTTP connection to access the resource list API, listing resources; the Watch function uses a long HTTP connection to access the resource watch API, listening for resource change events. This allows for monitoring changes to each container in the cluster. Those skilled in the art will understand that, due to the large number of annotations associated with the load balancer, when the number of nodes in a Kubernetes cluster reaches hundreds or thousands, and the number of containers reaches tens of thousands, every change will utilize annotation information. The approximate amount of this information can be obtained using the following formula:

[0057] Information content = Number of node changes × Number of container state changes × Number of annotations;

[0058] In this invention, monitoring changes to each container can be limited to monitoring changes in IP address, port information, load balancing tenant label, cluster name, and Pod state. As shown in the formula above, by monitoring only these five states, the amount of information processing can be significantly reduced, increasing the stability of the Kubernetes cluster. Of course, further monitoring can be conducted on changes to container name, environment variables, running commands, host configuration, network configuration, and data volume configuration. Pod state can specifically be persistent state, configuration state, session state, connection state, and cluster state, etc.

[0059] When a container in the cluster changes, step S30 is executed, controlling the linkage module to create an interface based on the parameter information and the state change information corresponding to the container whose state has changed, and sending the interface information of the interface to the load balancing control terminal.

[0060] Please refer to the following: Figure 3 In one embodiment, step S30 includes:

[0061] Step S31: Control the linkage module to obtain the state change information corresponding to the container whose state has changed;

[0062] The status items monitored in step S20 and the status items obtained in step S31 can be the same or different. For example, in step S20, only the above 5 status items can be monitored. When changes in the above 5 status items are detected, more current information about container-related status items can be obtained in step S31.

[0063] Step S32: Control the linkage module to create an interface based on the interface key information and the state change information;

[0064] Step S33: Control the linkage module to send the interface information of the interface to the load balancing control terminal corresponding to the container whose state has changed.

[0065] Step S33 further includes:

[0066] The control linkage module generates interface information for the interface that conforms to the dynamic parameter format based on the dynamic parameter format in the interface key information and the state change information.

[0067] The interface information of the interface is sent to the load balancing control terminal corresponding to the container whose state has changed.

[0068] The dynamic parameter format is a preset data receiving format template in the load balancer control module. For example, the JSON format includes the IP address (Internet Protocol Address), port name, and status name set sequentially. Different load balancer control modules may use different dynamic parameter formats. Interface information conforming to the dynamic parameter format is generated based on status change information so that the corresponding load balancer control module can recognize it. Using the same linkage module, it can connect to load balancer control modules provided by different vendors. Once the load balancer control module receives the interface information, it can further dynamically register Pod members based on that interface information.

[0069] In this invention, a global configuration module and a linkage module are added to the existing Kubernetes cluster and multiple load balancer control terminals for communication between the Kubernetes cluster and the load balancer control terminals. The global configuration module sends parameter information from the load balancer control terminals to the linkage device. The linkage device monitors changes in each container within the Kubernetes cluster. When a state change occurs, an interface is generated based on the parameter information and the dynamic state change, and the new mechanism is sent to the corresponding load balancer control terminal, allowing the load balancer control terminal to dynamically register Pod members based on the interface. This avoids compatibility issues between load balancer control terminals from different vendors when using the Controlle driver engine. Furthermore, when adjusting the cluster deployment, changes to containers can be addressed by sending interface information to the load balancer control terminal, enabling the load balancer control terminal to adjust synchronously according to the cluster deployment.

[0070] Further, please refer to Figure 4Based on the first embodiment of the present invention described above, a second embodiment of the load balancing method for the cluster of the present invention is proposed. In this embodiment, the refinement of step S10 in the above embodiment, which controls the global configuration module to obtain the parameter information of each load balancing control terminal corresponding to the cluster and controls the global configuration module to send the parameter information to the linkage module, includes:

[0071] Step S11: Control the global configuration module to obtain the interface key information and load balancer tag information corresponding to the cluster.

[0072] Step S12: Control the global configuration module to send the interface key information and load balancing tag information to the linkage module.

[0073] The API key information may include, but is not limited to, the URL (Uniform Resource Locator), request method, request headers, and dynamic parameter format. The URL includes the address of the load balancer and the API URL provided by the load balancer. Request methods include GET, POST, PUT, PATCH, etc. Request headers include authentication method and content mode. The API key information is sent to the linkage device to complete API key registration.

[0074] Those skilled in the art will further understand that, while performing the step of controlling the global configuration module to send the interface key information and load balancing tag information to the linkage module, the method also includes:

[0075] The global configuration module is controlled to send the interface key information and load balancing tag information to the driver module.

[0076] In this invention, the driver module is the Controlle driver engine. The interface key information and load balancing tag information are sent to the driver module to facilitate the Controlle driver engine's invocation.

[0077] Furthermore, it should be noted that, as Figure 5 and Figure 6 As shown, this invention also provides a cluster system, which includes:

[0078] The global configuration module is used to control the global configuration module to obtain parameter information of each load balancer control terminal corresponding to the cluster, and to control the global configuration module to send the parameter information to the linkage module.

[0079] The linkage module is used to control the linkage module to monitor changes in each container in the cluster;

[0080] When a container in the cluster changes, the control linkage module creates an interface based on the parameter information and the state change information of the container whose state has changed, and sends the interface information of the interface to the load balancing control terminal.

[0081] In this invention, a global configuration module and a linkage module are added to the existing Kubernetes cluster and multiple load balancer control terminals for communication between the Kubernetes cluster and the load balancer control terminals. The global configuration module sends parameter information from the load balancer control terminals to the linkage device. The linkage device monitors changes in each container within the Kubernetes cluster. When a state change occurs, an interface is generated based on the parameter information and the dynamic state change, and the new mechanism is sent to the corresponding load balancer control terminal, allowing the load balancer control terminal to dynamically register Pod members based on the interface. This avoids compatibility issues between load balancer control terminals from different vendors when using the Controlle driver engine. Furthermore, when adjusting the cluster deployment, changes to containers can be addressed by sending interface information to the load balancer control terminal, enabling the load balancer control terminal to adjust synchronously according to the cluster deployment.

[0082] Optionally, the global configuration module is also used for:

[0083] Obtain the interface key information and load balancer tag information for each load balancer control terminal in the cluster;

[0084] Send the interface key information and load balancing tag information to the linkage module.

[0085] Optionally, the linkage module is also used for:

[0086] Get the state change information of the container whose state has changed;

[0087] An interface is created based on the interface key information and the state change information;

[0088] The control linkage module sends the interface information of the interface to the load balancing control terminal corresponding to the container whose state has changed.

[0089] Optionally, the linkage module is also used for:

[0090] Based on the dynamic parameter format in the interface key information and the state change information, interface information conforming to the dynamic parameter format is generated for the interface.

[0091] The interface information of the interface is sent to the load balancing control terminal corresponding to the container whose state has changed.

[0092] Optionally, the interface information includes at least the registration URL, request method, request headers, and status change information.

[0093] Optionally, the linkage module is also used for:

[0094] Monitor the IP address, port information, load balancing tenant label, cluster name, and container status of each container in the cluster.

[0095] Optionally, the global configuration module is also used for:

[0096] Optionally, the linkage module is also used for:

[0097] The control linkage module calls the List / Watch interface to monitor changes in each container in the cluster.

[0098] The steps for implementing each functional unit of the cluster system can be referred to in the various embodiments of the load balancing method of the cluster of the present invention, and will not be repeated here.

[0099] Furthermore, the present invention also provides a cluster device, wherein the terminal includes: a memory, a processor, a communication bus, and a cluster load balancing program stored on the memory.

[0100] The communication bus is used to enable communication between the processor and the memory;

[0101] The processor is used to execute the load balancing program of the cluster to implement the steps of the various embodiments of the load balancing method for the cluster described above.

[0102] The present invention also provides a computer-readable storage medium storing one or more programs, which can be executed by one or more processors to implement the steps of the various embodiments of the load balancing method for the above-described cluster.

[0103] The specific implementation of the computer-readable storage medium of the present invention is basically the same as the various embodiments of the load balancing method for the cluster described above, and will not be repeated here.

[0104] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.

[0105] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0106] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0107] The above are merely preferred embodiments of the present invention and do not limit the scope of the patent. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.

Claims

1. A load balancing method for a cluster, characterized in that, The load balancing method for the cluster includes the following steps: The global configuration module obtains parameter information from each load balancer control terminal corresponding to the cluster, and controls the global configuration module to send the parameter information to the linkage module. The control and linkage module monitors changes in each container of the cluster; When a container in the cluster changes, the control linkage module creates an interface based on the parameter information and the state change information of the container whose state has changed, and sends the interface information of the interface to the load balancer control terminal. The step of controlling the global configuration module to obtain parameter information of each load balancer control terminal corresponding to the cluster and controlling the global configuration module to send the parameter information to the linkage module includes: The global configuration module controls the acquisition of the interface key information and load balancer tag information of each load balancer control terminal corresponding to the cluster. The load balancer tag information includes the manufacturer information, brand information and model information of the load balancer control terminal. The global configuration module is controlled to send the interface key information and load balancing tag information to the linkage module.

2. The cluster load balancing method as described in claim 1, characterized in that, The step of controlling the linkage module to create an interface based on the parameter information and the state change information corresponding to the container whose state has changed, and sending the interface information of the interface to the load balancing control terminal, includes: The linkage module is controlled to acquire the state change information corresponding to the container whose state has changed; The control module creates an interface based on the interface key information and the state change information; The control linkage module sends the interface information of the interface to the load balancing control terminal corresponding to the container whose state has changed.

3. The cluster load balancing method as described in claim 2, characterized in that, The step of controlling the linkage module to send the interface information of the interface to the load balancing control terminal corresponding to the container whose state has changed includes: The control linkage module generates interface information for the interface that conforms to the dynamic parameter format based on the dynamic parameter format in the interface key information and the state change information. The control linkage module sends the interface information of the interface to the load balancing control terminal corresponding to the container whose state has changed.

4. The load balancing method for a cluster as described in any one of claims 1 to 3, characterized in that, The interface information includes at least the registration URL, request method, request headers, and status change information.

5. The load balancing method for a cluster as described in any one of claims 1 to 3, characterized in that, The steps of the control linkage module monitoring changes in each container of the cluster include: The control and linkage module monitors the IP address, port information, load balancing tenant label, cluster name, and container status of each container in the cluster.

6. The load balancing method for the cluster as described in any one of claims 1 to 3, characterized in that, The steps of the control linkage module monitoring changes in each container of the cluster include: The control linkage module calls the List / Watch interface to monitor changes in each container in the cluster.

7. A cluster system, characterized in that, The cluster system includes: A global configuration module is used to control the global configuration module to obtain parameter information of each load balancing control terminal corresponding to the cluster, and to control the global configuration module to send the parameter information to the linkage module. The global configuration module is also used to obtain the interface key information and load balancing tag information of each load balancing control terminal corresponding to the cluster, wherein the load balancing tag information includes the manufacturer information, brand information, and model information of the load balancing control terminal; and to send the interface key information and load balancing tag information to the linkage module. The linkage module is used to control the linkage module to monitor changes in each container in the cluster; When a container in the cluster changes, the control linkage module creates an interface based on the parameter information and the state change information of the container whose state has changed, and sends the interface information of the interface to the load balancing control terminal.

8. A cluster device, characterized in that, The cluster device includes: a memory, a processor, and a cluster load balancing program stored in the memory and executable on the processor. When the cluster load balancing program is executed by the processor, it implements the steps of the cluster load balancing method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a cluster load balancing program, which, when executed by a processor, implements the steps of the cluster load balancing method as described in any one of claims 1 to 6.

Images