Cloud native distributed database upgrading method, device, equipment, medium and product

Abstract

The invention discloses a cloud native distributed database upgrading method, device and equipment, a medium and a product. The method comprises the following steps: receiving an upgrading request of a user through a goldendb-controller component deployed on a main node, and determining a target working node where a target container needing to be upgraded is located; the upgrade information issued by the main node is received through a goldendb-daemonset component deployed on the target working node, so that a new mirror image is pulled to the target working node according to the upgrade information, and container mirror image information in a stateful set corresponding to the target container is updated based on the new mirror image; and creating a new container for operation according to the new mirror image through a kubelet component deployed on the target working node. According to the technical scheme provided by the invention, the upgrading efficiency of the database component is greatly improved, the rapid upgrading of the distributed database on the cloud platform is realized, and the upgrading of peripheral component versions such as monitoring and log acquisition can be realized under the condition that the normal service state of the database business component is not influenced.

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of distributed database technology, and in particular, to a cloud-native distributed database upgrade method, device, equipment, medium and product. Background Art

[0002] In the cloud-native era, database technology has undergone significant changes to meet the needs of rapidly evolving applications. Distributed databases provide high availability and scalability, and support multi-tenancy and flexible data models under microservice architectures. Serverless computing models enable resources to be automatically adjusted on demand, and containerization technology enhances the flexibility and manageability of databases. In addition, real-time data processing is enabled through event-driven architectures, and multi-model databases support a variety of data processing methods. Together, these technologies have driven the development of high-performance and flexible data management solutions for cloud-native databases.

[0003] In existing cloud-native database technologies, when upgrading a database that has already been deployed on a cloud platform, the old container is deleted and a new one is created. This process requires recalculation to schedule components to the appropriate nodes, and also requires reallocation of network resources for the new container. Since the entire network link of a distributed database is relatively complex, it takes a long time to rebuild the network link, and it also takes time to pull the image, especially for scenarios with large images, which takes longer, all of which affects the upgrade efficiency. In addition, existing technologies generally do not support upgrading a single container, resulting in the need to suspend business when upgrading other components such as monitoring, which also affects the upgrade efficiency of the database. Summary of the invention

[0004] Embodiments of the present invention provide a cloud-native distributed database upgrade method, device, equipment, medium and product to solve the problem of low upgrade efficiency in the prior art.

[0005] In a first aspect, an embodiment of the present invention provides a method for upgrading a cloud-native distributed database, wherein the distributed database is deployed based on a cloud environment built by Kubernetes, and database components are deployed in a container manner, and the method includes:

[0006] Receive the user's upgrade request through the goldendb-controller component deployed on the master node, and determine the target working node where the target container to be upgraded is located;

[0007] Receive the upgrade information sent by the master node through the goldendb-daemonset component deployed on the target working node, pull the new image to the target working node according to the upgrade information, and update the container image information in the stateful set corresponding to the target container based on the new image;

[0008] A new container is created and run according to the new image by the kubelet component deployed on the target working node.

[0009] Optionally, creating a new container to run according to the new image by a kubelet component deployed on the target working node includes:

[0010] Calling the CRI interface of the target container through the goldendb-daemonset component deployed on the target working node to stop the operation of the target container;

[0011] When the kubelet component deployed on the target working node monitors that the target container stops running, the new container is created through the CRI interface to run.

[0012] Optionally, before receiving the user's upgrade request through the goldendb-controller component deployed on the master node, the method further includes:

[0013] A stateful set is created based on user requests by the goldendb-controller component deployed on the master node to deploy and manage various database components.

[0014] Optionally, the upgrade information includes container information and version information.

[0015] Optionally, pulling a new image to the target working node according to the upgrade information includes:

[0016] Create a corresponding Job according to the upgrade information to pull the new image.

[0017] Optionally, the method further includes:

[0018] The upgrade strategy of the distributed database is configured as a fast upgrade mode or a normal upgrade mode, and the above-mentioned cloud-native distributed database upgrade method is executed when configured in the fast upgrade mode.

[0019] In a second aspect, an embodiment of the present invention further provides a cloud-native distributed database upgrade device, wherein the distributed database is deployed based on a cloud environment built by kubernetes, and the database components are deployed in a container manner, and the device includes:

[0020] The upgrade request receiving module is used to receive the user's upgrade request through the goldendb-controller component deployed on the master node, and determine the target working node where the target container to be upgraded is located;

[0021] An image update module, configured to receive the upgrade information sent by the master node through the goldendb-daemonset component deployed on the target working node, to pull a new image to the target working node according to the upgrade information, and to update the container image information in the stateful set corresponding to the target container based on the new image;

[0022] The new container running module is used to create a new container running according to the new image through the kubelet component deployed on the target working node.

[0023] In a third aspect, an embodiment of the present invention further provides a computer device, the computer device comprising:

[0024] one or more processors;

[0025] A memory for storing one or more programs;

[0026] When the one or more programs are executed by the one or more processors, the one or more processors implement the cloud-native distributed database upgrade method provided by any embodiment of the present invention.

[0027] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium on which a computer program is stored, which, when executed by a processor, implements the cloud-native distributed database upgrade method provided by any embodiment of the present invention.

[0028] In a fifth aspect, an embodiment of the present invention further provides a computer program product, which includes a computer program, and when the program is executed by a processor, it implements the cloud-native distributed database upgrade method provided by any embodiment of the present invention.

[0029] The embodiment of the present invention provides a cloud native distributed database upgrade method, the distributed database targeted is deployed based on the cloud environment built by kubernetes, and each database component is deployed in a container manner. First, the goldendb-controller component deployed on the master node receives the user's upgrade request and determines the target working node where the target container to be upgraded is located, and then the goldendb-daemonset component deployed on the target working node receives the upgrade information sent by the master node, so as to pull the new image to the target working node according to the upgrade information, and update the container image information in the stateful set corresponding to the target container based on the new image, and then create a new container according to the new image through the kubelet component deployed on the target working node. The cloud native distributed database upgrade method provided by the embodiment of the present invention reuses the same container object, only modifies the fields in the corresponding state set, avoids the cost of scheduling and allocating network resources, and at the same time, pulls the new image in advance when receiving the upgrade information, which greatly improves the upgrade efficiency of the database component, realizes the rapid upgrade of the distributed database on the cloud platform, and can also realize the upgrade of the peripheral component versions such as monitoring and log collection without affecting the normal service state of the database business component. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Figure 1 A flowchart of a cloud-native distributed database upgrade method provided in Embodiment 1 of the present invention;

[0031] Figure 2 A schematic diagram of a distributed database deployment structure provided in Embodiment 1 of the present invention;

[0032] Figure 3 A schematic diagram of an upgrade process provided in Embodiment 1 of the present invention;

[0033] Figure 4 A schematic diagram of the structure of a cloud-native distributed database upgrade device provided in Embodiment 2 of the present invention;

[0034] Figure 5 This is a schematic diagram of the structure of a computer device provided in Embodiment 3 of the present invention. DETAILED DESCRIPTION

[0035] The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the present invention, rather than to limit the present invention. It should also be noted that, for ease of description, only parts related to the present invention, rather than all structures, are shown in the accompanying drawings.

[0036] It should be mentioned before discussing the exemplary embodiments in more detail that some exemplary embodiments are described as processes or methods depicted as flow charts. Although the flow charts describe the steps as sequential processes, many of the steps therein can be implemented in parallel, concurrently or simultaneously. In addition, the order of the steps can be rearranged. The process can be terminated when its operation is completed, but can also have additional steps not included in the accompanying drawings. The process can correspond to a method, function, procedure, subroutine, subprogram, etc.

[0037] Embodiment 1

[0038] Figure 1 This is a flowchart of the cloud-native distributed database upgrade method provided in the first embodiment of the present invention. This embodiment is applicable to the situation where a distributed database is deployed and used on a public cloud platform, and can support rapid version upgrades when necessary. The method can be executed by the cloud-native distributed database upgrade device provided in the embodiment of the present invention, which can be implemented by hardware and / or software and can generally be integrated into a computer device. The distributed database targeted by the method is deployed based on the cloud environment built by kubernetes, and each database component is deployed in a container manner. Figure 1 As shown, the method specifically comprises the following steps:

[0039] S11. The goldendb-controller component deployed on the master node receives the user's upgrade request and determines the target working node where the target container to be upgraded is located.

[0040] S12. Receive the upgrade information sent by the master node through the goldendb-daemonset component deployed on the target working node, pull the new image to the target working node according to the upgrade information, and update the container image information in the stateful set corresponding to the target container based on the new image.

[0041] S13. Create a new container to run according to the new image by deploying the kubelet component on the target working node.

[0042] Specifically, kubernetes (k8s) is an open source platform for managing containerized applications on multiple hosts in a cloud platform, providing a mechanism for application deployment, planning, updating, and maintenance. Distributed databases can be deployed based on the cloud environment built by kubernetes, such as Figure 2As shown, database components, such as computing node components, storage node components, etc., can also include peripheral components such as monitoring and log collection, which will be deployed in the k8s environment in the form of containers. The cloud control component goldendb-controller component is deployed on the master node (master) of k8s, and can receive user requests through the API SERVER component for processing. The goldendb-daemonset component is deployed on each working node (node) of k8s, and can be responsible for processing the interaction with the node CRI. In each working node, each database component and goldendb-daemonset component can be scheduled and run through POD respectively. Among them, POD is the smallest unit of k8s scheduling and management. A POD can contain one or more containers. Each POD has its own virtual IP. A working node can have multiple PODs. The master node can consider the load and automatically schedule the POD to which working node to run.

[0043] When the user needs to upgrade the version of the database component, he can enter a custom upgrade request. After receiving the user's upgrade request, the goldendb-controller component can determine the target working node where the target container to be upgraded is located according to the upgrade request, and send the determined upgrade information to the target working node. Optionally, the upgrade information includes container information and version information.

[0044] When the goldendb-daemonset component on the target working node receives the upgrade information sent by the goldendb-controller component, it can first preload the image and immediately pull the corresponding new image to the target working node for standby without waiting for the container to be processed. Optionally, pulling the new image to the target working node according to the upgrade information includes: creating a corresponding Job according to the upgrade information to pull the new image. After pulling the new image, the container image information in the stateful set that manages the target container is updated to the information of the new image, that is, the same POD object can be reused here, and only the fields need to be modified. The stateful set can be an enhanced Statefulset. Statefulset is a core concept in k8s, which is used to manage POD deployment and scaling of stateful applications. Compared with the native Statefulset, the enhanced Statefulset provides more fine-grained management for containers.

[0045] After completing the loading of the new image and updating the container image information, the kubelet component on the target working node creates a new container based on the new image to complete the upgrade of the target container image version. Optionally, the creation of a new container based on the new image by the kubelet component deployed on the target working node includes: calling the CRI interface of the target container by the goldendb-daemonset component deployed on the target working node to stop the operation of the target container; and creating the new container through the CRI interface when the kubelet component deployed on the target working node monitors that the target container stops running. The specific process is as follows: Figure 3 As shown in the figure, through the cooperation of goldendb-daemonset component and kubelet component on the target working node, the old container is stopped and the new container is enabled, thus completing the operation and maintenance upgrade of the corresponding database component. Among them, CRI is a standard interface provided by k8s for integration with different container runtimes. By defining a set of standardized APIs, k8s can communicate with multiple container runtimes, thereby realizing the life cycle management of containers.

[0046] Based on the above technical solution, optionally, before receiving the user's upgrade request through the goldendb-controller component deployed on the master node, it also includes: creating a stateful set based on the user request through the goldendb-controller component deployed on the master node to deploy and manage each database component, thereby first ensuring the normal operation of the database component.

[0047] On the basis of the above technical solution, optionally, the method further includes: configuring the upgrade strategy of the distributed database to be a fast upgrade mode or a normal upgrade mode, and executing any of the above cloud-native distributed database upgrade methods when configured to be in the fast upgrade mode. Specifically, when configured to be in the fast upgrade mode, the version upgrade can be performed by using the image preloading and field modification methods provided in this embodiment, and when configured to be in the normal upgrade mode, the traditional solution can also be used for the upgrade.

[0048] The technical solution provided by the embodiment of the present invention is deployed on a cloud environment built by kubernetes for the distributed database, wherein each database component is deployed in a container manner, firstly, the goldendb-controller component deployed on the master node receives the user's upgrade request, and determines the target working node where the target container to be upgraded is located, and then the goldendb-daemonset component deployed on the target working node receives the upgrade information issued by the master node, so as to pull the new image to the target working node according to the upgrade information, and update the container image information in the stateful set corresponding to the target container based on the new image, and then create a new container according to the new image through the kubelet component deployed on the target working node. By reusing the same container object, only the fields in the corresponding state set are modified, avoiding the cost of scheduling and allocating network resources, and at the same time, when the upgrade information is received, the new image is pulled in advance for standby, which greatly improves the upgrade efficiency of the database component, realizes the rapid upgrade of the distributed database on the cloud platform, and can also realize the upgrade of the peripheral component versions such as monitoring and log collection without affecting the normal service state of the database business component.

[0049] Embodiment 2

[0050] Figure 4 This is a schematic diagram of the structure of the cloud-native distributed database upgrade device provided in the second embodiment of the present invention. The device can be implemented by hardware and / or software, and can generally be integrated into a computer device to execute the cloud-native distributed database upgrade method provided in any embodiment of the present invention. The distributed database targeted by the device is deployed based on the cloud environment built by kubernetes, and each database component is deployed in a container manner. Figure 4 As shown, the device comprises:

[0051] The upgrade request receiving module 41 is used to receive the user's upgrade request through the goldendb-controller component deployed on the master node, and determine the target working node where the target container to be upgraded is located;

[0052] An image update module 42 is used to receive the upgrade information sent by the master node through the goldendb-daemonset component deployed on the target working node, so as to pull the new image to the target working node according to the upgrade information, and update the container image information in the stateful set corresponding to the target container based on the new image;

[0053] The new container running module 43 is used to create a new container running according to the new image through the kubelet component deployed on the target working node.

[0054] The technical solution provided by the embodiment of the present invention is deployed on a cloud environment built by kubernetes for the distributed database, wherein each database component is deployed in a container manner, firstly, the goldendb-controller component deployed on the master node receives the user's upgrade request, and determines the target working node where the target container to be upgraded is located, and then the goldendb-daemonset component deployed on the target working node receives the upgrade information issued by the master node, so as to pull the new image to the target working node according to the upgrade information, and update the container image information in the stateful set corresponding to the target container based on the new image, and then create a new container according to the new image through the kubelet component deployed on the target working node. By reusing the same container object, only the fields in the corresponding state set are modified, avoiding the cost of scheduling and allocating network resources, and at the same time, when the upgrade information is received, the new image is pulled in advance for standby, which greatly improves the upgrade efficiency of the database component, realizes the rapid upgrade of the distributed database on the cloud platform, and can also realize the upgrade of the peripheral component versions such as monitoring and log collection without affecting the normal service state of the database business component.

[0055] Based on the above technical solution, optionally, the new container operation module 43 includes:

[0056] The old container decommissioning unit is used to call the CRI interface of the target container through the goldendb-daemonset component deployed on the target working node to stop the operation of the target container;

[0057] The new container enabling unit is used to create the new container to run through the CRI interface when the kubelet component deployed on the target working node monitors that the target container stops running.

[0058] On the basis of the above technical solution, optionally, the device further includes:

[0059] The stateful set creation module is used to create a stateful set based on the user's request through the goldendb-controller component deployed on the master node before receiving the user's upgrade request through the goldendb-controller component deployed on the master node, so as to deploy and manage various database components.

[0060] Based on the above technical solution, optionally, the upgrade information includes container information and version information.

[0061] On the basis of the above technical solution, optionally, the image update module 42 includes:

[0062] The image pulling unit is used to create a corresponding Job according to the upgrade information to pull the new image.

[0063] On the basis of the above technical solution, optionally, the device further includes:

[0064] The upgrade strategy configuration module is used to configure the upgrade strategy of the distributed database to a fast upgrade mode or a normal upgrade mode, and to run the above device in the fast upgrade mode.

[0065] The cloud-native distributed database upgrade device provided in the embodiment of the present invention can execute the cloud-native distributed database upgrade method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0066] It is worth noting that in the above-mentioned embodiment of the cloud-native distributed database upgrade device, the various units and modules included are only divided according to functional logic, but are not limited to the above-mentioned division, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of the present invention.

[0067] Embodiment 3

[0068] Figure 5 The schematic diagram of the structure of the computer device provided for the third embodiment of the present invention shows a block diagram of an exemplary computer device suitable for implementing the implementation mode of the present invention. Figure 5 The computer device shown is only an example and should not limit the functions and scope of use of the embodiments of the present invention. Figure 5 As shown, the computer device includes a processor 51, a memory 52, an input device 53 and an output device 54; the number of processors 51 in the computer device can be one or more. Figure 5 Taking a processor 51 as an example, the processor 51, memory 52, input device 53 and output device 54 in the computer device can be connected through a bus or other means. Figure 5 The example of connecting through bus is taken in the following.

[0069] The memory 52, as a computer-readable storage medium, can be used to store software programs, computer executable programs and modules, such as program instructions / modules corresponding to the cloud-native distributed database upgrade method in the embodiment of the present invention (for example, the upgrade request receiving module 41, the image update module 42 and the new container running module 43 in the cloud-native distributed database upgrade device). The processor 51 executes various functional applications and data processing of the computer device by running the software programs, instructions and modules stored in the memory 52, that is, realizing the above-mentioned cloud-native distributed database upgrade method.

[0070] The memory 52 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system and at least one application required for a function; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 52 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 52 may further include a memory remotely arranged relative to the processor 51, and these remote memories may be connected to the computer 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 combinations thereof.

[0071] The input device 53 may be used to obtain the user's upgrade request, and to generate key signal input related to the user setting and function control of the computer device, etc. The output device 54 may be used to provide application services, etc. to the user.

[0072] Embodiment 4

[0073] Embodiment 4 of the present invention further provides a storage medium containing computer executable instructions, which, when executed by a computer processor, is used to execute a cloud native distributed database upgrade method, the method comprising:

[0074] Receive the user's upgrade request through the goldendb-controller component deployed on the master node, and determine the target working node where the target container to be upgraded is located;

[0075] Receive the upgrade information sent by the master node through the goldendb-daemonset component deployed on the target working node, pull the new image to the target working node according to the upgrade information, and update the container image information in the stateful set corresponding to the target container based on the new image;

[0076] A new container is created and run according to the new image by the kubelet component deployed on the target working node.

[0077] The storage medium may be any of various types of memory devices or storage devices. The term "storage medium" is intended to include: installation media, such as CD-ROM, floppy disk or tape device; 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, etc. The storage medium may also include other types of memory or combinations thereof. In addition, the storage medium may be located in the computer system in which the program is executed, or may be located in a different second computer system, which is connected to the computer system via a network (such as the Internet). The second computer system may provide program instructions to the computer for execution. The term "storage medium" may include two or more storage media that may reside in different locations (e.g., in different computer systems connected via a network). The storage medium may store program instructions (e.g., embodied as a computer program) that may be executed by one or more processors.

[0078] 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 method operations described above, can also execute related operations in the cloud-native distributed database upgrade method provided in any embodiment of the present invention.

[0079] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0080] The program code embodied on the computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0081] Through the above description of the implementation methods, the technicians in the relevant field can clearly understand that the present invention can be implemented by means of software and necessary general hardware, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access memory (RAM), flash memory (FLASH), hard disk or optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, server, or network device, etc.) to execute the methods described in each embodiment of the present invention.

[0082] Embodiment 5

[0083] Embodiment 5 of the present invention also provides a computer program product, which includes a computer program (also referred to as code, instruction), which can be stored in a computer-readable storage medium. When the computer program is executed by a processor, it is used to execute the cloud-native distributed database upgrade method provided in any of the above embodiments, and has the corresponding beneficial effects of the execution method.

[0084] Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A cloud native distributed database upgrade method, characterized in that: The distributed database is deployed based on a cloud environment built by Kubernetes, and database components are deployed in a container manner. The method includes: Receive the user's upgrade request through the goldendb-controller component deployed on the master node, and determine the target working node where the target container to be upgraded is located; Receive the upgrade information sent by the master node through the goldendb-daemonset component deployed on the target working node, pull the new image to the target working node according to the upgrade information, and update the container image information in the stateful set corresponding to the target container based on the new image; A new container is created and run according to the new image by the kubelet component deployed on the target working node.

2. The cloud native distributed database upgrade method according to claim 1, characterized in that: The step of creating a new container to run according to the new image by the kubelet component deployed on the target working node includes: Calling the CRI interface of the target container through the goldendb-daemonset component deployed on the target working node to stop the operation of the target container; When the kubelet component deployed on the target working node monitors that the target container stops running, the new container is created through the CRI interface to run.

3. The cloud native distributed database upgrade method according to claim 1, characterized in that: Before receiving the user's upgrade request through the goldendb-controller component deployed on the master node, it also includes: A stateful set is created based on user requests by the goldendb-controller component deployed on the master node to deploy and manage various database components.

4. The cloud native distributed database upgrade method according to claim 1, characterized in that: The upgrade information includes container information and version information.

5. The cloud native distributed database upgrade method according to claim 1, characterized in that: Pulling the new image to the target working node according to the upgrade information includes: Create a corresponding Job according to the upgrade information to pull the new image.

6. The cloud native distributed database upgrade method according to any one of claims 1 to 5, characterized in that: The method further comprises: Configure the upgrade strategy of the distributed database to a fast upgrade mode or a normal upgrade mode, and execute the cloud-native distributed database upgrade method as described in any one of claims 1 to 5 when configured in the fast upgrade mode.

7. A cloud native distributed database upgrade device, characterized in that: The distributed database is deployed based on the cloud environment built by kubernetes, and the database components are deployed in a container manner. The device includes: The upgrade request receiving module is used to receive the user's upgrade request through the goldendb-controller component deployed on the master node, and determine the target working node where the target container to be upgraded is located; An image update module, configured to receive the upgrade information sent by the master node through the goldendb-daemonset component deployed on the target working node, to pull a new image to the target working node according to the upgrade information, and to update the container image information in the stateful set corresponding to the target container based on the new image; The new container running module is used to create a new container running according to the new image through the kubelet component deployed on the target working node.

8. A computer device, characterized in that: include: one or more processors; A memory for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the cloud-native distributed database upgrade method as described in any one of claims 1-6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the cloud-native distributed database upgrade method as described in any one of claims 1 to 6 is implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, it implements the cloud-native distributed database upgrade method as described in any one of claims 1 to 6.

Images