Multi-application deployment method, multi-application deployment apparatus, and computer-readable storage medium

Abstract

The application provides a multi-application deployment method, a multi-application deployment device and a computer readable storage medium. The multi-application deployment method comprises the following steps: obtaining a resource manifest file of a deployment scheme, wherein the resource manifest file comprises at least one target application; mapping the resource manifest file to a multi-application deployment tool of a container cloud platform, wherein the multi-application deployment tool is an application pre-deployed on the container cloud platform; creating a target application sub-instance for an application parameter of each target application in the resource manifest file by using the multi-application deployment tool; and combining at least one target application sub-instance into a target application instance. In the foregoing manner, the multi-application deployment device creates an application in an application by using a deployment tool, the sub-application instances in the application are isolated from each other, the coupling between applications is reduced, when different applications are selected according to a business scenario, a chart package does not need to be re-produced, and only a configuration file or a resource manifest file needs to be filled in, thereby reducing the work cost of a developer in producing a chart package.

Description

Technical Field

[0001] This application relates to the field of application deployment technology for container cloud platforms, and in particular to a multi-application deployment method, a multi-application deployment apparatus, and a computer-readable storage medium. Background Technology

[0002] When deploying multiple applications in native Helm, the high degree of coupling between applications makes application management difficult. In native Helm, batch deployment of multiple applications requires deploying a single Chart package that integrates all applications. Deploying this Chart package generates an instance containing the resources of all applications.

[0003] When deploying multiple applications in bulk using native Helm, application orchestration is inflexible. Helm integrates all application chart packages into a single chart package via dependencies. Users can then deploy the entire chart package and launch all applications, achieving bulk deployment of multiple applications. However, in real-world production scenarios, users select the applications needed based on their specific needs. When applications are added or removed, the entire chart package needs to be rebuilt, increasing the user's operational costs. Summary of the Invention

[0004] This application provides a multi-application deployment method, a multi-application deployment apparatus, and a computer-readable storage medium.

[0005] This application provides a method for deploying multiple applications, the method comprising:

[0006] Obtain a resource inventory file for the deployment plan, wherein the resource inventory file includes at least one target application;

[0007] The resource manifest file is mapped to a multi-application deployment tool on the container cloud platform, wherein the multi-application deployment tool is an application pre-deployed on the container cloud platform;

[0008] The multi-application deployment tool is used to create a target application sub-instance based on the application parameters of each target application in the resource manifest file;

[0009] Combine at least one target application sub-instance into a target application instance.

[0010] The step of creating a target application sub-instance using the multi-application deployment tool for the application parameters of each target application in the resource manifest file includes:

[0011] The multi-application deployment tool is used to read the application parameters of each target application in the resource manifest file.

[0012] Create a configuration file based on the application parameters of each target application;

[0013] deploying application resources according to the configuration file, and obtaining a target application sub-instance of each target application.

[0014] The reading of the application parameters of each target application in the resource manifest file by the multi-application deployment tool includes:

[0015] obtaining resource information of the multi-application deployment tool;

[0016] creating a multi-application deployment tool application instance by using the resource information;

[0017] parsing the content of the resource manifest file by using the multi-application deployment tool application instance, so as to read the application parameters of each target application.

[0018] The parsing of the content of the resource manifest file by using the multi-application deployment tool application instance includes:

[0019] calling an interface of a management and control object of a container cloud platform by using the multi-application deployment tool application instance, and parsing the content of the resource manifest file.

[0020] The mapping of the resource manifest file to the multi-application deployment tool includes:

[0021] mapping the resource manifest file to a configuration file of the multi-application deployment tool;

[0022] mounting the configuration file as a directory in a task file of the multi-application deployment tool;

[0023] The creating of a target application sub-instance of each target application in the resource manifest file by using the multi-application deployment tool includes:

[0024] executing business logic by running the task file, and reading the application parameters in the resource manifest file under the configuration file of the multi-application deployment tool;

[0025] creating a corresponding target application sub-instance by using the application parameters of each target application.

[0026] The application parameters include an application name, a repository address, a template version, and / or numerical content; and the task file is a one-time task file or a timing task file.

[0027] After the combination of the at least one target application sub-instance into a target application instance, the multi-application deployment method further includes:

[0028] obtaining an upgrade configuration file of the at least one target application sub-instance in response to an upgrade instruction of the at least one target application sub-instance.

[0029] modify the current configuration file in the at least one target sub-application instance according to the upgrade configuration file, thereby obtaining an upgraded target application sub-instance.

[0030] The method further includes:

[0031] offline the at least one target sub-application instance from the target application instance while keeping other target sub-application instances online;

[0032] replace the current configuration file with the upgrade configuration file;

[0033] recreate a target application sub-instance according to the replaced upgrade configuration file, thereby upgrading the target application sub-instance.

[0034] The method further includes:

[0035] deploying, by the container cloud platform, an application package of the multi-application deployment tool;

[0036] deploying, by the container cloud platform, application resources of the multi-application deployment tool based on the application package;

[0037] generating, based on the application resources, an application instance of the multi-application deployment tool, thereby deploying the multi-application deployment tool on the container cloud platform.

[0038] The application further provides a multi-application deployment device, which includes a processor and a memory, the memory stores program data, and the processor is used to execute the program data to realize the multi-application deployment method as described above.

[0039] The application further provides a computer readable storage medium, which is used to store program data, and the program data is used to realize the multi-application deployment method when executed by a processor.

[0040] The beneficial effects of the present application are: the multi-application deployment device obtains a resource manifest file of a deployment scheme, wherein the resource manifest file includes at least one target application; the resource manifest file is mapped to a multi-application deployment tool of a container cloud platform, wherein the multi-application deployment tool is a pre-deployed application on the container cloud platform; the application parameters of each target application in the resource manifest file are used to create a target application sub-instance by the multi-application deployment tool; and at least one target application sub-instance is combined into a target application instance. In the above manner, the multi-application deployment device realizes the creation of an application in an application by using a deployment tool, and the sub-application instances in the application are isolated from each other, thereby reducing the coupling between applications. When different applications are selected according to a business scenario, it is not necessary to re-produce a chart package, but only to fill in a configuration file or a resource manifest file, thereby reducing the work cost of developers in producing a chart package. BRIEF DESCRIPTION OF DRAWINGS

[0041] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed in the embodiment description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor. Among them:

[0042] Figure 1 is a schematic diagram of the Helm native multi-application batch deployment process provided by the present application;

[0043] Figure 2 is a flowchart of an embodiment of the multi-application deployment method provided by the present application;

[0044] Figure 3 is a schematic diagram of the Helm multi-application deployment tool batch deployment process provided by the present application;

[0045] Figure 4 is a flowchart of another embodiment of the multi-application deployment method provided by the present application;

[0046] Figure 5 is a structural schematic diagram of an embodiment of the multi-application deployment device provided by the present application;

[0047] Figure 6 is a structural schematic diagram of another embodiment of the multi-application deployment device provided by the present application;

[0048] Figure 7 is a structural schematic diagram of an embodiment of the computer readable storage medium provided by the present application. DETAILED DESCRIPTION

[0049] The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art without creative work are within the scope of protection of the present application.

[0050] The present application mainly designs the helm application deployment of the container cloud platform, specifically a multi-application deployment scheme based on Helm. The technical terms involved in the present application will be introduced as follows:

[0051] Container cloud platform: a lightweight pass platform constructed by container technology, combined with cloud native technology, using technologies such as containers, container orchestration, service mesh, etc.

[0052] Helm: similar to the package manager under the linux system, such as yum / apt, etc., which can quickly deploy the previously packaged yaml file into k8s (Kubernetes, container cluster management system) for convenient management and maintenance.

[0053] Chart: the packaging format of Helm is called chart, and chart is a series of files describing a set of related k8s cluster resources.

[0054] Application instance: the resource collection generated after the application information described in the chart is deployed by Helm, which mainly includes user applications in the form of containers, persistent volumes for information storage, etc.

[0055] Among them, chart is a collection with a specific directory tree structure and files, and the general chart directory structure is as shown in Table 1:

[0056]

[0057] Table 1

[0058] Specifically, the chart package maintains the chart.yaml file, and yaml is a high readability format used to express data sequences, also called resource manifest file or resource orchestration.

[0059] The specific file structure of chart.yaml is shown in Table 2:

[0060]

[0061]

[0062] Table 2

[0063] Wherein, the dependencies field indicates other chart packages that the current chart package depends on. Before packaging, the dependencies tgz file can be downloaded to the charts directory (oci method) by using the Helm dependency update (build) method. In addition, a sub-dependency folder can be created in the charts directory, and Helm create mysubchart can be executed in the charts directory. The folder name needs to be consistent with the name of the dependencies of the chart directory. If the dependencies with the same name need to be distinguished, the alias name is the subdirectory name under the charts package.

[0064] For details, please refer to Figure 1 , Figure 1 is a schematic diagram of the multi-application batch deployment process provided by the Helm native application.

[0065] As Figure 1 shown, the developer needs to select different applications to generate chart packages for different scenarios. The specific method is to configure the dependencies field in the chart package chart.yaml file, select the required application, and finally use the Helm dependency update (build) method to download the dependency tgz file to the charts directory in the oci method.

[0066] After the operation and maintenance personnel get the chart package, they deploy it on the container cloud platform. Helm-controller renders and generates multi-application deployment resource information according to the chart package information obtained, and transmits the multi-application deployment resource information to kube-apiserver. k8s deploys specific resources, and generates resources of multiple applications. The collection of resources of multiple applications is an application instance, which is controlled by Helm-controller. Helm-controller is an object provided by Helm for managing and running containers on a cluster.

[0067] With the development of business, when a sub-application needs to be upgraded, the application instance needs to be upgraded. The upgrade process is controlled by Helm-controller. Since all application resources are coupled in an application instance, upgrading will affect the business functions of all applications.

[0068] To solve the above problems, the application provides a multi-application deployment tool for batch deployment of multi-application. The multi-application deployment tool itself is a chart package, i.e., an application package. After the container cloud platform deploys the chart package, the multi-application deployment tool application is pulled up by the Helm-controller. The multi-application deployment tool application is configured according to the content of the configuration file at the time of deployment, and each sub-application is deployed one by one. Each sub-application is an application instance, and supports independent upgrade, online and offline, and deletion operations.

[0069] The chart directory structure of the multi-application deployment tool is shown in Table 3.

[0070]

[0071] Table 3

[0072] The values.yaml configuration file structure of the multi-application deployment tool in Table 3 is shown in Table 4.

[0073]

[0074] Table 4

[0075] In combination with the structure of the multi-application deployment tool described above, the application provides a multi-application deployment method. For details, please refer to Figure 2 and Figure 3 , Figure 2 is a flowchart of an embodiment of the multi-application deployment method provided by the application, Figure 3 is a schematic diagram of the batch deployment process of the Helm multi-application deployment tool provided by the application.

[0076] The multi-application deployment method provided by the application can be applied to a multi-application deployment device. The multi-application deployment device can be a server or a terminal device, or a system in which the server and the terminal device cooperate with each other. Accordingly, each part of the multi-application deployment device, such as each unit, sub-unit, module, and sub-module, can be provided in the server, or can be provided in the server and the terminal device, respectively.

[0077] Further, the server can be hardware or software. When the server is hardware, it can be implemented as a distributed server cluster composed of multiple servers, such as a distributed system, a cloud, etc., or as a single server. When the server is software, it can be implemented as multiple software or software modules, such as software or software modules for providing a distributed server, or as a single software or software module, without specific limitation here. In some possible implementation manners, the multi-application deployment method provided by the embodiments of the application can be implemented by a processor calling computer readable instructions stored in a memory.

[0078] AsFigure 2 As shown, the multi-application deployment method of the embodiments of the present application specifically includes the following steps:

[0079] Step S11: Obtain a resource manifest file of a deployment scheme, wherein the resource manifest file includes at least one target application.

[0080] In the embodiments of the present application, the developer selects different applications, fills in the multi-application deployment tool values.yaml according to the format, and outputs the deployment scheme yaml, i.e., the resource manifest file, instead of the chart package. For example, Figure 3 As shown, the deployment scheme A composed of the applications selected by the developer can include application A, application B, application C, and application D, and the deployment scheme B can include application A, application B, application E, and application F.

[0081] Step S12: Map the resource manifest file to a multi-application deployment tool of a container cloud platform, wherein the multi-application deployment tool is an application pre-deployed on the container cloud platform.

[0082] In the embodiments of the present application, the multi-application deployment device maps the deployment scheme yaml, i.e., the resource manifest file, to the multi-application deployment tool.

[0083] Specifically, after the operation and maintenance personnel obtain the deployment scheme yaml, the multi-application deployment tool chart is deployed on the container cloud platform. Then, the multi-application deployment device maps the deployment scheme yaml to the multi-application deployment tool configmap, i.e., the configuration file.

[0084] It should be noted that the multi-application deployment tool is specifically an application pre-deployed on a container cloud platform, and the target application in step S11 can be a business application or a tool application, i.e., the multi-application deployment tool can also be deployed through the multi-application deployment file of the present application, i.e., as Figure 1 As shown, any one or more applications in the application package.

[0085] Specifically, the deployment process of the multi-application deployment tool is as follows: deploying the application package of the multi-application deployment tool on the container cloud platform; deploying the application resources of the multi-application deployment tool on the container cloud platform based on the application package; generating the application instance of the multi-application deployment tool based on the application resources, and deploying the multi-application deployment tool on the container cloud platform through the application instance.

[0086] Step S13: Create a target application sub-instance for the application parameters of each target application in the resource manifest file by using the multi-application deployment tool.

[0087] In the embodiment of the present application, the multi-application deployment device reads the application parameters of each target application in the resource manifest file by using the multi-application deployment tool, calls the interface of the management and control object of the container cloud platform by using the multi-application deployment tool application instance, and parses the content of the resource manifest file. The multi-application deployment device creates a configuration file based on the application parameters of each target application; deploys application resources according to the configuration file, and obtains the target application sub-instances of each target application.

[0088] Specifically, the deployment tool configmap is mounted as a directory to the deployment tool job, that is, a task file, and the deployment tool job executes business logic and reads the content under the configmap mapping directory, that is, the application parameters of different applications such as application name, repository address, template version, values content, etc. The deployment tool job can specifically select a one-time task file or a timing task file. Further, each sub-application respectively calls the api (interface) of the Helm-controller, and creates an application instance of each sub-application according to the application parameters thereof.

[0089] Further, the multi-application deployment device can also obtain the resource information of the multi-application deployment tool; create a multi-application deployment tool application instance by using the resource information; and parse the content of the resource manifest file by using the multi-application deployment tool application instance, so as to read the application parameters of each target application.

[0090] Specifically, after the Helm-controller of the container cloud platform obtains the chart information of the multi-application deployment tool, the chart information is rendered, so as to create the k8s resources of the multi-application deployment tool, thereby creating the application instance of the multi-application deployment tool. The application instance of the multi-application deployment tool parses the content of the deployment scheme, and reversely calls the Helm-controller of the container cloud platform to read the application parameters of each sub-application in the resource manifest file.

[0091] Step S14: combining at least one target application sub-instance into a target application instance.

[0092] In the embodiment of the present application, the multi-application deployment device creates the application instance A, the application instance B, the application instance C and the application instance D by using the above step S13, and combines them to form the target application instance. Figure 3 The target application instance.

[0093] In the embodiment of the present application, the multi-application deployment device obtains a resource manifest file of a deployment scheme, wherein the resource manifest file includes at least one target application; maps the resource manifest file to a multi-application deployment tool of a container cloud platform, wherein the multi-application deployment tool is an application pre-deployed on the container cloud platform; creates a target application sub-instance for the application parameters of each target application in the resource manifest file by using the multi-application deployment tool; and combines the at least one target application sub-instance into a target application instance. In the foregoing manner, the multi-application deployment device realizes the creation of an application in an application by using a deployment tool, and the sub-application instances in the application are isolated from each other, thereby reducing the coupling between applications. When different applications are selected according to a business scenario, it is not necessary to re-produce a chart package, but only to fill in a configuration file or a resource manifest file, thereby reducing the work cost of developers in producing a chart package.

[0094] In an actual production scenario, a version upgrade needs to be performed on a certain application, the application needs to be taken offline, and the business functions of the application are affected. Since all applications are integrated in the same instance, the online and offline of a certain application in the instance means the online and offline of all applications, and therefore the business functions of all applications are affected.

[0095] To solve the problem in the actual production scenario, the present application further provides another multi-application deployment method. Based on the multi-application deployment method, when a certain sub-application needs to be upgraded, only the sub-application instance needs to be upgraded. Since the sub-application instances are isolated from each other, the upgrade of a certain sub-application will not affect the business functions of other applications.

[0096] For details, please refer to Figure 4 , Figure 4 which is a flowchart of another embodiment of the multi-application deployment method provided by the present application

[0097] As Figure 4 shown, the multi-application deployment method of the embodiment of the present application specifically includes the following steps:

[0098] Step S21: In response to an upgrade instruction of at least one target sub-application instance, an upgrade configuration file of the at least one target sub-application instance is obtained.

[0099] In the embodiment of the present application, as Figure 3 described, an operation and maintenance personnel sends an upgrade instruction of an application A to a container cloud platform, and the container cloud platform obtains chart information of the application A, i.e., an upgrade configuration file of the application A, based on the upgrade instruction.

[0100] Step S22: The current configuration file in the at least one target sub-application instance is modified according to the upgrade configuration file, thereby obtaining an upgraded target sub-application instance.

[0101] In the embodiment of the present application, the container cloud platform takes the application instance A offline from the target application instance, and keeps other application instances, i.e., the application instance B, the application instance C and the application instance D, in the online state. The multi-application deployment device calls the Helm-controller of the container cloud platform to update the configuration file of the application instance A, so as to recreate the application instance A. During this period, the resources of other application instances are not affected and do not need to be taken offline.

[0102] In the embodiment of the present application, the application created by the deployment tool reversely calls the Helm-controller, realizing the creation of an application in an application. The original Helm multi-application batch deployment causes high coupling between applications, and it is difficult to control the applications. The deployment by the deployment tool ensures that the sub-application instances are isolated from each other on the basis of one-time configuration, reduces the coupling between applications, and realizes the independent upgrade, online and offline and deletion of the sub-application. According to the business scenario, different applications are selected without the need to re-produce the chart package, and only the configuration file needs to be filled in, reducing the work cost of the developer to produce the chart package.

[0103] Further, the multi-application deployment device supports the independent upgrade, online and offline and deletion functions of the sub-application. The coupling between applications is reduced, the granularity of application control is refined, a multi-application deployment yaml one-key configuration solution is provided, and the application to be deployed can be selected by modifying the configuration file without the need to re-produce the chart package.

[0104] Those skilled in the art can understand that in the above method of the specific implementation, the writing order of each step does not mean a strict execution order and does not constitute any limitation on the implementation process. The specific execution order of each step should be determined by its function and possible internal logic.

[0105] To realize the multi-application deployment method of the above-mentioned embodiments, the present application further provides a multi-application deployment device, which is specifically described in the following Figure 5 , Figure 5 is a structural schematic diagram of an embodiment of the multi-application deployment device provided by the present application.

[0106] The multi-application deployment device 300 of the embodiment of the present application comprises an acquisition module 31, a mapping module 32, a creation module 33 and a combination module 34.

[0107] The acquisition module 31 is configured to acquire a resource manifest file of a deployment scheme, wherein the resource manifest file comprises at least one target application.

[0108] The mapping module 32 is configured to map the resource manifest file to a multi-application deployment tool of a container cloud platform, wherein the multi-application deployment tool is an application pre-deployed on the container cloud platform.

[0109] The creating module 33 is configured to create a target application sub-instance for each target application in the resource manifest file by using the multi-application deployment tool.

[0110] The combining module 34 is configured to combine at least one target application sub-instance into a target application instance.

[0111] To implement the multi-application deployment method in the above embodiment, the application further provides another multi-application deployment apparatus, which can be referred to Figure 6 , Figure 6 FIG. 5 is a structural schematic diagram of another embodiment of the multi-application deployment apparatus provided by the application.

[0112] The multi-application deployment apparatus 500 in the embodiment of the application comprises a memory 51 and a processor 52, wherein the memory 51 and the processor 52 are coupled.

[0113] The memory 51 is configured to store program data, and the processor 52 is configured to execute the program data to implement the multi-application deployment method in the above embodiment.

[0114] In the embodiment, the processor 52 can also be referred to as a CPU (Central Processing Unit). The processor 52 can be an integrated circuit chip with a processing capability of signals. The processor 52 can also be a general-purpose processor, a DSP (Digital Signal Process), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. The general-purpose processor can be a microprocessor or the processor 52 can also be any conventional processor.

[0115] To implement the multi-application deployment method in the above embodiment, the application further provides a computer readable storage medium, such as Figure 7 As shown in FIG. 6, the computer readable storage medium 600 is configured to store program data 61, and the program data 61 is used to implement the multi-application deployment method in the above embodiment when executed by a processor.

[0116] The application further provides a computer program product, wherein the computer program product comprises a computer program, and the computer program is operable to make a computer execute the multi-application deployment method in the above embodiment. The computer program product can be a software installation package.

[0117] When the multi-application deployment method described in the above embodiments of the present application is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a device, such as a computer readable storage medium. Based on this understanding, the technical solutions of the present application, essentially or in other words, the part that contributes to the prior art or the whole or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium, including a number of instructions to make a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor execute all or part of the steps of the methods described in the various embodiments of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and various media that can store program codes.

[0118] The above is only an embodiment of the present application, and does not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation using the content of the present application specification and drawings, or direct or indirect application in other related technical fields, is also included in the patent protection scope of the present application.

Claims

1. A multi-application deployment method, characterized by, The multi-application deployment method comprises: obtaining a resource manifest file of a deployment scheme, wherein the resource manifest file comprises at least one target application; mapping the resource manifest file to a multi-application deployment tool of a container cloud platform, wherein the multi-application deployment tool is an application pre-deployed on the container cloud platform; creating a target application sub-instance for each target application in the resource manifest file by using the multi-application deployment tool; combining at least one target application sub-instance into a target application instance; the step of creating a target application sub-instance for each target application in the resource manifest file by using the multi-application deployment tool comprises: reading the application parameters of each target application in the resource manifest file by using the multi-application deployment tool; creating a configuration file based on the application parameters of each target application; deploying application resources according to the configuration file to obtain a target application sub-instance of each target application.

2. The multi-application deployment method of claim 1, wherein: the step of reading the application parameters of each target application in the resource manifest file by using the multi-application deployment tool comprises: obtaining resource information of the multi-application deployment tool; creating a multi-application deployment tool application instance by using the resource information; parsing the content of the resource manifest file by using the multi-application deployment tool application instance to read the application parameters of each target application.

3. The multi-application deployment method of claim 2, wherein: the step of parsing the content of the resource manifest file by using the multi-application deployment tool application instance comprises: calling an interface of a management and control object of the container cloud platform by using the multi-application deployment tool application instance to parse the content of the resource manifest file.

4. The multi-application deployment method of claim 1, wherein: the step of mapping the resource manifest file to the multi-application deployment tool comprises: mapping the resource manifest file to a configuration file of the multi-application deployment tool; mounting the configuration file as a directory in a task file of the multi-application deployment tool; the step of creating a target application sub-instance for each target application in the resource manifest file by using the multi-application deployment tool comprises: reading the application parameters in the resource manifest file under the configuration file of the multi-application deployment tool by running the task file to execute business logic; creating a corresponding target application sub-instance by using the application parameters of each target application; wherein the application parameters comprise an application name, a repository address, a template version, and / or numerical content; and the task file is a one-time task file or a timed task file.

5. The multi-application deployment method of claim 1, wherein: after the step of combining at least one target application sub-instance into a target application instance, the multi-application deployment method further comprises: in response to an upgrade instruction of at least one target application sub-instance, obtaining an upgrade configuration file of the at least one target application sub-instance. According to the upgrade configuration file, the current configuration file in the at least one target sub-application instance is modified, so as to obtain an upgraded target application sub-instance.

6. The multi-application deployment method of claim 5, wherein, According to the upgrade configuration file, the current configuration file in the at least one target sub-application instance is modified, so as to obtain an upgraded target application sub-instance. The at least one target sub-application instance is taken offline from the target application instance, while keeping other target sub-application instances online; The current configuration file is replaced by the upgrade configuration file; According to the replaced upgrade configuration file, a target application sub-instance is recreated, so as to upgrade the target application sub-instance.

7. The multi-application deployment method of claim 1, wherein, The multi-application deployment method further comprises: deploying, by the container cloud platform, an application package of the multi-application deployment tool; deploying, by the container cloud platform, application resources of the multi-application deployment tool based on the application package; generating, by the container cloud platform, an application instance of the multi-application deployment tool based on the application resources, and deploying, by the application instance, the multi-application deployment tool.

8. A multi-application deployment apparatus, characterized by comprising: The multi-application deployment apparatus comprises a processor and a memory, the memory stores program data, and the processor is configured to execute the program data to implement the multi-application deployment method of any one of claims 1 to 7.

9. A computer-readable storage medium, characterized in that, The computer readable storage medium is configured to store program data, and the program data, when executed by a processor, is configured to implement the multi-application deployment method of any one of claims 1 to 7.

Images