WO2021217871A1

WO2021217871A1 - Method and apparatus for deploying micro service cluster, computer device and storage medium

Info

Publication number: WO2021217871A1
Application number: PCT/CN2020/099554
Authority: WO
Inventors: 耿铭; 金鑫
Original assignee: 平安科技（深圳）有限公司
Priority date: 2020-04-28
Filing date: 2020-06-30
Publication date: 2021-11-04
Also published as: CN111666080A; CN111666080B

Abstract

A method and an apparatus for deploying a micro service cluster, a computer device and a storage medium. Said method comprises: upon receipt of a micro service cluster deployment instruction, acquiring a micro service cluster deployment file; storing a target environment configuration package into a local warehouse, making a Docket mirror file from the target environment configuration package by means of a Docker tool, associating the Docker mirror file with an environment configuration package name, and uploading the Docker mirror file to a Docker register; querying, by means of a Helm tool, from a Kubernetes cluster container whether there is an environment cluster name consistent with a target environment cluster name; creating a first micro service cluster consistent with the target environment cluster name; installing, by means of the Helm tool, the target environment configuration package into a first target host, and pushing the Docker mirror file to all of first target nodes; and constructing an environment configuration of the first micro service cluster by means of the Helm tool. The present invention implements automatic configuration of a cluster under a Kubernetes cluster container, reducing manual configuration, and improving the construction efficiency.

Description

Microservice cluster deployment method, device, computer equipment and storage medium

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office on April 28, 2020, the application number is 202010351614X, and the invention title is "microservice cluster deployment method, device, computer equipment and storage medium". The entire content of the application is approved The reference is incorporated in this application.

Technical field

This application relates to the field of microservice architecture, and in particular to a microservice cluster deployment method, device, computer equipment and storage medium.

Background technique

In the prior art, the Kubernetes cluster container scheduling orchestration technology is to divide the resources managed by a single operating system into isolated groups. The Kubernetes cluster container scheduling orchestration technology can be understood as a kind of sandbox. Each container runs an application. The containers are isolated from each other, but a communication mechanism can be established between the containers. However, building a Kubernetes cluster requires manual configuration, which is labor intensive, and the production and operation efficiency is low. Moreover, as the frequency of iterative upgrades increases, the labor costs are more and more, especially when it is encountered due to abnormalities. When rolling the historical version of the business application on the Kubernetes cluster, because Kubernetes does not natively support the rollback function. The inventor realizes that Helm's rollback function requires a command line operation to specifically query historical versions, and cannot distinguish the application environment, which consumes higher labor costs and lower operation and maintenance efficiency.

Summary of the invention

This application provides a microservice cluster deployment method, device, computer equipment, and storage medium, which realizes the automatic configuration of a cluster under a Kubernetes cluster container, reduces the tedious steps of manual configuration, improves the construction efficiency, and reduces the cost.

A microservice cluster deployment method includes:

The microservice cluster deployment instruction is received, and the microservice cluster deployment file contained in the microservice cluster deployment instruction is obtained; the microservice cluster deployment file includes the target environment cluster name, the target list, and the target environment associated with the environment configuration package name Configuration package; the target list includes a target primary IP address and at least one target node IP address;

The target environment configuration package is stored in a local warehouse, and the local warehouse uses the Docker tool to make the target environment configuration package into a Docker image file, and associates the Docker image file with the environment configuration package name, and Upload the Docker image file to the Docker registration machine;

After sending the microservice cluster deployment file to the Kubernetes cluster container, use the Helm tool to query from the Kubernetes cluster container whether there is an environment cluster name consistent with the target environment cluster name;

If there is no environment cluster name consistent with the target environment cluster name in the Kubernetes cluster container, a first microservice cluster consistent with the target environment cluster name will be created, and all those that match the target primary IP address will be created. The target machine in the Kubernetes cluster container is determined to be the first target host of the first microservice cluster, and the target machine in the Kubernetes cluster container that matches the IP address of the target node is determined to be the first microservice The first target node of the cluster;

Install the target environment configuration package to the first target host through the Helm tool, and at the same time push the Docker image file associated with the name of the environment configuration package from the Docker registry to all the first target nodes;

The environment configuration of the first microservice cluster is built through the Helm tool, and the deployment of the microservice cluster deployment file is determined to be completed.

A microservice cluster deployment device includes:

The receiving module is configured to receive the microservice cluster deployment instruction, and obtain the microservice cluster deployment file contained in the microservice cluster deployment instruction; the microservice cluster deployment file includes the target environment cluster name, the target list, and the environment configuration package A target environment configuration package associated with a name; the target list includes a target primary IP address and at least one target node IP address;

The storage module is used to store the target environment configuration package in a local warehouse. The local warehouse uses the Docker tool to make the target environment configuration package into a Docker image file, and combines the Docker image file with the environment configuration package Names are associated, and the Docker image file is uploaded to the Docker registration machine;

The query module is configured to, after sending the microservice cluster deployment file to the Kubernetes cluster container, use the Helm tool to query from the Kubernetes cluster container whether there is an environment cluster name consistent with the target environment cluster name;

The creation module is used to create a first microservice cluster consistent with the target environment cluster name if there is no environment cluster name consistent with the target environment cluster name in the Kubernetes cluster container, which will be the same as the target host The target machine in the Kubernetes cluster container that matches the IP address is determined to be the first target host of the first microservice cluster, and the target machine in the Kubernetes cluster container that matches the IP address of the target node is determined to be the target machine. The first target node of the first microservice cluster;

The installation module is used to install the target environment configuration package to the first target host through the Helm tool, and at the same time push the Docker image file associated with the name of the environment configuration package from the Docker registry to all the first target hosts. A target node;

The determining module is used to build the environment configuration of the first microservice cluster through the Helm tool, and determine the completion of the deployment of the microservice cluster deployment file.

A computer device includes a memory and a processor, the processor and the memory are connected to each other, wherein the memory is used to store a computer program, the computer program includes program instructions, and the processor is used to execute the The program instructions of the memory, wherein:

A computer-readable storage medium, the computer-readable storage medium stores a computer program, the computer program includes program instructions, and when the program instructions are executed by a processor, they are used to implement the following steps:

This application obtains the microservice cluster deployment file contained in the microservice cluster deployment instruction; the microservice cluster deployment file includes the target environment cluster name, the target list, and the target environment configuration package associated with the environment configuration package name; The target environment configuration package is stored in a local warehouse, and the local warehouse uses a Docker tool to make the target environment configuration package into a Docker image file, associate the Docker image file with the name of the environment configuration package, and associate the Upload the Docker image file to the Docker registration machine; create a first microservice cluster consistent with the target environment cluster name, and determine the target machine in the Kubernetes cluster container matching the target primary IP address as the first The first target host of a microservice cluster determines the target machine in the Kubernetes cluster container matching the IP address of the target node as the first target node of the first microservice cluster; the Helm tool The target environment configuration package is installed on the first target host, and the Docker image file associated with the name of the environment configuration package is pushed from the Docker registry to all the first target nodes; the Helm tool is used to build the first target node. The environment configuration of a microservice cluster is determined to complete the deployment of the microservice cluster deployment file. In this way, the target environment configuration package in the microservice cluster deployment file is obtained and stored in the local warehouse, and the Docker image file is made through the Docker tool. Upload to the Docker registry, create the first microservice cluster, install the target environment configuration package to the first target host in the first microservice cluster through the Helm tool, and push the Docker image file from the Docker registry to all the first target hosts in the first microservice cluster. A target node and the environment configuration for building the first microservice cluster. Therefore, automatically configuring a cluster under the Kubernetes cluster container reduces the tedious steps of manual configuration, improves the construction efficiency, and reduces the cost.

Description of the drawings

Fig. 1 is a schematic diagram of an application environment of a microservice cluster deployment method in an embodiment of the present application;

Figure 2 is a flowchart of a microservice cluster deployment method in an embodiment of the present application;

FIG. 3 is a flowchart of step S60 of a microservice cluster deployment method in an embodiment of the present application;

FIG. 4 is a flowchart of a microservice cluster deployment method in another embodiment of the present application;

FIG. 5 is a flowchart of step S80 of a microservice cluster deployment method in an embodiment of the present application;

Fig. 6 is a flowchart of step S60 of a microservice cluster deployment method in another embodiment of the present application;

FIG. 7 is a functional block diagram of a microservice cluster deployment device in an embodiment of the present application;

FIG. 8 is a functional block diagram of the determining module in the microservice cluster deployment device in an embodiment of the present application;

Fig. 9 is a schematic diagram of a computer device in an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described clearly and completely in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of them. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of this application.

The microservice cluster deployment method provided by this application can be applied in the application environment as shown in Fig. 1, where the client (computer equipment) communicates with the server through the network. Among them, the client (computer equipment) includes, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, cameras, and portable wearable devices. The server can be implemented as an independent server or a server cluster composed of multiple servers.

In an embodiment, as shown in FIG. 2, a microservice cluster deployment method is provided, and the technical solution mainly includes the following steps S10-S60:

S10. The microservice cluster deployment instruction is received, and the microservice cluster deployment file included in the microservice cluster deployment instruction is obtained; the microservice cluster deployment file includes a target environment cluster name, a target list, and information associated with the environment configuration package name Target environment configuration package; the target list includes a target primary IP address and at least one target node IP address.

Understandably, the microservice cluster deployment instruction refers to an instruction triggered when the target microservice cluster needs to be deployed, and the target microservice cluster is a cluster composed of multiple node servers or computers under the microservice architecture. The microservice cluster deployment instruction includes the target microservice cluster deployment file, and after receiving the microservice cluster deployment instruction, the microservice cluster deployment file is obtained, and the microservice cluster deployment file is for the target microservice cluster. Related files required for service cluster deployment, the microservice cluster deployment file includes the target environment cluster name, the target list, and the target environment configuration package, and the target environment cluster is named for the target microservice cluster A named unique code, the target list is a unique address (ie IP address) corresponding to all involved node servers or computers in the target microservice cluster, and the target list includes a target primary IP address and at least one target node IP address, the target primary IP address is the IP address corresponding to the server or computer in the target microservice cluster that needs to be deployed, and is responsible for managing the resources of all node servers or computers, and the target node IP address is all that needs to be deployed. The IP addresses of all involved node servers or computers in the target microservice cluster except the target primary IP address, and the target environment configuration package is a collection of codes required to deploy the target microservice cluster File, the target environment configuration package is associated with the target environment configuration package name, and the target environment configuration package name is a name for the target environment configuration package.

The server includes a Kubernetes cluster container, which is a containerized management cluster management system based on Docker, which provides the convenience of large-scale containerized cluster management.

In an embodiment, the target environment configuration package name includes a chart directory name, a target environment name, and a target version name, and the target environment name is based on the configuration under the target environment configuration package associated with the environment configuration package name. The file name corresponding to the file is abbreviated and obtained, the target version name is an iteratively updated version number, and the uniqueness of the environment configuration package name is determined according to the chart directory name, the target environment name, and the target version name .

Understandably, the target environment configuration package name includes the chart directory name, the target environment name, and the target version name. For example, the target environment configuration package name is "chart_EGLW_1.0.0", and the chart directory name is , The target environment name and the target version name can determine the unique environment configuration package, and the target environment name is spliced according to the abbreviation of the file name corresponding to the configuration file under the target environment configuration package. The target version name is an iteratively updated version number, and the format of the target version name can be set according to requirements, for example, the format of the target version name is XX.XX.XX.

In this way, through the target environment configuration package name, it is realized that the Kubernetes cluster container can allow the directory files with the same chart directory name to have different versions in different clusters, breaking the chart with only one version in the Kubernetes cluster container. The insufficiency of the directory file of the directory name makes it possible to separate the directory files of the same chart directory name between clusters.

S20. Store the target environment configuration package in a local warehouse, where the local warehouse uses a Docker tool to make the target environment configuration package into a Docker image file, and associate the Docker image file with the name of the environment configuration package , Upload the Docker image file to the Docker registration machine.

Understandably, the target environment configuration package is made into a Docker image file by using the Docker tool. The Docker image file is a completely consistent file for making the target environment configuration package. After receiving the Docker image file, you can follow The developer runs the same as the target environment configuration package, and does not need to manually configure the target environment configuration package one by one. The local warehouse is a server or computer that stores the target environment configuration package and the historical environment configuration package. The history The environment configuration package of is the target environment configuration package received before, the Docker registration machine manages to push the received Docker image file to the specified registered target machine, and the Docker tool is for developers to write Shell commands A tool for visual management of lines or scripts, through the Docker tool, the threshold for developers can be lowered, the time for writing Shell command lines or scripts can be reduced, and development efficiency can be improved.

S30. After the microservice cluster deployment file is sent to the Kubernetes cluster container, the Helm tool is used to query from the Kubernetes cluster container whether there is an environment cluster name consistent with the target environment cluster name.

Understandably, the microservice cluster deployment file is sent to the Kubernetes cluster container, and the Kubernetes cluster container is queried from the Kubernetes cluster container with the name of the target environment cluster through the Helm tool, and the Kubernetes cluster The container includes several environmental cluster names.

Among them, the Helm tool is a tool that provides powerful functions such as software deployment, deletion, upgrade, and rollback of applications on Kubernetes, and is convenient for users to find, install, upgrade, and uninstall applications in a simple manner.

S40: If there is no environment cluster name consistent with the target environment cluster name in the Kubernetes cluster container, create a first microservice cluster consistent with the target environment cluster name, which will match the target primary IP address The target machine in the Kubernetes cluster container is determined to be the first target host of the first microservice cluster, and the target machine in the Kubernetes cluster container that matches the IP address of the target node is determined to be the first The first target node of the microservice cluster.

Understandably, if the environment cluster name consistent with the target environment cluster name cannot be queried in the Kubernetes cluster container, the first microservice cluster is created, and the first microservice cluster is the same as the target environment cluster name. For target microservice clusters with the same cluster name, the target machine in the Kubernetes cluster container matching the target primary IP address is determined as the first target host of the first microservice cluster, and the target machine is the A server or computer that has a unique IP address in the Kubernetes cluster container and is registered on the Docker registration machine. The registration is an operation mode of registering on the Docker registration machine and uploading the corresponding state of the target machine regularly. The target machine in the Kubernetes cluster container matching the node IP address is determined to be the first target node of the first microservice cluster, that is, all target machines in the Kubernetes cluster container except the first target node are traversed Query the target machine that matches one of the IP addresses of all the target nodes, and determine the target machine as the first target node of the first microservice cluster.

S50. Install the target environment configuration package to the first target host through the Helm tool, and at the same time push the Docker image file associated with the name of the environment configuration package from the Docker registry to all the first target nodes .

Understandably, the target environment configuration package can be installed to the first target host through the Helm tool. The installation process is completely completed by the Helm tool without manual operation. At the same time, the The Docker image file associated with the environmental configuration package name is pushed from the Docker registration machine to all the first target nodes, and the push mode is a point-to-multipoint sending mode.

S60: Build the environment configuration of the first microservice cluster through the Helm tool, and determine to complete the deployment of the microservice cluster deployment file.

Understandably, the Helm tool is used to install the Docker image file on all the first target nodes to build the first microservice cluster, complete the environment configuration of the first microservice cluster, and then determine the The deployment of the microservice cluster deployment file is completed.

This application obtains the microservice cluster deployment file contained in the microservice cluster deployment instruction; the microservice cluster deployment file includes the target environment cluster name, the target list, and the target environment configuration package associated with the environment configuration package name; The target environment configuration package is stored in a local warehouse, and the local warehouse uses a Docker tool to make the target environment configuration package into a Docker image file, associate the Docker image file with the name of the environment configuration package, and associate the Upload the Docker image file to the Docker registration machine; create a first microservice cluster consistent with the target environment cluster name, and determine the target machine in the Kubernetes cluster container matching the target primary IP address as the first The first target host of a microservice cluster determines the target machine in the Kubernetes cluster container matching the IP address of the target node as the first target node of the first microservice cluster; the Helm tool The target environment configuration package is installed on the first target host, and the Docker image file associated with the name of the environment configuration package is pushed from the Docker registry to all the first target nodes; the Helm tool is used to build the first target node. The environment configuration of a microservice cluster determines that the deployment of the microservice cluster deployment file is completed.

This application realizes the creation of the first microservice cluster by obtaining the target environment configuration package in the microservice cluster deployment file and storing it in the local warehouse, using the Docker tool to make a Docker image file, uploading it to the Docker registry, and creating the first microservice cluster, and using the Helm tool to store the target environment The configuration package is installed to the first target host in the first microservice cluster, and the Docker image file is pushed from the Docker registration machine to all the first target nodes, and the environment configuration of the first microservice cluster is set up. Therefore, Automatic configuration of a cluster under the Kubernetes cluster container reduces the tedious steps of manual configuration, improves the construction efficiency, and reduces the cost.

In one embodiment, as shown in FIG. 3, the step S60, that is, the establishment of the environment configuration of the first microservice cluster through the Helm tool, and the determination to complete the deployment of the microservice cluster deployment file includes:

S601: Obtain the chart directory name in the target environment configuration package and the name of the environment configuration package.

Understandably, a directory file with the same name as the chart directory in the name of the environment configuration package is found from the target environment configuration package, and the directory file is used to manage the file directories under the chart directory name. , Usually save the file directory in a file in the form of a file.

S602. Through the Helm tool, the Kubernetes cluster container executes the resource declaration of the directory file associated with the chart directory name in the target environment configuration package in the first microservice cluster, and completes the configuration of the first microservice cluster. Environmental configuration.

Understandably, the Helm tool also operates on the directory file associated with the chart directory name, and performs resource declaration on the directory file associated with the chart directory name in the first microservice cluster, which means that the directory file is enabled , Enable the files under the chart directory name, that is, enable the related files of the chart directory name.

In this way, this application can quickly and complete the resource declaration of the directory file associated with the chart directory name through the Helm tool, which reduces manual and tedious operations.

In an embodiment, as shown in FIG. 4, after the step S30, that is, after querying from the Kubernetes cluster container whether there is an environmental cluster name consistent with the target environmental cluster name, the method further includes:

S70: If there is an environment cluster name consistent with the target environment cluster name in the Kubernetes cluster container, mark the cluster with the environment cluster name consistent with the target environment cluster name as a second microservice cluster; the second The microservice cluster includes a second target host and at least one second target node.

Understandably, if there is an environment cluster name consistent with the target environment cluster name in the Kubernetes cluster container, the cluster whose environment cluster name is consistent with the target environment cluster name is determined as the second microservice Cluster, the second target host is a server or computer that is associated with a second microservice cluster and manages resources for all second target nodes under the second microservice cluster, and the second target node is a second microservice cluster. All node servers or computers under the service cluster except the second target host.

S80. Update the second target host and all second target nodes of the second microservice cluster according to the target list.

Understandably, according to the target primary IP address and the target node IP address in the target list, perform the operations on the second target host and all the second target nodes in the second microservice cluster. Refresh, that is, re-determine the second target host and all second target nodes of the second microservice cluster.

In one embodiment, as shown in FIG. 5, the step S80, that is, updating the second target host and all second target nodes of the second microservice cluster according to the target list includes:

S801: Cancel the association between the second microservice cluster and the second target host, and at the same time cancel the association between the second microservice cluster and the second target node.

Understandably, there is an association relationship between the second target host and the second microservice cluster, and a connection is established through a regular monitoring method and an interactive communication method to cancel the association between the second microservice cluster and the second target host , That is, cancel the connection between the second microservice cluster and the second target host; the second target node has an association relationship with the second microservice cluster, and the connection is established through regular monitoring and interactive communication, and the cancellation The association between the second microservice cluster and the second target node is to cancel the connection between the second microservice cluster and the second target node.

S802. Determine the target machine in the Kubernetes cluster container that matches the target primary IP address as the updated second target host, and set the target machine in the Kubernetes cluster container that matches the target node IP address The target machine is determined to be the second target node after the update.

Understandably, the target machine in the Kubernetes cluster container that matches the target primary IP address is associated with the second microservice cluster, and the Kubernetes cluster that matches the target primary IP address is established. The target machine in the container is recorded as the updated second target host; the target machine in the Kubernetes cluster container matching the target node IP address is associated with the second microservice cluster, and The target machine record in the Kubernetes cluster container matching the IP address of the target node is the updated second target node, and the second microservice cluster is associated with multiple second target nodes.

S90. Install the target environment configuration package to the updated second target host through the Helm tool, and at the same time push the Docker image file associated with the name of the environment configuration package from the Docker registry to all updates The second target node afterwards.

Understandably, the target environment configuration package can be installed to the updated second target host through the Helm tool. The installation process is completely completed by the Helm tool without manual operation. At the same time, the The Docker image file associated with the name of the environment configuration package is pushed from the Docker registry to all the second target nodes, and the push mode is a point-to-multipoint sending mode.

In S100, the environment configuration of the second microservice cluster is built through the Helm tool, and the deployment of the deployment file of the microservice cluster is determined to be completed.

Understandably, the Helm tool is used to install the Docker image file on all the second target nodes to build the second microservice cluster, complete the environment configuration of the second microservice cluster, and then determine the The deployment of the microservice cluster deployment file is completed.

This application realizes that the target environment configuration package in the microservice cluster deployment file is obtained and stored in the local warehouse, the Docker image file is made through the Docker tool, and uploaded to the Docker registry, and the second microservice cluster is updated according to the target list. The Helm tool installs the target environment configuration package to the updated second target host in the second microservice cluster, and at the same time pushes the Docker image file from the Docker registry to all the updated second target nodes, and builds the second microservice cluster. The environment configuration of the service cluster, therefore, provides a way to update the existing cluster in the Kubernetes cluster container, through the Helm tool and the Docker tool, the target environment configuration package is iteratively updated the environment configuration of the cluster, and the labor cost and labor cost of cluster construction are realized. Improved construction efficiency.

In one embodiment, as shown in FIG. 6, after the step S60, that is, after the environment configuration of the first microservice cluster is built through the Helm tool, and after the deployment of the microservice cluster deployment file is determined to be completed, it includes :

S110. The microservice cluster rollback deployment instruction is received, and the microservice cluster rollback deployment file included in the microservice cluster rollback deployment instruction is obtained; the microservice cluster rollback deployment file includes the rollback environment cluster name and the rollback deployment file. Rollback list and rollback version name; the rollback list includes a rollback master IP address and at least one rollback node IP address.

Understandably, the microservice cluster rollback deployment instruction refers to an instruction that is triggered when a target microservice cluster that has been deployed and exists needs to be rolled back to a certain historical version, and the microservice cluster rollback deployment instruction The rollback deployment file of the microservice cluster includes the rollback deployment file of the microservice cluster. The rollback deployment file of the microservice cluster includes the rollback environment cluster name, the rollback list, and the rollback version name; the rollback list includes a rollback master IP address and at least An IP address of a rollback node, the rollback environment cluster is a name with a unique code corresponding to the target microservice cluster that needs to perform the environment rollback operation, and the rollback list is the target microservice that needs to perform the environment rollback operation The unique addresses (ie IP addresses) corresponding to all involved node servers or computers in the cluster, the rollback list includes one rollback primary IP address and at least one rollback node IP address, and the rollback primary IP address is required The IP address of the server or computer corresponding to the server or computer responsible for managing the resources of all node servers or computers in the target microservice cluster that performs the environment rollback operation, and the rollback node IP address is the target microservice cluster that needs to perform the environment rollback operation IP addresses corresponding to all involved node servers or computers except the primary IP address of the rollback, the rollback version is one of the environmental configuration package names associated with the historical environmental configuration package, and the rollback version The selection can be selected from the environmental configuration package names associated with all historical environmental configuration packages, or can be manually entered by the developer or selected after fuzzy query in the query dialog box.

S120. Determine the name of the configured environment configuration package that matches the name of the rollback version, and obtain the environment configuration package associated with the matched environment configuration package name from the local warehouse, where the local warehouse uses Docker The tool makes the environment configuration package into a rollback Docker image file, associates the rollback Docker image file with the rollback version name, and uploads the rollback Docker image file to the Docker registry.

Understandably, obtain the name of the environment configuration package that matches the name of the rollback version and that has been configured (that is, the name of the environment configuration package associated with the historical environment configuration package), and all historical environments are stored in the local warehouse Configuration package and each historical environment configuration package is associated with a corresponding environment configuration package name, the local warehouse manages all environment configuration packages, and the matching environment configuration package is obtained from the local warehouse Name-associated environment configuration package, the environment configuration package is made into the rollback Docker image file through the Docker tool, and the rollback Docker image file is associated with the rollback version name, and all The rollback Docker image file is sent to the Docker registration machine.

S130. Mark the cluster whose environment cluster name is consistent with the rollback environment cluster name as a third microservice cluster; update the third target host and all third target nodes of the third microservice cluster according to the rollback list .

Understandably, the cluster whose environment cluster name is consistent with the rollback environment cluster name is determined as the third microservice cluster, the third target host is associated with the third microservice cluster, and the management pair The servers or computers of all the resources of the third target node under the microservice cluster, where the third target node is all the node servers or computers under the third microservice cluster except the third target host; according to the rollback list The rollback primary IP address and the rollback node IP address in the third microservice cluster refresh the third target host and all the third target nodes in the third microservice cluster, that is, re-determine the The third target host and all third target nodes of the third microservice cluster.

S140. Install the environment configuration package to the updated third target host through the Helm tool, and at the same time push the rollback Docker image file from the Docker registry to all the updated third target nodes .

Understandably, the environment configuration package can be installed to the updated third target host through the Helm tool. The installation process is completely completed by the Helm tool without manual operation. The rollback Docker image file is pushed from the Docker registration machine to all the third target nodes, and the pushing method is a point-to-multipoint sending method.

S150: Build the environment configuration of the third microservice cluster through the Helm tool, and determine to complete the deployment of the microservice cluster deployment file.

Understandably, through the Helm tool, install the rollback Docker image file to all the third target nodes, so as to build the third microservice cluster, complete the environment configuration of the third microservice cluster, and then determine The deployment of the microservice cluster deployment file is completed.

This application realizes that the environment configuration package corresponding to the rollback version name can be quickly obtained through the local warehouse, and the third microservice cluster can be quickly rolled back to any historical environment configuration through the Docker tool and the Helm tool. , So as to quickly build the environment configuration of the third microservice cluster. In this way, manual configuration operations are greatly reduced, and the rollback limitation of the Kubernetes cluster container is solved, and the cluster under the Kubernetes cluster container can quickly be rolled back to the historical task. One version of the environment configuration.

In one embodiment, a microservice cluster deployment device is provided, and the microservice cluster deployment device corresponds to the microservice cluster deployment method in the foregoing embodiment one-to-one. As shown in FIG. 7, the device for deploying a microservice cluster includes a receiving module 11, a storage module 12, a query module 13, a creation module 14, an installation module 15 and a determination module 16. The detailed description of each functional module is as follows:

The receiving module 11 is configured to receive a microservice cluster deployment instruction, and obtain a microservice cluster deployment file contained in the microservice cluster deployment instruction; the microservice cluster deployment file includes a target environment cluster name, a target list, and environment configuration A target environment configuration package associated with the package name; the target list includes a target primary IP address and at least one target node IP address;

The storage module 12 is configured to store the target environment configuration package in a local warehouse, which uses a Docker tool to make the target environment configuration package into a Docker image file, and configures the Docker image file with the environment The package name is associated, and the Docker image file is uploaded to the Docker registration machine;

The query module 13 is configured to, after sending the microservice cluster deployment file to the Kubernetes cluster container, use the Helm tool to query from the Kubernetes cluster container whether there is an environment cluster name consistent with the target environment cluster name;

The creation module 14 is configured to create a first microservice cluster consistent with the target environment cluster name if there is no environment cluster name consistent with the target environment cluster name in the Kubernetes cluster container, which will be consistent with the target environment cluster name. The target machine in the Kubernetes cluster container that matches the primary IP address is determined to be the first target host of the first microservice cluster, and the target machine in the Kubernetes cluster container that matches the target node IP address is determined to be The first target node of the first microservice cluster;

The installation module 15 is used to install the target environment configuration package to the first target host through the Helm tool, and at the same time push the Docker image file associated with the name of the environment configuration package from the Docker registry to all the The first target node;

The determining module 16 is configured to build the environment configuration of the first microservice cluster through the Helm tool, and determine the completion of the deployment of the microservice cluster deployment file.

In an embodiment, as shown in FIG. 8, the determining module 16 includes:

The obtaining unit 61 is configured to obtain the chart directory name in the target environment configuration package and the name of the environment configuration package;

The execution unit 62 is configured to use the Helm tool, the Kubernetes cluster container to execute the resource declaration of the directory file associated with the chart directory name in the target environment configuration package in the first microservice cluster to complete the first The environment configuration of the microservice cluster.

In an embodiment, the query module 13 includes:

The marking unit is configured to mark the cluster whose environmental cluster name is consistent with the target environment cluster name as the second microservice cluster if there is an environmental cluster name consistent with the target environment cluster name in the Kubernetes cluster container; The second microservice cluster includes a second target host and at least one second target node;

An update unit, configured to update the second target host and all second target nodes of the second microservice cluster according to the target list;

The installation unit is configured to install the target environment configuration package to the updated second target host through the Helm tool, and at the same time push the Docker image file associated with the name of the environment configuration package from the Docker registry To all the second target nodes after the update;

The deployment unit is used to build the environment configuration of the second microservice cluster through the Helm tool, and determine to complete the deployment of the microservice cluster deployment file.

In an embodiment, the update unit includes:

A canceling subunit, configured to cancel the association between the second microservice cluster and the second target host, and at the same time cancel the association between the second microservice cluster and the second target node;

The association subunit is configured to determine the target machine in the Kubernetes cluster container that matches the target primary IP address as the updated second target host, and the Kubernetes that matches the target node IP address The target machine in the cluster container is determined to be the second target node after the update.

In an embodiment, the determining module 16 further includes:

The rollback receiving unit is configured to receive a microservice cluster rollback deployment instruction, and obtain the microservice cluster rollback deployment file included in the microservice cluster rollback deployment instruction; the microservice cluster rollback deployment file includes rollback Environmental cluster name, rollback list, and rollback version name; the rollback list includes a rollback primary IP address and at least one rollback node IP address;

The rollback production unit is used to determine the environment configuration package name that matches the rollback version name and has been configured, and obtains the environment configuration package associated with the matched environment configuration package name from the local warehouse, so The local warehouse uses the Docker tool to make the environment configuration package into a rollback Docker image file, associate the rollback Docker image file with the rollback version name, and upload the rollback Docker image file to the Docker registration machine;

The rollback marking unit is used to mark the cluster whose environment cluster name is consistent with the rollback environment cluster name as a third microservice cluster; and update the third target host and the third microservice cluster of the third microservice cluster according to the rollback list All third target nodes;

The rollback dark transfer unit is used to install the environment configuration package to the updated third target host through the Helm tool, and at the same time push the rollback Docker image file from the Docker registry to all updated The third target node;

The rollback deployment unit is used to build the environment configuration of the third microservice cluster through the Helm tool, and determine to complete the deployment of the microservice cluster deployment file.

For the specific limitation of the microservice cluster deployment device, please refer to the above limitation on the microservice cluster deployment method, which will not be repeated here. Each module in the above-mentioned microservice cluster deployment device can be implemented in whole or in part by software, hardware, and a combination thereof. The above-mentioned modules may be embedded in the form of hardware or independent of the processor in the computer equipment, or may be stored in the memory of the computer equipment in the form of software, so that the processor can call and execute the operations corresponding to the above-mentioned modules.

In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. 9. The computer equipment includes a processor, a memory, a network interface, and a database connected through a system bus. Among them, the processor of the computer device is used to provide calculation and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external terminal through a network connection. The computer program is executed by the processor to realize a microservice cluster deployment method.

In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and running on the processor. The processor executes the computer program to implement the microservice cluster deployment method in the above embodiment .

In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and the computer program is executed by a processor to implement the microservice cluster deployment method in the above-mentioned embodiment. Wherein, the computer-readable storage medium may be non-volatile or volatile.

A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer readable storage. In the medium, when the computer program is executed, it may include the processes of the above-mentioned method embodiments. Wherein, any reference to memory, storage, database, or other media used in the embodiments provided in this application may include non-volatile and/or volatile memory. Non-volatile memory may include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. As an illustration and not a limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM

(SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), And memory bus dynamic RAM (RDRAM), etc.

The above are only specific implementations of this application, but the protection scope of this application is not limited to this. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in this application. Should be covered within the scope of protection of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

A microservice cluster deployment method, which includes:

The microservice cluster deployment instruction is received, and the microservice cluster deployment file contained in the microservice cluster deployment instruction is obtained; the microservice cluster deployment file includes the target environment cluster name, the target list, and the target environment associated with the environment configuration package name Configuration package; the target list includes a target primary IP address and at least one target node IP address;

The target environment configuration package is stored in a local warehouse, and the local warehouse uses the Docker tool to make the target environment configuration package into a Docker image file, and associates the Docker image file with the environment configuration package name, and Upload the Docker image file to the Docker registration machine;

After sending the microservice cluster deployment file to the Kubernetes cluster container, use the Helm tool to query from the Kubernetes cluster container whether there is an environment cluster name consistent with the target environment cluster name;

If there is no environment cluster name consistent with the target environment cluster name in the Kubernetes cluster container, a first microservice cluster consistent with the target environment cluster name will be created, and all those that match the target primary IP address will be created. The target machine in the Kubernetes cluster container is determined to be the first target host of the first microservice cluster, and the target machine in the Kubernetes cluster container that matches the IP address of the target node is determined to be the first microservice The first target node of the cluster;

Install the target environment configuration package to the first target host through the Helm tool, and at the same time push the Docker image file associated with the name of the environment configuration package from the Docker registry to all the first target nodes;

The environment configuration of the first microservice cluster is built through the Helm tool, and the deployment of the microservice cluster deployment file is determined to be completed.
The microservice cluster deployment method of claim 1, wherein the target environment configuration package name includes a chart directory name, a target environment name, and a target version name, and the target environment name is based on the name associated with the environment configuration package name. The file name corresponding to the configuration file under the target environment configuration package is abbreviated and obtained, the target version name is an iteratively updated version number, which is determined according to the chart directory name, the target environment name, and the target version name The uniqueness of the environment configuration package name.
The method for deploying a microservice cluster according to claim 1, wherein the establishment of the environment configuration of the first microservice cluster through the Helm tool and determining the completion of the deployment of the deployment file of the microservice cluster comprises:

Acquiring the chart directory name in the target environment configuration package and the name of the environment configuration package;

Through the Helm tool, the Kubernetes cluster container executes the resource declaration of the directory file associated with the chart directory name in the target environment configuration package in the first microservice cluster to complete the environment configuration of the first microservice cluster .
The microservice cluster deployment method of claim 1, wherein after querying from the Kubernetes cluster container whether there is an environmental cluster name consistent with the target environmental cluster name, the method further comprises:

If there is an environment cluster name consistent with the target environment cluster name in the Kubernetes cluster container, the cluster whose environment cluster name is consistent with the target environment cluster name is marked as the second microservice cluster; the second microservice The cluster includes a second target host and at least one second target node;

Update the second target host and all second target nodes of the second microservice cluster according to the target list;

Install the target environment configuration package to the updated second target host through the Helm tool, and at the same time push the Docker image file associated with the environment configuration package name from the Docker registry to all updated The second target node;

The environment configuration of the second microservice cluster is built through the Helm tool, and the deployment of the microservice cluster deployment file is determined to be completed.
The method for deploying a microservice cluster according to claim 4, wherein said updating the second target host and all second target nodes of the second microservice cluster according to the target list comprises:

Cancel the association between the second microservice cluster and the second target host, and at the same time cancel the association between the second microservice cluster and the second target node;

The target machine in the Kubernetes cluster container that matches the target primary IP address is determined to be the updated second target host, and the target machine in the Kubernetes cluster container that matches the target node IP address is determined Determined as the second target node after the update.
The method for deploying a microservice cluster according to claim 1, wherein the establishment of the environment configuration of the first microservice cluster through the Helm tool, and after determining that the deployment of the microservice cluster deployment file is completed, comprises:

The microservice cluster rollback deployment instruction is received, and the microservice cluster rollback deployment file included in the microservice cluster rollback deployment instruction is obtained; the microservice cluster rollback deployment file includes the rollback environment cluster name and the rollback list And the rollback version name; the rollback list includes a rollback master IP address and at least one rollback node IP address;

Determine the environment configuration package name that matches the rollback version name and has been configured, and obtain the environment configuration package associated with the matching environment configuration package name from the local warehouse, and the local warehouse uses the Docker tool to download The environment configuration package is made into a rollback Docker image file, the rollback Docker image file is associated with the rollback version name, and the rollback Docker image file is uploaded to the Docker registry;

Mark the cluster whose environment cluster name is consistent with the rollback environment cluster name as the third microservice cluster; update the third target host and all third target nodes of the third microservice cluster according to the rollback list;

Install the environment configuration package to the updated third target host through the Helm tool, and at the same time push the rollback Docker image file from the Docker registry to all the updated third target nodes;

The environment configuration of the third microservice cluster is built through the Helm tool, and the deployment of the microservice cluster deployment file is determined to be completed.
A microservice cluster deployment device, which includes:

The receiving module is configured to receive the microservice cluster deployment instruction, and obtain the microservice cluster deployment file contained in the microservice cluster deployment instruction; the microservice cluster deployment file includes the target environment cluster name, the target list, and the environment configuration package A target environment configuration package associated with a name; the target list includes a target primary IP address and at least one target node IP address;

The storage module is used to store the target environment configuration package in a local warehouse. The local warehouse uses the Docker tool to make the target environment configuration package into a Docker image file, and combines the Docker image file with the environment configuration package Names are associated, and the Docker image file is uploaded to the Docker registration machine;

The query module is configured to, after sending the microservice cluster deployment file to the Kubernetes cluster container, use the Helm tool to query from the Kubernetes cluster container whether there is an environment cluster name consistent with the target environment cluster name;

The creation module is used to create a first microservice cluster consistent with the target environment cluster name if there is no environment cluster name consistent with the target environment cluster name in the Kubernetes cluster container, which will be the same as the target host The target machine in the Kubernetes cluster container that matches the IP address is determined to be the first target host of the first microservice cluster, and the target machine in the Kubernetes cluster container that matches the IP address of the target node is determined to be the target machine. The first target node of the first microservice cluster;

The installation module is used to install the target environment configuration package to the first target host through the Helm tool, and at the same time push the Docker image file associated with the name of the environment configuration package from the Docker registry to all the first target hosts. A target node;

The determining module is used to build the environment configuration of the first microservice cluster through the Helm tool, and determine the completion of the deployment of the microservice cluster deployment file.
The microservice cluster deployment device according to claim 7, which comprises:

An obtaining unit for obtaining the chart directory name in the target environment configuration package and the name of the environment configuration package;

The execution unit is configured to use the Helm tool to execute the resource declaration of the directory file associated with the chart directory name in the target environment configuration package in the first microservice cluster by the Kubernetes cluster container to complete the first microservice cluster. The environment configuration of the service cluster.
A computer device includes a memory and a processor, the processor and the memory are connected to each other, wherein the memory is used to store a computer program, the computer program includes program instructions, and the processor is used to execute the The program instructions of the memory, wherein:

The microservice cluster deployment instruction is received, and the microservice cluster deployment file contained in the microservice cluster deployment instruction is obtained; the microservice cluster deployment file includes the target environment cluster name, the target list, and the target environment associated with the environment configuration package name Configuration package; the target list includes a target primary IP address and at least one target node IP address;

The target environment configuration package is stored in a local warehouse, and the local warehouse uses the Docker tool to make the target environment configuration package into a Docker image file, and associates the Docker image file with the environment configuration package name, and Upload the Docker image file to the Docker registration machine;

After sending the microservice cluster deployment file to the Kubernetes cluster container, use the Helm tool to query from the Kubernetes cluster container whether there is an environment cluster name consistent with the target environment cluster name;

If there is no environment cluster name consistent with the target environment cluster name in the Kubernetes cluster container, a first microservice cluster consistent with the target environment cluster name will be created, and all those that match the target primary IP address will be created. The target machine in the Kubernetes cluster container is determined to be the first target host of the first microservice cluster, and the target machine in the Kubernetes cluster container that matches the IP address of the target node is determined to be the first microservice The first target node of the cluster;

Install the target environment configuration package to the first target host through the Helm tool, and at the same time push the Docker image file associated with the name of the environment configuration package from the Docker registry to all the first target nodes;

The environment configuration of the first microservice cluster is built through the Helm tool, and the deployment of the microservice cluster deployment file is determined to be completed.
The computer device according to claim 9, wherein the target environment configuration package name includes a chart directory name, a target environment name, and a target version name, and the target environment name is based on the target associated with the environment configuration package name. The file name corresponding to the configuration file under the environment configuration package is abbreviated and obtained, the target version name is an iteratively updated version number, and the environment is determined according to the chart directory name, the target environment name, and the target version name Configure the uniqueness of the package name.
The computer device of claim 9, wherein the processor is configured to:

Acquiring the chart directory name in the target environment configuration package and the name of the environment configuration package;

Through the Helm tool, the Kubernetes cluster container executes the resource declaration of the directory file associated with the chart directory name in the target environment configuration package in the first microservice cluster to complete the environment configuration of the first microservice cluster .
The computer device of claim 9, wherein the processor is configured to:

If there is an environment cluster name consistent with the target environment cluster name in the Kubernetes cluster container, the cluster whose environment cluster name is consistent with the target environment cluster name is marked as the second microservice cluster; the second microservice The cluster includes a second target host and at least one second target node;

Update the second target host and all second target nodes of the second microservice cluster according to the target list;

Install the target environment configuration package to the updated second target host through the Helm tool, and at the same time push the Docker image file associated with the environment configuration package name from the Docker registry to all updated The second target node;

The environment configuration of the second microservice cluster is built through the Helm tool, and the deployment of the microservice cluster deployment file is determined to be completed.
The computer device of claim 12, wherein the processor is configured to:

Cancel the association between the second microservice cluster and the second target host, and at the same time cancel the association between the second microservice cluster and the second target node;

The target machine in the Kubernetes cluster container that matches the target primary IP address is determined to be the updated second target host, and the target machine in the Kubernetes cluster container that matches the target node IP address is determined Determined as the second target node after the update.
The computer device of claim 9, wherein the processor is configured to:

The microservice cluster rollback deployment instruction is received, and the microservice cluster rollback deployment file included in the microservice cluster rollback deployment instruction is obtained; the microservice cluster rollback deployment file includes the rollback environment cluster name and the rollback list And the rollback version name; the rollback list includes a rollback master IP address and at least one rollback node IP address;

Determine the environment configuration package name that matches the rollback version name and has been configured, and obtain the environment configuration package associated with the matching environment configuration package name from the local warehouse, and the local warehouse uses the Docker tool to download The environment configuration package is made into a rollback Docker image file, the rollback Docker image file is associated with the rollback version name, and the rollback Docker image file is uploaded to the Docker registry;

Mark the cluster whose environment cluster name is consistent with the rollback environment cluster name as the third microservice cluster; update the third target host and all third target nodes of the third microservice cluster according to the rollback list;

Install the environment configuration package to the updated third target host through the Helm tool, and at the same time push the rollback Docker image file from the Docker registry to all the updated third target nodes;

The environment configuration of the third microservice cluster is built through the Helm tool, and the deployment of the microservice cluster deployment file is determined to be completed.
A computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, the computer program includes program instructions, and when the program instructions are executed by a processor, they are used to implement the following steps:

The microservice cluster deployment instruction is received, and the microservice cluster deployment file contained in the microservice cluster deployment instruction is obtained; the microservice cluster deployment file includes the target environment cluster name, the target list, and the target environment associated with the environment configuration package name Configuration package; the target list includes a target primary IP address and at least one target node IP address;

The target environment configuration package is stored in a local warehouse, and the local warehouse uses the Docker tool to make the target environment configuration package into a Docker image file, and associates the Docker image file with the environment configuration package name, and Upload the Docker image file to the Docker registration machine;

After sending the microservice cluster deployment file to the Kubernetes cluster container, use the Helm tool to query from the Kubernetes cluster container whether there is an environment cluster name consistent with the target environment cluster name;

If there is no environment cluster name consistent with the target environment cluster name in the Kubernetes cluster container, a first microservice cluster consistent with the target environment cluster name will be created, and all those that match the target primary IP address will be created. The target machine in the Kubernetes cluster container is determined to be the first target host of the first microservice cluster, and the target machine in the Kubernetes cluster container that matches the IP address of the target node is determined to be the first microservice The first target node of the cluster;

Install the target environment configuration package to the first target host through the Helm tool, and at the same time push the Docker image file associated with the name of the environment configuration package from the Docker registry to all the first target nodes;

The environment configuration of the first microservice cluster is built through the Helm tool, and the deployment of the microservice cluster deployment file is determined to be completed.
The computer-readable storage medium of claim 15, wherein the target environment configuration package name includes a chart directory name, a target environment name, and a target version name, and the target environment name is based on the name associated with the environment configuration package name. The file name corresponding to the configuration file under the target environment configuration package is abbreviated and obtained, the target version name is an iteratively updated version number, which is determined according to the chart directory name, the target environment name, and the target version name The uniqueness of the environment configuration package name.
15. The computer-readable storage medium of claim 15, wherein when the program instructions are executed by the processor, they are further used to implement the following steps:

Acquiring the chart directory name in the target environment configuration package and the name of the environment configuration package;

Through the Helm tool, the Kubernetes cluster container executes the resource declaration of the directory file associated with the chart directory name in the target environment configuration package in the first microservice cluster to complete the environment configuration of the first microservice cluster .
15. The computer-readable storage medium of claim 15, wherein when the program instructions are executed by the processor, they are further used to implement the following steps:

If there is an environment cluster name consistent with the target environment cluster name in the Kubernetes cluster container, the cluster whose environment cluster name is consistent with the target environment cluster name is marked as the second microservice cluster; the second microservice The cluster includes a second target host and at least one second target node;

Update the second target host and all second target nodes of the second microservice cluster according to the target list;

Install the target environment configuration package to the updated second target host through the Helm tool, and at the same time push the Docker image file associated with the environment configuration package name from the Docker registry to all updated The second target node;

The environment configuration of the second microservice cluster is built through the Helm tool, and the deployment of the microservice cluster deployment file is determined to be completed.
18. The computer-readable storage medium of claim 18, wherein, when the program instructions are executed by the processor, they are further used to implement the following steps:

Cancel the association between the second microservice cluster and the second target host, and at the same time cancel the association between the second microservice cluster and the second target node;

The target machine in the Kubernetes cluster container that matches the target primary IP address is determined to be the updated second target host, and the target machine in the Kubernetes cluster container that matches the target node IP address is determined Determined as the second target node after the update.
15. The computer-readable storage medium of claim 15, wherein when the program instructions are executed by the processor, they are further used to implement the following steps:

The microservice cluster rollback deployment instruction is received, and the microservice cluster rollback deployment file included in the microservice cluster rollback deployment instruction is obtained; the microservice cluster rollback deployment file includes the rollback environment cluster name and the rollback list And the rollback version name; the rollback list includes a rollback master IP address and at least one rollback node IP address;

Determine the environment configuration package name that matches the rollback version name and has been configured, and obtain the environment configuration package associated with the matching environment configuration package name from the local warehouse, and the local warehouse uses the Docker tool to download The environment configuration package is made into a rollback Docker image file, the rollback Docker image file is associated with the rollback version name, and the rollback Docker image file is uploaded to the Docker registry;

Mark the cluster whose environment cluster name is consistent with the rollback environment cluster name as the third microservice cluster; update the third target host and all third target nodes of the third microservice cluster according to the rollback list;

Install the environment configuration package to the updated third target host through the Helm tool, and at the same time push the rollback Docker image file from the Docker registry to all the updated third target nodes;

The environment configuration of the third microservice cluster is built through the Helm tool, and the deployment of the microservice cluster deployment file is determined to be completed.