WO2021098392A1

WO2021098392A1 - Application deployment method and apparatus, electronic device and storage medium

Info

Publication number: WO2021098392A1
Application number: PCT/CN2020/119215
Authority: WO
Inventors: 琚汝强
Original assignee: 平安科技（深圳）有限公司
Priority date: 2019-11-19
Filing date: 2020-09-30
Publication date: 2021-05-27
Also published as: CN111090437A; CN111090437B

Abstract

An application deployment method. The method comprises: acquiring a plurality of Docker images obtained by packaging executable programs of a plurality of applications to be deployed (S11); storing the plurality of Docker images into a Docker image warehouse (S12); acquiring a plurality of Helm application templates, selected by a user at a client, corresponding to the plurality of said applications, each Helm application template containing information of a corresponding Docker image (S13); storing the plurality of Helm application templates into an application template warehouse (S14); acquiring collective deployment task information of the plurality of Helm application templates, and creating a collective deployment task according to the collective deployment task information (S15); and receiving a deployment instruction for executing the collective deployment task; invoking a Helm CLI on the basis of the deployment instruction to send a deployment request to a Kubernetes cluster, a kube-apiserver in the Kubernetes cluster invoking a Tiller of the Helm, and the Tiller deploying the plurality of said applications on the basis of the Helm application template and the Docker images in the application template warehouse (S16). Also disclosed are an application deployment apparatus and a computer-readable storage medium, which can increase the efficiency of deploying a plurality of applications.

Description

Application deployment method, device, electronic equipment and storage medium

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office on November 19, 2019, the application number is CN201911139848.1, and the invention title is "application deployment method, device and computer-readable 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 computer technology, and in particular to an application deployment method, device, electronic equipment, and storage medium.

Background technique

With the containerization of business and the transformation of system architecture to microservice architecture, it has become a development trend to decompose huge monolithic applications into multiple services. This approach decomposes the complexity of monolithic applications and makes each microservice Services can be deployed and expanded independently, which is conducive to agile development and rapid iteration.

technical problem

The inventor realized that when a huge monolithic application was decomposed into multiple services, the number of services increased greatly due to the application being split into multiple services (or components), and each service usually had its own resource file, so During deployment, it is necessary to manage, edit, and install various files (images, dependencies, etc.) required by each service, which makes it inefficient when deploying a large number of services.

Technical solutions

This application provides an application deployment method, device, electronic equipment, and storage medium.

This application also provides an application deployment method, which includes:

Obtain multiple Docker images packaged by the executable programs of multiple applications to be deployed;

Save the multiple Docker images to the Docker image warehouse;

Acquiring multiple Helm application templates corresponding to the multiple applications to be deployed selected by the user on the client, each Helm application template containing information about the corresponding Docker image;

Saving the multiple Helm application templates to the application template warehouse;

Acquiring collective deployment task information for the plurality of Helm application templates, and creating a collective deployment task according to the collective deployment task information;

Receive a deployment instruction for executing the collective deployment task, and call Helm CLI based on the deployment instruction to send a deployment request to the Kubernetes cluster, so that the kube-apiserver in the Kubernetes cluster calls Helm's Tiller, which is based on the application template The Helm application template and the Docker image in the warehouse deploy the multiple applications to be deployed.

This application also provides an application deployment device, which includes:

The first obtaining module is used to obtain multiple Docker images packaged by the executable programs of multiple applications to be deployed;

The first saving module is used to save the multiple Docker images to the Docker image warehouse;

The second obtaining module is configured to obtain multiple Helm application templates corresponding to the multiple applications to be deployed selected by the user on the client, and each Helm application template contains information about the corresponding Docker image;

The second saving module is used to save the plurality of Helm application templates to the application template warehouse;

A creation module, configured to obtain collective deployment task information for the multiple Helm application templates, and create a collective deployment task according to the collective deployment task information;

The processing module is configured to receive a deployment instruction for executing the collective deployment task, and call Helm CLI based on the deployment instruction to send a deployment request to the Kubernetes cluster, so that the kube-apiserver in the Kubernetes cluster calls Helm's Tiller, the Tiller Deploy the multiple applications to be deployed based on the Helm application template and the Docker image in the application template warehouse.

The present application also provides an electronic device that includes a memory and a processor, the memory stores an application deployment program that can run on the processor, and the application deployment program is executed when the processor is executed The following steps:

Save the multiple Docker images to the Docker image warehouse;

The present application also provides a computer-readable storage medium having an application deployment program stored on the computer-readable storage medium, and the application deployment program may be executed by one or more processors to implement the following steps:

Save the multiple Docker images to the Docker image warehouse;

Description of the drawings

FIG. 1 is a schematic flowchart of an application deployment method provided by an embodiment of this application;

2 is a schematic diagram of the internal structure of an electronic device provided by an embodiment of the application;

FIG. 3 is a schematic diagram of modules of an application deployment apparatus provided by an embodiment of the application.

The realization, functional characteristics, and advantages of the purpose of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings.

Embodiments of the present invention

It should be understood that the specific embodiments described here are only used to explain the application, and not used to limit the application.

This application provides an application deployment method. Referring to FIG. 1, it is a schematic flowchart of an application deployment method provided by an embodiment of this application. The method can be executed by an electronic device.

In this embodiment, the application deployment method includes:

Step S11: Obtain multiple Docker images packaged by multiple executable programs of applications to be deployed.

In this embodiment, the application to be deployed refers to an application to be deployed in Kubernetes, and the number of the multiple applications to be deployed is at least two.

The Docker image is a read-only template, an independent file system, including the data required to run the container, which can be used to create a new container.

Optionally, in another embodiment of the present application, the obtaining multiple Docker images packaged by executable programs of multiple applications to be deployed includes:

If a submission instruction for submitting the source code of the multiple applications to be deployed to the code repository is detected, quality inspection is performed on the source code of the multiple applications to be deployed;

If the source code of the multiple applications to be deployed passes the quality inspection, the source code of the multiple applications to be deployed is compiled and the multiple executable programs obtained after the compilation are packaged into multiple Docker images.

The code warehouse may be a system capable of code management such as Github and Gitlab.

In an optional embodiment, the source code may be quality checked by a third-party code checking tool such as SonarQube, so as to avoid large quality defects in the deployed application.

When performing quality inspection on the source code of multiple applications to be deployed, if there is a source code of the application to be deployed that has not passed the quality inspection, the source code of the application to be deployed is not compiled. For example, if there are 5 applications to be deployed, the source code of these 5 applications to be deployed is tested for quality. If all pass the quality inspection, the source code of these 5 applications to be deployed is compiled, and the 5 obtained after compilation The executable program is packaged into 5 Docker images; if the source code of the 5 applications to be deployed is checked for quality, the source code of 2 applications to be deployed fails the quality inspection, then the other 3 applications to be deployed that pass the quality inspection Compile the source code of, and package the 3 executable programs obtained after compilation into 3 Docker images.

In this embodiment, when the Docker image is packaged and generated, Docker can be packaged and generated based on the Dockerfile.

In another embodiment of the present application, the user writes or modifies the source code of multiple applications to be deployed through the integrated development environment of the application deployment platform, and compiles the source code through the integrated development environment to obtain an executable program, which is packaged into a Docker image. Obtain the path of the Docker image configured by the user on the client side of the application deployment platform, and then obtain the Docker image through the path of the Docker image.

Step S12: Save the multiple Docker images in the Docker image warehouse.

The structure of the Docker image is: the bottom end of the Docker image is a file boot system, namely bootfs. The second layer of the Docker image is the root file system rootfs, which is usually one or more operating systems, such as ubuntu. In Docker, the file system is always read-only, and every time it is modified, it is copied and superimposed to form the final file system. Docker calls such files an image. One mirror can be iterated on top of another mirror. The mirror at the bottom is called the parent mirror, and the mirror at the bottom is called the base mirror. Finally, when starting a container from an image, Docker will load a read-write file system at the top level as the container.

In this embodiment, the Docker image warehouse is used to store the Docker image of the application to be deployed.

In an optional embodiment, saving the multiple Docker images in the Docker mirror warehouse includes: acquiring the address of the Docker mirror warehouse, and saving the multiple Docker images in the Docker mirror warehouse based on the acquired address of the Docker mirror warehouse .

Step S13: Obtain multiple Helm application templates corresponding to the multiple applications to be deployed selected by the user on the client, and each Helm application template contains information about the corresponding Docker image.

In this embodiment, the client provides a window for interaction.

In an optional embodiment, the client is a client of an application deployment platform. For example, multiple application templates corresponding to multiple applications to be deployed selected in the webpage of the browser are obtained.

In this embodiment, the Helm application template is also called a Helm package, or a chart. A Helm application template contains images, dependencies, and resource definitions required to run an application, and can also contain service definitions in the Kubernetes cluster. . Helm application templates are written in Go template language, and the values of the template are recorded in the values.yaml file.

In this embodiment, the Helm application template corresponding to the application to be deployed includes images, dependencies, and resource definitions required to run the application to be deployed.

Each Helm application template contains the information of the corresponding Docker image, that is, each Helm application template contains the image name, image version and other information of the corresponding Docker image.

In this embodiment, for example, if there are 5 applications to be deployed, there are also 5 Helm application templates corresponding to the acquired applications to be deployed. Or, when there is overlap in the resource packs required by the application to be deployed when running, the number of Helm application templates corresponding to the application to be deployed can be less than 5, for example, there are 5 applications to be deployed, and the Helm corresponding to the application to be deployed is obtained. There are 3 application templates.

Further, in another embodiment of the present application, the acquiring multiple Helm application templates selected by the user on the client side and corresponding to the multiple applications to be deployed includes:

Obtain multiple application templates selected by the user from preset application templates included in the application template warehouse as multiple Helm application templates corresponding to the application to be deployed.

In this embodiment, the application template warehouse contains preset application templates. For example, the preset application templates are common applications or middleware application templates provided by public cloud vendors, such as Redis/Zookeeper/RabbitMQ/Eureka, etc.

For example, the selectable preset application template is displayed on the webpage of the browser, and the preset application template selected by the user is determined to be the Helm application template corresponding to the application to be deployed.

Through this embodiment, the application template of the application to be deployed can be quickly obtained, thereby facilitating the rapid deployment of the application to be deployed.

Or, in other embodiments of the present application, the acquiring multiple Helm application templates selected by the user on the client side and corresponding to the multiple applications to be deployed includes:

Obtain at least one application template selected by the user from the preset application templates contained in the application template warehouse as the application template to be modified, and obtain multiple application templates obtained after the user is modified based on the application template to be modified as corresponding to the application to be deployed Helm application template.

For example, if the user selects an application template and makes multiple modifications based on the application template to obtain multiple different application templates, the multiple application templates obtained after the modification are Helm application templates corresponding to the application to be deployed.

In this embodiment, the user can copy an existing public template for modification, thereby generating a private application template. For example, modify the image name.

The private application template can be saved persistently and is only available to the user. Or, the user can set the private template to be shared with other users.

Through this embodiment, it is possible to quickly create a Helm application template suitable for the application to be deployed based on the template that should be used, which improves the speed of obtaining the Helm template using the template, and realizes convenient customization of the Helm application template.

Step S14: Save the multiple Helm application templates to the application template warehouse.

In an optional embodiment, the application template warehouse may store public application templates and private application templates.

Step S15: Obtain collective deployment task information for the multiple Helm application templates, and create a collective deployment task according to the collective deployment task information.

In this embodiment, the deployment task includes, but is not limited to, the application template name, template version number, and information about the cluster to which it will be deployed. The collective deployment task includes each Helm application template, each template version number, and information about each cluster to be deployed (such as the cluster name).

For example, when there are 5 applications to be deployed, the collective deployment task information includes deployment information of these 5 applications to be deployed respectively, and the created collective deployment task can be used to deploy these 5 applications to be deployed.

For example, if the b version of a application is to be deployed to the c cluster, and the e version of the d application is to be protected to the f cluster, the deployment information of the two applications is deployed.

In other optional embodiments, the collective deployment task information is information input by the user on the web page of the browser, such as application template name, template version number, cluster name, etc.

Optionally, in another embodiment of the present application, the acquisition of collective deployment task information for the multiple Helm application templates includes:

Acquiring a collective deployment task file, where the collective deployment task file is a file in XML format;

Parse the collective deployment task file to obtain collective deployment task information for the multiple Helm application templates.

Step S16, receiving a deployment instruction for executing the collective deployment task, and calling Helm CLI based on the deployment instruction to send a deployment request to the Kubernetes cluster, so that the kube-apiserver in the Kubernetes cluster calls Helm's Tiller, which is based on the The Helm application template and the Docker image in the application template warehouse deploy the multiple applications to be deployed.

In this embodiment, the Helm CLI is the client of Helm, the Tiller is the server of Helm, and the Tiller runs in a Kubernetes cluster.

In this embodiment, when the collective deployment task contains multiple applications to be deployed, the applications to be deployed are deployed concurrently.

By creating a collective deployment task and then executing the collective deployment task in this embodiment, multiple applications can be deployed quickly without deploying a single application one by one, which improves the efficiency of application deployment.

Optionally, in another embodiment of the present application, the application deployment method further includes:

Receive a display instruction for the collective deployment task, and display the deployment progress of the collective deployment task.

For example, if the deployment progress is displayed as 3/5, it means that there are 5 deployments and 3 deployments have been completed.

In other embodiments of the present application, a deployment list is displayed through a web page, and the deployment list includes completed deployment tasks. Conducive to quickly and easily understand the deployment progress and deployment status.

The application deployment method proposed in this embodiment obtains multiple Docker images packaged by the executable programs of multiple applications to be deployed; saves the multiple Docker images in the Docker mirror warehouse; The multiple Helm application templates corresponding to the multiple applications to be deployed, each Helm application template contains the information of the corresponding Docker image; save the multiple Helm application templates in the application template warehouse; obtain the multiple Helm application templates The collective deployment task information is created based on the collective deployment task information; the deployment instruction for executing the collective deployment task is received, and Helm CLI is called based on the deployment instruction to send a deployment request to the Kubernetes cluster, so that the Kubernetes cluster The kube-apiserver in, calls Tiller of Helm, and the Tiller deploys the multiple applications to be deployed based on the Helm application template and the Docker image in the application template repository. Because the user selects the Helm application template for application deployment, users can operate conveniently and quickly without deploying through the form of command lines; at the same time, because the Helm application template is a template that packs the resources required to run the application, this The form makes the files of each application to be deployed are unified and well managed, which is conducive to the rapid deployment of rapid applications; and by combining multiple applications to be deployed into a deployment task for deployment, there is no need to deploy each application to be deployed separately, which further improves The speed of deployment achieves the goal of improving the efficiency of deploying multiple applications.

The application also provides an electronic device. Referring to FIG. 2, it is a schematic diagram of the internal structure of an electronic device provided by an embodiment of this application.

In this embodiment, the electronic device 1 may be a PC (Personal Computer, personal computer), or a terminal device such as a smart phone, a tablet computer, or a portable computer. The electronic device 1 at least includes a memory 11, a processor 12, a network interface 13, and a communication bus 14.

The memory 11 includes at least one type of readable storage medium, and the readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), magnetic memory, magnetic disk, optical disk, and the like. The memory 11 may be an internal storage unit of the electronic device 1 in some embodiments, such as a hard disk of the electronic device 1. In other embodiments, the memory 11 may also be an external storage device of the electronic device 1, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), or a secure digital (Secure Digital, SD) equipped on the electronic device 1. Flash memory card Card) and so on. Further, the memory 11 may also include both an internal storage unit of the electronic device 1 and an external storage device. The memory 11 can be used not only to store application software and various data installed in the electronic device 1, such as the code of the application deployment program 01, etc., but also to temporarily store data that has been output or will be output.

The processor 12 may be a central processing unit (Central Processing Unit) in some embodiments. Processing Unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chips are used to run program codes or process data stored in the memory 11, such as executing application deployment program 01.

The network interface 13 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface), and is usually used to establish a communication connection between the electronic device 1 and other electronic devices.

The communication bus 14 is used to realize the connection and communication between these components.

Optionally, the electronic device 1 may further include a user interface. The user interface may include a display (Display) and an input unit such as a keyboard (Keyboard). The optional user interface may also include a standard wired interface and a wireless interface. Optionally, in some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, and an OLED (Organic Light-Emitting Diode, organic light-emitting diode) touch device and so on. Among them, the display can also be appropriately called a display screen or a display unit, which is used to display the information processed in the electronic device 1 and to display a visualized user interface.

FIG. 2 only shows the electronic device 1 with components 11-14 and the application deployment program 01. Those skilled in the art can understand that the structure shown in FIG. 2 does not constitute a limitation on the electronic device 1, and may include a comparison diagram Show fewer or more components, or combinations of certain components, or different component arrangements.

In the embodiment of the electronic device 1 shown in FIG. 2, the application deployment program 01 is stored in the memory 11; when the processor 12 executes the application deployment program 01 stored in the memory 11, the following steps are implemented:

Obtain multiple Docker images packaged by the executable programs of multiple applications to be deployed.

When performing quality inspection on the source code of multiple applications to be deployed, if there is a source code of the application to be deployed that has not passed the quality inspection, the source code of the application to be deployed is not compiled. For example, if there are 5 applications to be deployed, the source code of these 5 applications to be deployed is tested for quality. If all pass the quality inspection, the source code of these 5 applications to be deployed is compiled, and the 5 obtained after compilation The executable program is packaged into 5 Docker images; if after the quality inspection of the source code of the 5 applications to be deployed, the source code of 2 applications to be deployed fails the quality inspection, then the other 3 applications to be deployed that pass the quality inspection Compile the source code of, and package the 3 executable programs obtained after compilation into 3 Docker images.

Save the multiple Docker images to the Docker image warehouse.

Acquire multiple Helm application templates corresponding to the multiple applications to be deployed selected by the user on the client, and each Helm application template includes information about a corresponding Docker image.

In this embodiment, the client provides a window for interaction.

Save the plurality of Helm application templates to the application template warehouse.

Acquire collective deployment task information for the multiple Helm application templates, and create a collective deployment task according to the collective deployment task information.

The application deployment device proposed in this embodiment obtains multiple Docker images packaged by the executable programs of multiple applications to be deployed; saves the multiple Docker images in the Docker mirror warehouse; obtains the information selected by the user on the client The multiple Helm application templates corresponding to the multiple applications to be deployed, each Helm application template contains the information of the corresponding Docker image; save the multiple Helm application templates in the application template warehouse; obtain the multiple Helm application templates The collective deployment task information is created based on the collective deployment task information; the deployment instruction for executing the collective deployment task is received, and Helm CLI is called based on the deployment instruction to send a deployment request to the Kubernetes cluster, so that the Kubernetes cluster The kube-apiserver in, calls Tiller of Helm, and the Tiller deploys the multiple applications to be deployed based on the Helm application template and the Docker image in the application template repository. Because the user selects the Helm application template for application deployment, users can operate conveniently and quickly without deploying through the form of command lines; at the same time, because the Helm application template is a template that packs the resources required to run the application, this The form makes the files of each application to be deployed are unified and well managed, which is conducive to the rapid deployment of rapid applications; and by combining multiple applications to be deployed into a deployment task for deployment, there is no need to deploy each application to be deployed separately, which further improves The speed of deployment achieves the goal of improving the efficiency of deploying multiple applications.

3, this is a schematic diagram of modules of an embodiment of the application deployment apparatus of this application. In this embodiment, the application deployment apparatus includes a first acquisition module 10, a first storage module 20, a second acquisition module 30, and a second storage module. 40. The creation module 50 and the processing module 60, exemplarily:

The first obtaining module 10 is used to: obtain multiple Docker images packaged by executable programs of multiple applications to be deployed;

The first saving module 20 is used to: save the multiple Docker images to the Docker image warehouse;

The second obtaining module 30 is configured to obtain a plurality of Helm application templates corresponding to the plurality of applications to be deployed selected by the user on the client, and each Helm application template includes information of a corresponding Docker image;

The second saving module 40 is configured to: save the plurality of Helm application templates to the application template warehouse;

The creation module 50 is configured to obtain collective deployment task information for the plurality of Helm application templates, and create a collective deployment task according to the collective deployment task information;

The processing module 60 is configured to receive a deployment instruction for executing the collective deployment task, and call Helm CLI based on the deployment instruction to send a deployment request to the Kubernetes cluster, so that the kube-apiserver in the Kubernetes cluster calls Helm's Tiller. Tiller deploys the multiple applications to be deployed based on the Helm application template and the Docker image in the application template warehouse.

The functions or operation steps implemented when the program modules such as the first acquisition module 10, the first storage module 20, the second acquisition module 30, the second storage module 40, the creation module 50, and the processing module 60 are executed are substantially the same as those in the foregoing embodiment. The same, so I won't repeat them here.

In addition, the embodiment of the present application also proposes a computer-readable storage medium, the computer-readable storage medium may be non-volatile or volatile, and the computer-readable storage medium stores an application deployment program, The application deployment program may be executed by one or more processors to implement the following operations:

Save the multiple Docker images to the Docker image warehouse;

The specific implementation of the computer-readable storage medium of the present application is basically the same as the above-mentioned embodiments of the application deployment apparatus and method, and is not described here.

It should be noted that the serial numbers of the foregoing embodiments of the present application are only for description, and do not represent the advantages and disadvantages of the embodiments. And the terms "include", "include" or any other variants thereof in this article are intended to cover non-exclusive inclusion, so that a process, device, article or method including a series of elements not only includes those elements, but also includes those elements that are not explicitly included. The other elements listed may also include elements inherent to the process, device, article, or method. Without more restrictions, the element defined by the sentence "including a..." does not exclude the existence of other identical elements in the process, device, article, or method that includes the element.

Through the description of the above implementation manners, those skilled in the art can clearly understand that the above-mentioned embodiment method can be implemented by means of software plus the necessary general hardware platform, of course, it can also be implemented by hardware, but in many cases the former is better.的实施方式。 Based on this understanding, the technical solution of this application essentially or the part that contributes to the existing technology can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM/RAM) as described above. , Magnetic disks, optical disks), including several instructions to make a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) execute the method described in each embodiment of the present application.

The above are only the preferred embodiments of the application, and do not limit the scope of the patent for this application. Any equivalent structure or equivalent process transformation made using the content of the description and drawings of the application, or directly or indirectly applied to other related technical fields , The same reason is included in the scope of patent protection of this application.

Claims

An application deployment method, wherein the method includes:

Obtain multiple Docker images packaged by the executable programs of multiple applications to be deployed;

Save the multiple Docker images to the Docker image warehouse;

Acquiring multiple Helm application templates corresponding to the multiple applications to be deployed selected by the user on the client, each Helm application template containing information about the corresponding Docker image;

Saving the multiple Helm application templates to the application template warehouse;

Acquiring collective deployment task information for the plurality of Helm application templates, and creating a collective deployment task according to the collective deployment task information;

Receive a deployment instruction for executing the collective deployment task, and call Helm CLI based on the deployment instruction to send a deployment request to the Kubernetes cluster, so that the kube-apiserver in the Kubernetes cluster calls Helm's Tiller, which is based on the application template The Helm application template and the Docker image in the warehouse deploy the multiple applications to be deployed.
5. The application deployment method according to claim 1, wherein said acquiring a plurality of Helm application templates corresponding to the plurality of applications to be deployed selected by the user at the client terminal comprises:

Acquiring multiple application templates selected by the user from the preset application templates contained in the application template warehouse as multiple Helm application templates corresponding to the application to be deployed; or

Obtain at least one application template selected by the user from the preset application templates contained in the application template warehouse as the application template to be modified, and obtain multiple application templates obtained after the user is modified based on the application template to be modified as corresponding to the application to be deployed Helm application template.
8. The application deployment method of claim 1, wherein said obtaining multiple Docker images packaged by executable programs of multiple applications to be deployed comprises:

If a submission instruction for submitting the source code of the multiple applications to be deployed to the code repository is detected, quality inspection is performed on the source code of the multiple applications to be deployed;

If the source code of the multiple applications to be deployed passes the quality inspection, the source code of the multiple applications to be deployed is compiled and the multiple executable programs obtained after the compilation are packaged into multiple Docker images.
5. The application deployment method according to claim 1, wherein said acquiring collective deployment task information for said plurality of Helm application templates comprises:

Acquiring a collective deployment task file, where the collective deployment task file is a file in XML format;

Parse the collective deployment task file to obtain collective deployment task information for the multiple Helm application templates.
The application deployment method according to any one of claims 1 to 4, wherein the method further comprises:

Receive a display instruction for the collective deployment task, and display the deployment progress of the collective deployment task.
The application deployment method of claim 3, wherein the code repository is Github or Gitlab.
5. The application deployment method of claim 1, wherein the storing the multiple Docker images in a Docker image warehouse comprises:

Obtain the address of the Docker image warehouse, and save the multiple Docker images to the Docker image warehouse based on the acquired address of the Docker image warehouse.
An application deployment device, wherein the device includes:

The first obtaining module is used to obtain multiple Docker images packaged by the executable programs of multiple applications to be deployed;

The first saving module is used to save the multiple Docker images to the Docker image warehouse;

The second obtaining module is configured to obtain multiple Helm application templates corresponding to the multiple applications to be deployed selected by the user on the client, and each Helm application template contains information about the corresponding Docker image;

The second saving module is used to save the plurality of Helm application templates to the application template warehouse;

A creation module, configured to obtain collective deployment task information for the multiple Helm application templates, and create a collective deployment task according to the collective deployment task information;

The processing module is configured to receive a deployment instruction for executing the collective deployment task, and call Helm CLI based on the deployment instruction to send a deployment request to the Kubernetes cluster, so that the kube-apiserver in the Kubernetes cluster calls Helm's Tiller, the Tiller Deploy the multiple applications to be deployed based on the Helm application template and the Docker image in the application template warehouse.
An electronic device, wherein the electronic device includes a memory and a processor, the memory stores an application deployment program that can run on the processor, and the application deployment program is executed by the processor as follows step:

Obtain multiple Docker images packaged by the executable programs of multiple applications to be deployed;

Save the multiple Docker images to the Docker image warehouse;

Acquiring multiple Helm application templates corresponding to the multiple applications to be deployed selected by the user on the client, each Helm application template containing information about the corresponding Docker image;

Saving the multiple Helm application templates to the application template warehouse;

Acquiring collective deployment task information for the plurality of Helm application templates, and creating a collective deployment task according to the collective deployment task information;

Receive a deployment instruction for executing the collective deployment task, and call Helm CLI based on the deployment instruction to send a deployment request to the Kubernetes cluster, so that the kube-apiserver in the Kubernetes cluster calls Helm's Tiller, which is based on the application template The Helm application template and the Docker image in the warehouse deploy the multiple applications to be deployed.
9. The electronic device according to claim 9, wherein said acquiring the plurality of Helm application templates corresponding to the plurality of applications to be deployed selected by the user at the client terminal comprises:

Acquiring multiple application templates selected by the user from the preset application templates contained in the application template warehouse as multiple Helm application templates corresponding to the application to be deployed; or

Obtain at least one application template selected by the user from the preset application templates contained in the application template warehouse as the application template to be modified, and obtain multiple application templates obtained after the user is modified based on the application template to be modified as corresponding to the application to be deployed Helm application template.
9. The electronic device according to claim 9, wherein said obtaining multiple Docker images packaged by executable programs of multiple applications to be deployed comprises:

If a submission instruction for submitting the source code of the multiple applications to be deployed to the code repository is detected, quality inspection is performed on the source code of the multiple applications to be deployed;

If the source code of the multiple applications to be deployed passes the quality inspection, the source code of the multiple applications to be deployed is compiled and the multiple executable programs obtained after the compilation are packaged into multiple Docker images.
The electronic device according to any one of claims 9 to 11, wherein the application deployment program can be executed by the processor, and further implements the following steps:

Receive a display instruction for the collective deployment task, and display the deployment progress of the collective deployment task.
9. The electronic device according to claim 9, wherein said acquiring collective deployment task information for said plurality of Helm application templates comprises:

Acquiring a collective deployment task file, where the collective deployment task file is a file in XML format;

Parse the collective deployment task file to obtain collective deployment task information for the multiple Helm application templates.
The electronic device of claim 11, wherein the code repository is Github or Gitlab.
A computer-readable storage medium, wherein an application deployment program is stored on the computer-readable storage medium, and the application deployment program can be executed by one or more processors to implement the following steps:

Obtain multiple Docker images packaged by the executable programs of multiple applications to be deployed;

Save the multiple Docker images to the Docker image warehouse;

Acquiring multiple Helm application templates corresponding to the multiple applications to be deployed selected by the user on the client, each Helm application template containing information about the corresponding Docker image;

Saving the multiple Helm application templates to the application template warehouse;

Acquiring collective deployment task information for the plurality of Helm application templates, and creating a collective deployment task according to the collective deployment task information;

Receive a deployment instruction for executing the collective deployment task, and call Helm CLI based on the deployment instruction to send a deployment request to the Kubernetes cluster, so that the kube-apiserver in the Kubernetes cluster calls Helm's Tiller, which is based on the application template The Helm application template and the Docker image in the warehouse deploy the multiple applications to be deployed.
15. The computer-readable storage medium according to claim 15, wherein said acquiring the plurality of Helm application templates corresponding to the plurality of applications to be deployed selected by the user at the client terminal comprises:

Acquiring multiple application templates selected by the user from the preset application templates contained in the application template warehouse as multiple Helm application templates corresponding to the application to be deployed; or

Obtain at least one application template selected by the user from the preset application templates contained in the application template warehouse as the application template to be modified, and obtain multiple application templates obtained after the user is modified based on the application template to be modified as corresponding to the application to be deployed Helm application template.
15. The computer-readable storage medium according to claim 15, wherein said obtaining a plurality of Docker images packaged by executable programs of a plurality of applications to be deployed comprises:

If a submission instruction for submitting the source code of the multiple applications to be deployed to the code repository is detected, quality inspection is performed on the source code of the multiple applications to be deployed;

If the source code of the multiple applications to be deployed passes the quality inspection, the source code of the multiple applications to be deployed is compiled and the multiple executable programs obtained after the compilation are packaged into multiple Docker images.
15. The computer-readable storage medium according to claim 15, wherein said acquiring collective deployment task information for said plurality of Helm application templates comprises:

Acquiring a collective deployment task file, where the collective deployment task file is a file in XML format;

Parse the collective deployment task file to obtain collective deployment task information for the multiple Helm application templates.
18. The computer-readable storage medium according to any one of claims 15 to 18, wherein the application deployment program further implements the following steps when the application deployment program can be executed by one or more processors:

Receive a display instruction for the collective deployment task, and display the deployment progress of the collective deployment task.
The computer-readable storage medium of claim 17, wherein the code repository is Github or Gitlab.