Watch resource optimization method and system for k8s gateway service

Abstract

Provided in the present invention are a watch resource optimization method, system and apparatus for a Kubernetes (K8s) gateway service. The method comprises: initializing a K8s cluster, and reporting a minimum resource version number of a cache resource of a Kube-Apiserver instance; and on the basis of the minimum resource version number, a gateway service component KubeGateway selecting a rear-end Apiserver instance. In the present invention, a minimum resource version number cached by a Kube-Apiserver is cached by means of a gateway service component KubeGateway, and is used as a decision-making basis in a proxy watch monitoring request stage to optimize a watch resource, thereby reducing the retry request pressure of a gateway service in respect of a rear-end instance, improving the performance of Apiserver, and reducing the pressure of an Apiserver service; and a minimum version number cache solution can be used as a decision-making basis of a load balancing algorithm, so as to provide a better decision-making capability.

Description

A K8s gateway service Watch resource optimization method and system

[0001] This application claims priority to Chinese patent application number CN202311664068.5, filed on December 6, 2023, entitled “A K8s Gateway Service Watch Resource Optimization Method and System,” the entire text of which is hereby incorporated by reference. Technical Field

[0002] The present invention relates to the technical field of Kubernetes container orchestration and gateway proxy technology, and in particular to a K8s gateway service Watch resource optimization method and system. Background Art

[0003] In the process of building large-scale Kubernetes (K8s) clusters, the KubeGateway gateway service is positioned to provide stable traffic management services for the massive clusters it represents.

[0004] Currently, in actual production practice, the KubeGateway gateway service uses a service discovery-based approach to select a backend instance for proxy requests. It selects the backend Kube-Apiserver instance in a round-robin manner and proxies the request to the selected Kube-Apiserver instance, as shown in Figure 1.

[0005] However, because the resource versions (i.e., resourceVersion) maintained in the local caches of multiple Kube-Apiserver replicas are inconsistent, the minimum resource versions cached in each Kube-Apiserver are different. As a result, when a client initiates a Watch request, if the request is proxied to an incompatible instance, a "too old version" error will be triggered. For example, if the gateway service proxies the request to an instance that no longer has the resource version in its cache, this error will frequently occur. Summary of the Invention

[0006] In view of this, the purpose of the present invention is to design a server firmware package management method, in which the gateway service selects RS based on the minimum resource version cached by multiple instances, thereby avoiding version errors, while alleviating the pressure on Kube-Apiserver instances to retry requests, and further improving Apiserver performance.

[0007] The present invention provides a K8s gateway service Watch resource optimization method, comprising the following steps:

[0008] S1. Initialize the Kubernetes cluster and report the minimum resource version number of the cached resources of the Kube-Apiserver instance;

[0009] K8s (Kubernetes, container orchestration platform): Kubernetes is a portable, extensible open source platform for managing containerized workloads and services that facilitates declarative configuration and automation.

[0010] Kube-Apiserver (Kubernetes API service): exposes the API interfaces of various Kubernetes resources and is responsible for responding to API requests from users, controllers, etc.

[0011] S2. According to the minimum resource version number of the cached resources of the Kube-Apiserver instance, the gateway service component KubeGateway selects the backend Apiserver instance.

[0012] KubeGateway (Kubernetes Gateway Service): KubeGateway is a seven-layer load balancing proxy designed and customized for HTTP2 traffic of Kube-apiserver, used for massive cluster proxy and traffic management services.

[0013] Furthermore, the method of initializing the Kubernetes cluster in step S1 and reporting the minimum resource version number of the cached resources of the Kube-Apiserver instance includes the following steps:

[0014] S11. Configure the Kubernetes agent, and have the Kube-Apiserver component initiate a registration request to the gateway service component KubeGateway.

[0015] S12. The gateway service component KubeGateway manages multiple Kube-Apiserver instances of the Kubernetes cluster;

[0016] S13. The Kube-Apiserver component periodically reports the minimum resource version number of the cached resources of the Kube-Apiserver instance to the gateway service component KubeGateway;

[0017] S14. The gateway service component KubeGateway uses the instance name of the Kube-Apiserver instance and its reported minimum resource version number as a tuple to implement local caching.

[0018] Furthermore, the method of selecting the backend Apiserver instance by the gateway service component KubeGateway in step S2 includes the following steps:

[0019] S21. The client or Kubelet component initiates a Watch request to the gateway service component KubeGateway.

[0020] Watch (an interface that provides real-time resource monitoring in Kubernetes): An interface implemented in the Kubernetes client-go client tool. It is mainly used for caching resources by various controllers (including custom controllers) in the cluster. It is usually used together with List (a full-data pull interface) to provide accuracy and real-time performance of various resources.

[0021] S22. The gateway service component KubeGatewa finds a Kube-Apiserver instance with a resource version number that is smaller than the resource version number in the current Watch monitoring request;

[0022] S23, the gateway service component KubeGateway forwards the Watch monitoring request agent to the backend Apiserver instance;

[0023] S24. The backend Apiserver instance responds to the Watch monitoring request.

[0024] Furthermore, in step S22, the gateway service component KubeGatewa finds a Kube-Apiserver instance with a resource version number smaller than the current Watch listening request by:

[0025] The gateway service component KubeGatewa traverses the local cache and finds a Kube-Apiserver instance with a resource version number that is smaller than the resource version number in the current Watch monitoring request.

[0026] The present invention also provides a K8s gateway service Watch resource system, which executes the K8s gateway service Watch resource optimization method as described above, including:

[0027] System initialization module: used to initialize the Kubernetes cluster and report the minimum resource version number of the cached resources of the Kube-Apiserver instance;

[0028] Backend instance selection module: used to select the backend Apiserver instance by the gateway service component KubeGateway based on the minimum resource version number of the cached resources of the Kube-Apiserver instance.

[0029] Furthermore, the system initialization module includes:

[0030] Initiate registration request unit: used to configure the Kubernetes agent, the Kube-Apiserver component initiates a registration request to the gateway service component KubeGateway;

[0031] Gateway service management instance unit: used to manage multiple Kube-Apiserver instances of the Kubernetes cluster through the gateway service component KubeGateway;

[0032] Version number reporting unit: used to periodically report the minimum resource version number of the cached resources of the Kube-Apiserver instance to the gateway service component KubeGateway through the Kube-Apiserver component;

[0033] Local cache unit: used to implement local caching by using the gateway service component KubeGateway to use the instance name of the Kube-Apiserver instance and its reported minimum resource version number as a tuple.

[0034] Furthermore, the backend instance selection module includes:

[0035] Initiate Watch request unit: used to initiate Watch request to the gateway service component KubeGateway through the client or Kubelet component;

[0036] Search resource version number unit: used to traverse the local cache through the gateway service component KubeGateway to find the Kube-Apiserver instance with a resource version number smaller than the resource version number in the current Watch listening request;

[0037] Forwarding Watch monitoring request unit: used to forward the Watch monitoring request proxy to the backend Apiserver instance through the gateway service component KubeGateway;

[0038] The backend instance responds to the Watch monitoring request unit: is used to respond to the Watch monitoring request through the backend Apiserver instance.

[0039] The present invention also provides a K8s gateway service Watch resource optimization device, which is installed with the K8s gateway service Watch resource optimization system as described above.

[0040] The gateway service component KubeGateway in the present invention accurately selects the backend instance based on the minimum resource version number cached in the backend instance, which can relieve the pressure of a large number of retry requests from the upstream gateway service for Kube-Apiserver and further improve the performance of Apiserver.

[0041] The present invention also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the K8s gateway service Watch resource optimization method as described above.

[0042] The present invention also provides a computer device, which includes a memory, a processor, and a computer program stored in the memory and runnable on the processor. When the processor executes the program, the steps of the K8s gateway service Watch resource optimization method as described above are implemented.

[0043] Compared with the prior art, the present invention has the following beneficial effects:

[0044] The present invention caches the minimum resource version number cached by Kube-Apiserver through the gateway service component KubeGateway, which can be used as a decision-making basis in the proxy Watch listening request stage, which is more optimized than the traditional polling method; optimizing Watch resources reduces the retry request pressure of the gateway service on the back-end instance, further improves the performance of Apiserver, and reduces the pressure on Apiserver service in the scenario of managing large-scale clusters; the minimum version number caching scheme proposed in the present invention is used as the decision-making basis of the load balancing algorithm, which can provide better decision-making capabilities than the traditional polling load balancing algorithm. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] Various other advantages and benefits will become apparent to those skilled in the art by reading the following detailed description of the preferred embodiment.The accompanying drawings are only for the purpose of illustrating the preferred embodiment and are not to be considered as limiting the present invention.

[0046] In the attached figure:

[0047] FIG1 is an architecture diagram of a gateway service polling and selecting a backend instance in the prior art;

[0048] FIG2 is a diagram of an initialization Kubernetes cluster architecture according to an embodiment of the present invention;

[0049] 3 is an architecture diagram of a gateway service according to an embodiment of the present invention that selects a backend instance based on the minimum resource version cached by multiple instances;

[0050] FIG4 is a schematic diagram of the structure of a computer device according to an embodiment of the present invention;

[0051] FIG5 is a flow chart of a K8s gateway service Watch resource optimization method according to the present invention;

[0052] FIG6 is a flow chart of a method for initializing a Kubernetes cluster and reporting the minimum resource version number of a cached resource of a Kube-Apiserver instance according to the present invention;

[0053] Figure 7 is a flow chart of the method for selecting a backend Apiserver instance by the gateway service component KubeGateway of the present invention. DETAILED DESCRIPTION

[0054] Exemplary embodiments will be described in detail herein, examples of which are illustrated in the accompanying drawings. In the following description, when referring to the drawings, like numbers in different figures represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all possible embodiments consistent with the present disclosure. Rather, they are merely examples of systems and products consistent with certain aspects of the present disclosure, as detailed in the appended claims.

[0055] The terms used in this disclosure are for the purpose of describing specific embodiments only and are not intended to limit the disclosure. As used in this disclosure and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

[0056] It should be understood that although the terms first, second, third, etc. may be used in this disclosure to describe various information, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of this disclosure, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining."

[0057] The embodiments of the present invention are described in further detail below.

[0058] An embodiment of the present invention provides a K8s gateway service Watch resource optimization method, as shown in FIG5 , including the following steps:

[0059] S1. Initialize the Kubernetes cluster and report the minimum resource version number of the cached resources of the Kube-Apiserver instance;

[0060] K8s (Kubernetes, container orchestration platform): Kubernetes is a portable, extensible open source platform for managing containerized workloads and services that facilitates declarative configuration and automation.

[0061] Kube-Apiserver (Kubernetes API service): exposes the API interfaces of various Kubernetes resources and is responsible for responding to API requests from users, controllers, etc.

[0062] The method for initializing the Kubernetes cluster and reporting the minimum resource version number of the cached resources of the Kube-Apiserver instance, as shown in Figure 6, includes the following steps:

[0063] S11. Configure the Kubernetes agent, and have the Kube-Apiserver component initiate a registration request to the gateway service component KubeGateway.

[0064] S12. The gateway service component KubeGateway manages multiple Kube-Apiserver instances of the Kubernetes cluster;

[0065] S13. The Kube-Apiserver component periodically reports the minimum resource version number of the cached resources of the Kube-Apiserver instance to the gateway service component KubeGateway;

[0066] S14. The gateway service component KubeGateway uses the instance name of the Kube-Apiserver instance and its reported minimum resource version number as a tuple to implement local caching.

[0067] 2 is an architecture diagram showing the initialization of the Kubernetes cluster and reporting of the minimum resource version number of the cached resources of the Kube-Apiserver instance in this embodiment;

[0068] S2. According to the minimum resource version number of the cached resources of the Kube-Apiserver instance, the gateway service component KubeGateway selects the backend Apiserver instance.

[0069] KubeGateway (Kubernetes Gateway Service): KubeGateway is a seven-layer load balancing proxy designed and customized for HTTP2 traffic of Kube-apiserver, used for massive cluster proxy and traffic management services.

[0070] The method for selecting the backend Apiserver instance by the gateway service component KubeGateway, as shown in Figure 7, includes the following steps:

[0071] S21. The client or Kubelet component initiates a Watch request to the gateway service component KubeGateway.

[0072] Watch (an interface that provides real-time resource monitoring in Kubernetes): An interface implemented in the Kubernetes client-go client tool. It is mainly used for caching resources by various controllers (including custom controllers) in the cluster. It is usually used together with List (a full-data pull interface) to provide accuracy and real-time performance of various resources.

[0073] S22. The gateway service component KubeGatewa finds a Kube-Apiserver instance with a resource version number that is smaller than the resource version number in the current Watch monitoring request;

[0074] The method for the gateway service component KubeGatewa to find the Kube-Apiserver instance with a resource version number smaller than the current Watch monitoring request is:

[0075] The gateway service component KubeGatewa traverses the local cache and finds a Kube-Apiserver instance with a resource version number that is smaller than the resource version number in the current Watch monitoring request.

[0076] S23, the gateway service component KubeGateway forwards the Watch monitoring request agent to the backend Apiserver instance;

[0077] S24. The backend Apiserver instance responds to the Watch monitoring request.

[0078] 3 is an architecture diagram showing the gateway service component KubeGateway selecting a backend Apiserver instance in this embodiment.

[0079] An embodiment of the present invention also provides a K8s gateway service Watch resource system, which executes the K8s gateway service Watch resource optimization method described above, including:

[0080] System initialization module: used to initialize the Kubernetes cluster and report the minimum resource version number of the cached resources of the Kube-Apiserver instance;

[0081] Backend instance selection module: used to select the backend Apiserver instance by the gateway service component KubeGateway based on the minimum resource version number of the cached resources of the Kube-Apiserver instance.

[0082] The system initialization module includes:

[0083] Initiate registration request unit: used to configure the Kubernetes agent, the Kube-Apiserver component initiates a registration request to the gateway service component KubeGateway;

[0084] Gateway service management instance unit: used to manage multiple Kube-Apiserver instances of the Kubernetes cluster through the gateway service component KubeGateway;

[0085] Version number reporting unit: used to periodically report the minimum resource version number of the cached resources of the Kube-Apiserver instance to the gateway service component KubeGateway through the Kube-Apiserver component;

[0086] Local cache unit: used to implement local caching by using the gateway service component KubeGateway to use the instance name of the Kube-Apiserver instance and its reported minimum resource version number as a tuple.

[0087] The backend instance selection module includes:

[0088] Initiate Watch request unit: used to initiate Watch request to the gateway service component KubeGateway through the client or Kubelet component;

[0089] Search resource version number unit: used to traverse the local cache through the gateway service component KubeGateway to find the Kube-Apiserver instance with a resource version number smaller than the resource version number in the current Watch listening request;

[0090] Forwarding Watch monitoring request unit: used to forward the Watch monitoring request proxy to the backend Apiserver instance through the gateway service component KubeGateway;

[0091] The backend instance responds to the Watch monitoring request unit: is used to respond to the Watch monitoring request through the backend Apiserver instance.

[0092] An embodiment of the present invention also provides a K8s gateway service Watch resource optimization device, which is installed with the K8s gateway service Watch resource optimization system as described above.

[0093] In the embodiment of the present invention, the KubeGateway gateway service accurately selects the backend instance based on the minimum resource version number cached in the backend instance, which can relieve the pressure of a large number of retry requests from the upstream gateway service for Kube-Apiserver and further improve the performance of Apiserver.

[0094] An embodiment of the present invention also provides a computer device. Figure 4 is a structural diagram of a computer device provided by an embodiment of the present invention. Referring to Figure 4 of the accompanying drawings, the computer device includes: an input system 23, an output system 24, a memory 22 and a processor 21; the memory 22 is used to store one or more programs; when the one or more programs are executed by the one or more processors 21, the one or more processors 21 implement the K8s gateway service Watch resource optimization method provided in the above embodiment; wherein the input system 23, the output system 24, the memory 22 and the processor 21 can be connected via a bus or other means, and Figure 4 takes the connection via a bus as an example.

[0095] The memory 22 is a readable and writable storage medium of a computing device, which can be used to store software programs and computer executable programs, such as the program instructions corresponding to the K8s gateway service Watch resource optimization method described in the embodiment of the present invention; the memory 22 may mainly include a program storage area and a data storage area, wherein the program storage area can store an operating system and at least one application required for a function; the data storage area can store data created according to the use of the device, etc.; in addition, the memory 22 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device; in some instances, the memory 22 may further include a memory remotely located relative to the processor 21, and these remote memories may be connected to the device via a network. Examples of the above-mentioned network include but are not limited to the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.

[0096] The input system 23 may be used to receive input digital or character information, and generate key signal input related to user settings and function control of the device; the output system 24 may include display devices such as a display screen.

[0097] The processor 21 executes various functional applications and data processing of the device by running software programs, instructions and modules stored in the memory 22, thereby implementing the above-mentioned K8s gateway service Watch resource optimization method.

[0098] The computer device provided above can be used to execute the K8s gateway service Watch resource optimization method provided in the above embodiment, and has corresponding functions and beneficial effects.

[0099] An embodiment of the present invention also provides a storage medium containing computer executable instructions, which, when executed by a computer processor, are used to execute the K8s gateway service Watch resource optimization method provided in the above embodiment. The storage medium is any of various types of memory devices or storage devices, including: installation media, such as CD-ROM, floppy disk or tape system; computer system memory or random access memory, such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory, such as flash memory, magnetic media (such as hard disk or optical storage); registers or other similar types of memory elements; the storage medium may also include other types of memory or a combination thereof; in addition, the storage medium may be located in the first computer system in which the program is executed, or may be located in a different second computer system, the second computer system being connected to the first computer system via a network (such as the Internet); the second computer system may provide program instructions to the first computer for execution. The storage medium includes two or more storage media that can reside in different locations (for example, in different computer systems connected via a network). The storage medium can store program instructions (for example, specifically implemented as a computer program) that can be executed by one or more processors.

[0100] Of course, the storage medium containing computer-executable instructions provided in an embodiment of the present invention, whose computer-executable instructions are not limited to the K8s gateway service Watch resource optimization method described in the above embodiment, can also execute related operations in the K8s gateway service Watch resource optimization method provided in any embodiment of the present invention.

[0101] Thus far, the technical solutions of the present invention have been described in conjunction with the preferred embodiments shown in the accompanying drawings. However, it will be readily understood by those skilled in the art that the scope of protection of the present invention is obviously not limited to these specific embodiments. Without departing from the principles of the present invention, those skilled in the art may make equivalent changes or substitutions to the relevant technical features, and the technical solutions after such changes or substitutions will fall within the scope of protection of the present invention.

[0102] The foregoing description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Those skilled in the art will readily appreciate that the present invention is susceptible to various modifications and variations. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of the present invention are intended to be within the scope of protection of the present invention.

Claims

1. A K8s gateway service Watch resource optimization method, characterized in that: The following steps are involved: S1. Initialize the Kubernetes cluster and report the minimum resource version number of the cached resources of the Kube-Apiserver instance; S2. According to the minimum resource version number of the cached resources of the Kube-Apiserver instance, the gateway service component KubeGateway selects the backend Apiserver instance.

2. The K8s gateway service Watch resource optimization method according to claim 1, characterized in that: The method of initializing the Kubernetes cluster in step S1 and reporting the minimum resource version number of the cached resources of the Kube-Apiserver instance includes the following steps: S11. Configure the Kubernetes agent, and the Kube-Apiserver component initiates a registration request to the gateway service component KubeGateway; S12, the gateway service component KubeGateway manages multiple Kube-Apiserver instances of the Kubernetes cluster; S13, the Kube-Apiserver component periodically reports the minimum resource version number of the cached resources of the Kube-Apiserver instance to the gateway service component KubeGateway; S14. The gateway service component KubeGateway uses the instance name of the Kube-Apiserver instance and its reported minimum resource version number as a tuple to implement local caching.

3. The K8s gateway service Watch resource optimization method according to claim 2, characterized in that: The method of selecting the backend Apiserver instance by the gateway service component KubeGateway in step S2 includes the following steps: S21. The client or Kubelet component initiates a Watch request to the gateway service component KubeGateway. S22, the gateway service component KubeGatewa finds the Kube-Apiserver instance with a resource version number smaller than the resource version number in the current Watch monitoring request; S23, the gateway service component KubeGateway forwards the Watch monitoring request proxy to the backend Apiserver instance; S24. The backend Apiserver instance responds to the Watch monitoring request.

4. The K8s gateway service Watch resource method according to claim 3, characterized in that: The method for the gateway service component KubeGatewa in step S22 to find the Kube-Apiserver instance with a resource version number smaller than the current Watch listening request is: The gateway service component KubeGatewa traverses the local cache and finds a Kube-Apiserver instance with a resource version number that is smaller than the current Watch listening request.

5. A K8s gateway service Watch resource system, executing the K8s gateway service Watch resource optimization method according to any one of claims 1 to 4, characterized in that: include: System initialization module: used to initialize the Kubernetes cluster and report the minimum resource version number of the cache resources of the Kube-Apiserver instance; The backend instance selection module is used to select the backend Apiserver instance by the gateway service component KubeGateway according to the minimum resource version number of the cached resources of the Kube-Apiserver instance.

6. The K8s gateway service Watch resource optimization system according to claim 5, characterized in that: The system initialization module includes: Initiate registration request unit: used to configure the Kubernetes agent, and the Kube-Apiserver component initiates a registration request to the gateway service component KubeGateway; Gateway service management instance unit: used to manage multiple Kube-Apiserver instances of the Kubernetes cluster through the gateway service component KubeGateway; Version number reporting unit: used to periodically report the minimum resource version number of the cached resources of the Kube-Apiserver instance to the gateway service component KubeGateway through the Kube-Apiserver component; Local cache unit: used to implement local cache by using the gateway service component KubeGateway to use the instance name of the Kube-Apiserver instance and its reported minimum resource version number as a tuple.

7. The K8s gateway service Watch resource optimization system according to claim 5, characterized in that: The backend instance selection module includes: Initiate Watch request unit: used to initiate a Watch request to the gateway service component KubeGateway through the client or Kubelet component; Search resource version number unit: used to traverse the local cache through the gateway service component KubeGateway to find a Kube-Apiserver instance with a resource version number smaller than the current Watch listening request; The Watch request forwarding unit is used to forward the Watch request proxy to the backend Apiserver instance through the gateway service component KubeGateway; The backend instance responds to the Watch monitoring request unit: is used to respond to the Watch monitoring request through the backend Apiserver instance.

8. A K8s gateway service Watch resource optimization device, characterized in that: A K8s gateway service Watch resource optimization system as described in any one of claims 5-7 is installed.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by the processor, the steps of the K8s gateway service Watch resource optimization method described in any one of claims 1-4 are implemented.

10. A computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the steps of the K8s gateway service Watch resource optimization method as described in any one of claims 1-4 are implemented.

Images