Container management method and device, equipment, medium and program product

Abstract

The invention provides a container management method and device, equipment, a medium and a program product, which can be applied to the fields of cloud computing and finance. The method comprises the steps that basic container model data and container service configuration data of a target container are read, the basic container model data comprise basic attribute information of the target container, and the container service configuration data comprise a side vehicle container label configured for the target container; according to the sidecar container label, obtaining target sidecar container configuration information corresponding to the sidecar container label from a predefined sidecar service directory; generating a target service deployment file determined for the target container according to the target side vehicle container configuration information and the basic container model data; and managing the target container based on the target service deployment file.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, specifically to the fields of cloud computing and finance, and more specifically to a container management method, device, equipment, medium and program product. Background Art

[0002] When releasing a container application into production, in addition to configuring the main business container, you must also manually configure sidecar containers such as security and operation and maintenance containers according to actual needs to implement non-business core auxiliary functions.

[0003] In the process of implementing the concept of the present disclosure, the inventors found that when there are many container services, a large number of repeated configurations will occur; and manual configuration of the sidecar container is time-consuming, labor-intensive, and prone to errors. Summary of the invention

[0004] In view of the above problems, the present disclosure provides a container management method, apparatus, device, medium and program product.

[0005] According to one aspect of the present disclosure, a container management method is provided, characterized in that the method includes: calling a first application program interface for transmitting container model data provided by a configuration management database, reading basic container model data and container service configuration data of a target container recorded in the configuration management database, wherein the basic container model data includes basic attribute information of the target container, and the container service configuration data includes a sidecar container label configured for the target container; in response to determining that a production release module has obtained the container service configuration data, obtaining target sidecar container configuration information corresponding to the sidecar container label from a predefined sidecar service directory according to the sidecar container label, and the sidecar service directory is pre-configured in the production release module; generating a target service deployment file determined for the target container according to the target sidecar container configuration information and the basic container model data; and calling a second application program interface for deploying a container service provided by a container cloud platform, so as to send the target service deployment file to the container cloud platform based on the second application program interface, and manage the target container based on the target service deployment file by using the container cloud platform.

[0006] According to an embodiment of the present disclosure, the container management method also includes: before obtaining the target sidecar container configuration information corresponding to the sidecar container label from a predefined sidecar service directory according to the sidecar container label, obtaining sidecar container function information used to configure the sidecar container; according to the standardized configuration rules represented by the sidecar container in the container service, converting the sidecar container function information into sidecar container configuration information that satisfies the standardized configuration rules; and building a sidecar service directory according to the sidecar container configuration information of multiple types of sidecar containers.

[0007] According to an embodiment of the present disclosure, the sidecar service directory includes multiple sidecar container names, each sidecar container name has sidecar container configuration information for configuring the sidecar container represented by the sidecar container name; according to the sidecar container label, obtaining the target sidecar container configuration information corresponding to the sidecar container label from the predefined sidecar service directory includes: according to the sidecar container name information to be configured represented by the sidecar container label, determining the target sidecar container name matching the sidecar container name information to be configured from the sidecar service directory; and reading the sidecar container configuration information under the target sidecar container name from the sidecar service directory to obtain the target sidecar container configuration information.

[0008] According to an embodiment of the present disclosure, generating a target service deployment file determined for a target container according to target sidecar container configuration information and basic container model data includes: generating an initial service deployment file of the target container according to the basic container model data, wherein basic attribute information is recorded in the initial service deployment file; and in response to the determined target sidecar container configuration information, injecting the target sidecar container configuration information into the initial service deployment file to obtain the target service deployment file.

[0009] According to an embodiment of the present disclosure, generating an initial service deployment file of a target container according to basic container model data includes: in response to receiving business container configuration information configured for the target container, generating an initial service deployment file according to the basic container model data and the business container configuration information.

[0010] Another aspect of the present disclosure provides a container management method, including: obtaining basic container model data and container service configuration data of a target container based on a configuration management database, wherein the basic container model data includes basic attribute information of the target container, and the container service configuration data includes a sidecar container label configured for the target container; and calling a first application program interface for transmitting container model data provided by the configuration management database, sending the basic container model data and the container service configuration data to a production release module, in response to determining that the production release module has obtained the container service configuration data, obtaining target sidecar container configuration information corresponding to the sidecar container label from a predefined sidecar service directory according to the sidecar container label, and generating a target service deployment file determined for the target container according to the target sidecar container configuration information and the basic container model data, and calling a second application program interface for deploying container services provided by a container cloud platform, so as to send the target service deployment file to the container cloud platform based on the second application program interface, and manage the target container based on the target service deployment file using the container cloud platform, wherein the sidecar service directory is pre-configured in the production release module.

[0011] According to an embodiment of the present disclosure, obtaining basic container model data and container service configuration data of a target container based on a configuration management database includes: calling a third application program interface provided by a container cloud platform for transmitting basic container model data, and reading the basic container model data of the target container from container data published by the container cloud platform; and generating container service configuration data related to the basic container model data in response to sidecar container label information received for the container service configuration represented by the basic container model data.

[0012] Another aspect of the present disclosure provides a container management method, including: in response to determining that a second application program interface for deploying a container service provided by a container cloud platform is called, based on the second application program interface, obtaining a target service deployment file determined for a target container, wherein the target service deployment file is generated by obtaining target sidecar container configuration information corresponding to the sidecar container label from a predefined sidecar service directory according to the sidecar container label by using a production release module, and based on the target sidecar container configuration information and the read basic container model data, the sidecar container label is determined according to the container service configuration data of the target container, the basic container model data includes basic attribute information of the target container, the basic container model data and the container service configuration data are read by calling a first application program interface for transmitting container model data provided by a configuration management database by using the production release module, the basic container model data and the container service configuration data of the target container are already recorded in the configuration management database, and the sidecar service directory is pre-configured in the production release module; and managing the target container based on the target service deployment file.

[0013] According to an embodiment of the present disclosure, managing a target container based on a target service deployment file includes: in response to determining that the target container is not published in a container cloud platform, deploying basic container service information of the target container in the container cloud platform according to basic container model data, wherein the basic container service information includes container scheduling instance information; and automatically injecting the target sidecar container configuration information into the container scheduling instance represented by the container scheduling instance information.

[0014] According to an embodiment of the present disclosure, managing a target container based on a target service deployment file includes: in response to determining that a target container has been published in a container cloud platform, and that target container information published by the target container in the container cloud platform does not include target sidecar container configuration information, automatically injecting the target sidecar container configuration information into a container scheduling instance of the target container.

[0015] Another aspect of the present disclosure provides a container management device, including: a container model data reading module, used to call a first application program interface for transmitting container model data provided by a configuration management database, and read basic container model data and container service configuration data of a target container recorded in the configuration management database, wherein the basic container model data includes basic attribute information of the target container, and the container service configuration data includes a sidecar container label configured for the target container; a target sidecar container configuration information acquisition module, used to obtain target sidecar container configuration information corresponding to the sidecar container label from a predefined sidecar service directory in response to determining that the production and release module has obtained the container service configuration data, according to the sidecar container label, and the sidecar service directory is pre-configured in the production and release module; a target service deployment file generation module, used to generate a target service deployment file determined for the target container according to the target sidecar container configuration information and the basic container model data; and a first container management module, used to call a second application program interface for deploying container services provided by a container cloud platform, so as to send the target service deployment file to the container cloud platform based on the second application program interface, and use the container cloud platform to manage the target container based on the target service deployment file.

[0016] Another aspect of the present disclosure provides a container management device, characterized in that the device includes: a container model data acquisition module, used to acquire basic container model data and container service configuration data of a target container based on a configuration management database, wherein the basic container model data includes basic attribute information of the target container, and the container service configuration data includes a sidecar container label configured for the target container; and a container model data sending module, used to call a first application program interface for transmitting container model data provided by the configuration management database, and send the basic container model data and the container service configuration data to the production release module, so as to obtain the target sidecar container configuration information corresponding to the sidecar container label from a predefined sidecar service directory in response to determining that the production release module has obtained the container service configuration data according to the sidecar container label, and generate a target service deployment file determined for the target container according to the target sidecar container configuration information and the basic container model data, and call a second application program interface for deploying container services provided by the container cloud platform, so as to send the target service deployment file to the container cloud platform based on the second application program interface, and manage the target container based on the target service deployment file using the container cloud platform, wherein the sidecar service directory is pre-configured in the production release module.

[0017] Another aspect of the present disclosure provides a container management device, characterized in that the device includes: a target service deployment file acquisition module, which is used to respond to determining that a second application program interface for deploying a container service provided by the container cloud platform is called, and based on the second application program interface, obtain a target service deployment file determined for a target container, wherein the target service deployment file is generated by using the commissioning and publishing module to obtain target sidecar container configuration information corresponding to the sidecar container label from a predefined sidecar service directory according to the sidecar container label, and based on the target sidecar container configuration information and the read basic container model data, the sidecar container label is determined according to the read container service configuration data of the target container, the basic container model data includes basic attribute information of the target container, the basic container model data and the container service configuration data are read by calling the first application program interface for transmitting container model data provided by the configuration management database using the commissioning and publishing module, the basic container model data and the container service configuration data of the target container are already recorded in the configuration management database, and the sidecar service directory is pre-configured in the commissioning and publishing module; and a second container management module, which is used to manage the target container based on the target service deployment file.

[0018] Another aspect of the present disclosure provides an electronic device, including: one or more processors; and a memory for storing one or more computer programs, wherein the one or more processors execute the one or more computer programs to implement the container management method of the present disclosure.

[0019] Another aspect of the present disclosure further provides a computer-readable storage medium on which a computer program or instruction is stored. When the computer program or instruction is executed by a processor, the container management method of the present disclosure is implemented.

[0020] Another aspect of the present disclosure further provides a computer program product, including a computer program or instructions, which implements the container management method of the present disclosure when the computer program or instructions are executed by a processor.

[0021] According to an embodiment of the present disclosure, because a first application program interface for transmitting container model data provided by a configuration management database is called, basic container model data and container service configuration data of the target container recorded in the configuration management database are read, wherein the basic container model data include basic attribute information of the target container, and the container service configuration data include a sidecar container label configured for the target container; in response to determining that the production release module has obtained the container service configuration data, according to the sidecar container label, the target sidecar container configuration information corresponding to the sidecar container label is obtained from a predefined sidecar service directory, and the sidecar service directory is pre-configured in the production release module; according to the target sidecar container configuration information and the basic container model data, a confirmation of the target container is generated. The target service deployment file is determined; and a second application program interface for deploying container services provided by the container cloud platform is called, so that the target service deployment file is sent to the container cloud platform based on the second application program interface, and the technical means for managing the target container based on the target service deployment file is used by the container cloud platform. By configuring the sidecar container label in the production and release module, formulating and maintaining the sidecar service directory, and automatically matching and automatically configuring the sidecar container, combined with the configuration management database and the container cloud platform architecture, the required auxiliary sidecar container can be automatically injected when the container application is put into production and released, making the production process more convenient and quick, reducing the labor cost, time and error risk of manually configuring the sidecar container, and improving the production efficiency of the container release. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The above contents and other purposes, features and advantages of the present disclosure will become more apparent through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:

[0023] Figure 1 The application scenario diagram of the container management method according to the embodiment of the present disclosure is schematically shown;

[0024] Figure 2 A system architecture diagram for implementing a container management system according to an embodiment of the present disclosure is schematically shown;

[0025] Figure 3 A flowchart of a container management method applied to a CMDB according to an embodiment of the present disclosure is schematically shown;

[0026] Figure 4 A flowchart of a container management method applied to a production release module according to an embodiment of the present disclosure is schematically shown;

[0027] Figure 5 The flowchart of the container management method applied to the container cloud platform according to the embodiment of the present disclosure is schematically shown;

[0028] Figure 6The overall flow chart of the container management method applied to the container management system according to the embodiment of the present disclosure is schematically shown;

[0029] Figure 7 A structural block diagram of a first container management device applied to a production release module according to an embodiment of the present disclosure is schematically shown;

[0030] Figure 8 A structural block diagram of a second container management device applied to CMDB according to an embodiment of the present disclosure is schematically shown;

[0031] Fig. 9 A structural block diagram schematically shows a third container management device applied to a container cloud platform according to an embodiment of the present disclosure; and

[0032] Fig.10 A block diagram of an electronic device suitable for implementing a container management method according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0033] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0034] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of the features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0035] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification and should not be interpreted in an idealized or overly rigid manner.

[0036] When using expressions such as "at least one of A, B, and C, etc.", they should generally be interpreted according to the meaning of the expression commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).

[0037] It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0038] Each sidecar container has more or less some configuration items such as environment variables, port configuration, configuration groups, volume mounts, etc.

[0039] In the process of implementing the concept of the present disclosure, the inventors found that since the configuration items corresponding to each sidecar container are generally fixed and belong to universal configurations, applicable to all container services, when there are many container services to be released for production, a large number of duplicate configurations will occur. Manual configuration of sidecar containers is time-consuming and labor-intensive, and prone to errors. The project team needs to pay attention to each configuration of the sidecar container and cannot fully focus on the business. The project team generally only pays attention to the main business container itself, and has little willingness to pay attention to security and operation and maintenance sidecar containers, resulting in time-consuming and labor-intensive promotion of security and operation and maintenance management and specifications.

[0040] Embodiments of the present disclosure provide a container management method, apparatus, device, medium and program product, the method comprising: calling a first application program interface for transmitting container model data provided by a configuration management database, reading basic container model data and container service configuration data of a target container recorded in the configuration management database, wherein the basic container model data comprises basic attribute information of the target container, and the container service configuration data comprises a sidecar container label configured for the target container; in response to determining that a production release module has obtained the container service configuration data, obtaining target sidecar container configuration information corresponding to the sidecar container label from a predefined sidecar service directory according to the sidecar container label, the sidecar service directory being pre-configured in the production release module; generating a target service deployment file determined for the target container according to the target sidecar container configuration information and the basic container model data; and calling a second application program interface for deploying a container service provided by a container cloud platform, so as to send the target service deployment file to the container cloud platform based on the second application program interface, and manage the target container based on the target service deployment file using the container cloud platform.

[0041] It should be noted that the container management method, device, equipment, medium and program product disclosed in the present invention can be used in cloud computing, finance and other fields, and can also be used in any field other than cloud computing, finance and other fields. The application field of the container management method, device, equipment, medium and program product disclosed in the present invention is not limited.

[0042] Figure 1 The application scenario diagram of the container management method according to the embodiment of the present disclosure is schematically shown.

[0043] like Figure 1 As shown, the application scenario 100 according to this embodiment may include a first terminal device 101, a second terminal device 102, a third terminal device 103, a network 104, and a server 105. The network 104 is used to provide a medium for a communication link between the first terminal device 101, the second terminal device 102, the third terminal device 103, and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or optical fiber cables, etc.

[0044] The user can use the first terminal device 101, the second terminal device 102, and the third terminal device 103 to interact with the server 105 through the network 104 to receive or send messages, etc. Various communication client applications can be installed on the first terminal device 101, the second terminal device 102, and the third terminal device 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only for example).

[0045] The first terminal device 101, the second terminal device 102, and the third terminal device 103 may be various electronic devices having display screens and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, and the like.

[0046] The server 105 may be a server that provides various services, such as a background management server (only as an example) that provides support for websites browsed by users using the first terminal device 101, the second terminal device 102, and the third terminal device 103. The background management server may analyze and process the received data such as user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal device.

[0047] It should be noted that the container management method provided in the embodiment of the present disclosure can generally be executed by the server 105. Accordingly, the container management device provided in the embodiment of the present disclosure can generally be set in the server 105. The container management method provided in the embodiment of the present disclosure can also be executed by a server or server cluster that is different from the server 105 and can communicate with the first terminal device 101, the second terminal device 102, the third terminal device 103 and / or the server 105. Accordingly, the container management device provided in the embodiment of the present disclosure can also be set in a server or server cluster that is different from the server 105 and can communicate with the first terminal device 101, the second terminal device 102, the third terminal device 103 and / or the server 105.

[0048] It should be understood that Figure 1The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0049] The following will be based on Figure 1 The scene described by Figure 2~Figure 3 The container management method of the disclosed embodiment is described in detail.

[0050] Figure 2 The system architecture diagram for implementing a container management system according to an embodiment of the present disclosure is schematically shown.

[0051] like Figure 2 As shown, the system architecture 200 may involve three systems, including: container cloud platform 210, CMDB (Configuration Management Database) 220, and production release module 230. The overall data flow is as follows: CMDB 220 synchronizes container model data from container cloud platform 210 and supports manual maintenance. Production release module 230 synchronizes container model data from CMDB 220. Production release module 230 executes container release, creates or modifies container services on container cloud platform 210, and runs service Pod (container scheduling) instances.

[0052] According to the embodiments of the present disclosure, CMDB can efficiently control and manage the ever-changing IT infrastructure and IT services by acquiring, maintaining, and checking business IT (Internet Technology) resources, and provide accurate configuration information for other systems such as task scheduling, operation and maintenance work orders, and release management systems. Figure 2 As shown, CMDB 220 may be responsible for maintaining container model data, including synchronizing basic container model data, maintaining basic container model data, and maintaining container service configuration data.

[0053] Figure 3 The flowchart of the container management method applied to CMDB according to the embodiment of the present disclosure is schematically shown.

[0054] like Figure 3 As shown, the method includes operations S310 to S320, and the container management method can be executed by the first terminal device 101, the second terminal device 102, the third terminal device 103 or the server 105.

[0055] In operation S310, basic container model data and container service configuration data of the target container are obtained based on the configuration management database, wherein the basic container model data includes basic attribute information of the target container, and the container service configuration data includes a sidecar container label configured for the target container.

[0056] According to an embodiment of the present disclosure, the basic attribute information represented by the basic container model data may include business system information, container cluster information, namespace information, container service information, Pod instance information, etc., and may not be limited thereto. Each business system may include one or more container clusters. Each container cluster may be deployed in one or more namespaces. Namespaces can be used to implement multi-tenant resource isolation. Namespaces "allocate" resource objects within the container cluster to different Namespaces to form logically grouped different projects, groups or user groups, so that different groups can be managed separately while sharing the resources of the entire cluster. Container service, i.e., container application, may refer to an application running on a container cluster, and each container service may contain one or more Pod instances. Pod is the smallest working unit and scheduling unit of Kubernetes (abbreviated as K8S, an open source containerized application). Each Pod may contain one or more containers. The containers in the Pod may be scheduled as a whole by the Master (K8S container cluster control node) to run on a Node (K8S container cluster workload node). Multiple Pods may run on a Node. A container represents the carrier that actually runs the application process. A Pod can have multiple containers and at least one application main container.

[0057] According to the embodiments of the present disclosure, the container service configuration data can be in the form of tags, indicating whether the container service needs to configure sa (a software program for implementing security management), apm (application monitoring program), fserver (file transfer program), jobexecutor (batch job scheduling execution program), etc. Sa, apm, fserver, jobexecutor, etc. can be run together with the business container in the form of a sidecar container to assist in implementing the security management related functions of the container service.

[0058] According to an embodiment of the present disclosure, for a new, unpublished container service, a user may manually maintain basic model data corresponding to the container service in, for example, a CMDB, including basic container model data and container service configuration data.

[0059] It should be noted that the user may also manually maintain the basic model data in other systems and directly read the basic model data from the CMDB, which is not limited here.

[0060] In operation S320, a first application programming interface for transmitting container model data provided by the configuration management database is called, and the basic container model data and the container service configuration data are sent to the production release module. In response to determining that the production release module has obtained the container service configuration data, the target sidecar container configuration information corresponding to the sidecar container label is obtained from the predefined sidecar service directory according to the sidecar container label, and a target service deployment file determined for the target container is generated according to the target sidecar container configuration information and the basic container model data, and a second application programming interface for deploying container services provided by the container cloud platform is called, so that the target service deployment file is sent to the container cloud platform based on the second application programming interface, and the target container is managed based on the target service deployment file using the container cloud platform, wherein the sidecar service directory is pre-configured in the production release module.

[0061] According to an embodiment of the present disclosure, CMDB may provide a first application program interface for transmitting container model data. In response to the first application program interface being called, CMDB may send basic container model data and container service configuration data to the production release module so that the production release module performs automatic injection of sidecar container configuration information and subsequent container management processes.

[0062] Through the above-mentioned embodiments of the present disclosure, a method for container application production release based on CMDB automatic configuration of sidecar containers is provided. Based on the container service configuration data, when the container application is put into production and released, the sidecar container that implements auxiliary functions can be automatically configured and injected, making the production process more convenient and quick, reducing the labor cost, time and error risk of manually configuring the sidecar container, and improving the production efficiency of container release.

[0063] In conjunction with specific embodiments, Figure 3 The method shown is described in further detail.

[0064] According to an embodiment of the present disclosure, the above operation S310 may include: calling a third application program interface provided by the container cloud platform for transmitting basic container model data, and reading the basic container model data of the target container from the container data published by the container cloud platform. In response to receiving the sidecar container label information for the container service configuration represented by the basic container model data, generating container service configuration data related to the basic container model data.

[0065] According to an embodiment of the present disclosure, the target container may include a container that has been published in the container cloud platform. In this case, the CMDB may, for example, provide a scheduled task and manual triggering to call a third application program interface provided by the container cloud platform to obtain the basic container model data of the target container that has been published on the container cloud platform.

[0066] According to an embodiment of the present disclosure, the basic container model data of the target container published on the container cloud platform may also be written into the middleware redis first, and the CMDB may also synchronously obtain the basic container model data from redis, which is not limited here.

[0067] According to an embodiment of the present disclosure, when basic container model data is obtained based on CMDB, a user may tag container service information in the basic container model data in CMDB to maintain container service configuration data of the corresponding container service.

[0068] Through the above-mentioned embodiments of the present disclosure, configuring the container service configuration data by labeling can facilitate the subsequent matching of the sidecar container and realize the automation of the sidecar container injection process.

[0069] According to the embodiments of the present disclosure, the production release system can represent an automated system for implementing application deployment, online release, daily change and operation and maintenance. Figure 2 As shown, the production release module 230 can be used to formulate and maintain the sidecar service directory, synchronize container model data, automatically match the sidecar service directory, inject the sidecar container configuration, and release the container.

[0070] Figure 4 The flowchart of the container management method applied to the production release module according to the embodiment of the present disclosure is schematically shown.

[0071] like Figure 4 As shown, the method includes operations S410 to S440, and the container management method can be executed by the first terminal device 101, the second terminal device 102, the third terminal device 103 or the server 105.

[0072] In operation S410, a first application program interface for transmitting container model data provided by the configuration management database is called to read basic container model data and container service configuration data of the target container recorded in the configuration management database, wherein the basic container model data includes basic attribute information of the target container, and the container service configuration data includes a sidecar container label configured for the target container.

[0073] According to the embodiments of the present disclosure, basic container model data and container service configuration data can be directly produced in the production and release module through manual configuration, or can be read from the CMDB by the production and release module, or can be read from the container cloud platform by the production and release module, without limitation here.

[0074] For example, the production release system can provide scheduled tasks and manual triggering to call the first application interface provided by CMDB to obtain container model data, including basic container model data and container service configuration data.

[0075] It should be noted that the container model data on the CMDB can also be written into the middleware redis first, and the production release system can also synchronously obtain the container model data from redis, which is not limited here.

[0076] In operation S420, in response to determining that the production release module has obtained the container service configuration data, according to the sidecar container label, the target sidecar container configuration information corresponding to the sidecar container label is obtained from a predefined sidecar service directory, and the sidecar service directory is pre-configured in the production release module.

[0077] According to an embodiment of the present disclosure, the sidecar container label may include at least one of the following: sa, apm, fserver, jobexecutor, etc., and may not be limited thereto. The sidecar service directory may include target sidecar container configuration information corresponding to each sidecar container label. Thus, when the container service configuration data is obtained based on the production release system, the corresponding sidecar service directory can be automatically matched.

[0078] In operation S430 , a target service deployment file determined for the target container is generated according to the target sidecar container configuration information and the basic container model data.

[0079] According to an embodiment of the present disclosure, the target service deployment file may include basic information of the target container to be deployed, such as container name information, service name information, namespace information, and sidecar container information of the target container, but may not be limited thereto.

[0080] In operation S440, a second application programming interface for deploying container services provided by the container cloud platform is called, so that the target service deployment file is sent to the container cloud platform based on the second application programming interface, and the target container is managed by the container cloud platform based on the target service deployment file.

[0081] According to an embodiment of the present disclosure, a service deployment file, also known as a service deployment description file, can define various details of container service deployment, such as at least one of the following: the name of the service to be deployed, the namespace in which it is located, the number of service replicas, the business main container configuration, the sidecar container configuration, the environment variables and other information. Each container service requires a corresponding service deployment file to implement deployment. Management may include operations such as creation and update, but is not limited to this.

[0082] For example, after obtaining the target service deployment file, you can create a target container or update an existing target container based on the information carried in the target service deployment file. This operation can be performed in the production release module, or it can be sent from the production release module to other modules, such as the container cloud platform, and executed on the container cloud platform, but it is not limited to this.

[0083] For example, the user can select the service deployment file generated based on the above method to perform the container publishing operation. When executing the container publishing operation, the service deployment API interface provided by the container cloud platform, that is, the second application program interface, can be called to deploy the container service.

[0084] Through the above-mentioned embodiments of the present disclosure, by configuring the sidecar container label, formulating and maintaining the sidecar service catalog, and automatically matching and automatically configuring the sidecar container, the required auxiliary sidecar container can be automatically injected when the container application is put into production and released, making the production process more convenient and quick, reducing the labor cost, time and error risk of manually configuring the sidecar container, and improving the production efficiency of the container release.

[0085] In conjunction with specific embodiments, Figure 4 The method shown is described in further detail.

[0086] According to an embodiment of the present disclosure, before performing the above operation S420, a sidecar service directory may be first constructed. The method may include: obtaining sidecar container function information for configuring the sidecar container. According to the standardized configuration rules represented by the sidecar container in the container service, the sidecar container function information is converted into sidecar container configuration information that satisfies the standardized configuration rules. According to the sidecar container configuration information of multiple types of sidecar containers, a sidecar service directory is constructed.

[0087] According to an embodiment of the present disclosure, the sidecar container function information may include, for example, environment variable information, access path information, mounted volume information, etc. of various sidecar containers, and may not be limited thereto. The standardized configuration rule may characterize the JSON structure or command line existence form of the sidecar container function information in the container service, and may not be limited thereto.

[0088] For example, a sidecar service catalog can be developed and maintained in advance in the production release system. Each sidecar service catalog can standardize and configure the corresponding sidecar container functions based on the above rules.

[0089] According to an embodiment of the present disclosure, a sidecar service directory may include multiple sidecar container names, and each sidecar container name may have sidecar container configuration information for configuring the sidecar container represented by the sidecar container name. The above operation S420 may include: according to the sidecar container name information to be configured represented by the sidecar container tag, determining a target sidecar container name matching the sidecar container name information to be configured from the sidecar service directory. Read the sidecar container configuration information under the target sidecar container name from the sidecar service directory to obtain the target sidecar container configuration information.

[0090] For example, if the container service configuration data includes a label that requires apm configuration, the production release system can automatically match the sidecar service directory based on the label to obtain the apm sidecar container configuration information that matches apm as the target sidecar container configuration information.

[0091] Through the above-mentioned embodiments of the present disclosure, by formulating and maintaining a standardized sidecar service catalog, in a way of automatically matching and automatically configuring the sidecar container, it is helpful to unify and promote security specifications, security management, operation and maintenance specifications and operation and maintenance management.

[0092] According to an embodiment of the present disclosure, the above operation S430 may include: generating an initial service deployment file of the target container according to the basic container model data, wherein the initial service deployment file records the basic attribute information. In response to the determined target sidecar container configuration information, the target sidecar container configuration information is injected into the initial service deployment file to obtain the target service deployment file.

[0093] According to an embodiment of the present disclosure, the initial deployment file may only record basic information such as the container corresponding cluster, container name, container namespace, etc.

[0094] For example, the production release module can first synchronize the container model data from the CMDB. When creating a service deployment file, the production release module can automatically match the sidecar service directory based on the container service configuration information in the container model data, and inject the corresponding sidecar container configuration into the service deployment file. Then, the service deployment file can be used to release the container.

[0095] According to an embodiment of the present disclosure, generating the initial service deployment file of the target container based on the basic container model data may include: in response to receiving business container configuration information configured for the target container, generating the initial service deployment file based on the basic container model data and the business container configuration information.

[0096] According to the embodiments of the present disclosure, the sidecar container is usually deployed in the same Pod as the main container of the business application (non-sidecar container), shares the same Namespace, shares the same life cycle, and provides auxiliary functions for the business container, such as script execution, log collection, application monitoring, etc. The business container, that is, the main container of the application, also known as the main container, is the carrier for running the core business logic process.

[0097] For example, a user can create a service deployment file corresponding to a container service based on the container model data obtained from the CMDB or middleware, and configure the configuration information related to the business container in the service deployment file.

[0098] On this basis, the production release system can automatically inject the target sidecar container configuration information corresponding to the target sidecar service directory into the service deployment file by modifying the service deployment file based on the matched target sidecar service directory. In this embodiment, these sidecar container configuration information and business container configuration information can also be combined to form a complete service deployment file.

[0099] Through the above-mentioned embodiments of the present disclosure, the sidecar container configuration under the matched sidecar service directory can be automatically added to the corresponding container service deployment file, thereby reducing the repetitive labor and error-prone problems of manual operations and improving deployment efficiency.

[0100] According to the embodiments of the present disclosure, the container cloud platform may refer to a cloud platform that provides container orchestration, storage, network, security and other services based on cloud computing technology and is used to provide containerized application deployment and operation and maintenance. Figure 2 As shown, the container cloud platform 210 can be used to create container services, run Pod instances, and generate business main containers and sidecar containers.

[0101] Figure 5 The flowchart of the container management method applied to the container cloud platform according to an embodiment of the present disclosure is schematically shown.

[0102] like Figure 5 As shown, the method includes operations S510 to S520, and the container management method can be executed by the first terminal device 101, the second terminal device 102, the third terminal device 103 or the server 105.

[0103] In operation S510, in response to determining that a second application program interface for deploying container services provided by the container cloud platform is called, based on the second application program interface, a target service deployment file determined for the target container is obtained, wherein the target service deployment file is generated by obtaining the target sidecar container configuration information corresponding to the sidecar container label from a predefined sidecar service directory according to the sidecar container label by using the commissioning and release module, and based on the target sidecar container configuration information and the read basic container model data. The sidecar container label is determined based on the container service configuration data of the target container, the basic container model data includes basic attribute information of the target container, the basic container model data and the container service configuration data are read by calling the first application program interface for transmitting container model data provided by the configuration management database by using the commissioning and release module, the basic container model data and the container service configuration data of the target container are already recorded in the configuration management database, and the sidecar service directory is pre-configured in the commissioning and release module.

[0104] In operation S520, a target container is managed based on the target service deployment file.

[0105] For example, after the service deployment API interface of the container cloud platform is called, the target service deployment file matched based on the production release module can be obtained, and the corresponding container service can be automatically generated on the container cloud platform, and the Pod instance corresponding to the container service can be run.

[0106] It should be noted that the specific implementation methods of other relevant features in this embodiment have been described in the previous embodiments and will not be repeated here.

[0107] According to an embodiment of the present disclosure, the above operation S520 may include: in response to determining that the target container is not published in the container cloud platform, deploying basic container service information of the target container in the container cloud platform according to the basic container model data, wherein the basic container service information includes container scheduling instance information. Automatically injecting the target sidecar container configuration information into the container scheduling instance represented by the container scheduling instance information.

[0108] According to an embodiment of the present disclosure, the above operation S520 may also include: in response to determining that the target container has been published in the container cloud platform, and the target container information published by the target container in the container cloud platform does not include the target sidecar container configuration information, automatically injecting the target sidecar container configuration information into the container scheduling instance of the target container.

[0109] For example, after the service deployment API interface provided by the container cloud platform is called by the production and release system, it can automatically create or modify the corresponding container service on the container cloud platform and run the Pod instance corresponding to the container service. In addition to the business main container main, each Pod instance can also automatically inject various sidecar containers matched in the production and release module, such as sa, apm and other containers, and is not limited to this.

[0110] Figure 6 The overall flow chart of the container management method applied to the container management system according to the embodiment of the present disclosure is schematically shown.

[0111] like Figure 6 As shown, the method includes operations S611 to S613 performed based on the CMDB 610 , operations S621 to S627 performed based on the production release module 620 , and operation S631 performed based on the container cloud platform 630 .

[0112] like Figure 6 As shown, it corresponds to CMDB 610.

[0113] In operation S611, basic container model data is manually maintained.

[0114] In operation S612 , basic container model data is synchronized from the container cloud platform 630 .

[0115] In operation S613 , based on the basic container model data obtained in operation S611 and / or S612 , container service configuration data is maintained and container service configuration data is generated.

[0116] According to an embodiment of the present disclosure, container model data may be constructed based on the basic container model data and container service configuration data obtained in the above operations S611 to S613 , and stored in the CMDB 610 .

[0117] like Figure 6 As shown, it corresponds to the production release module 620.

[0118] In operation S621 , a sidecar service catalog is formulated and maintained.

[0119] In operation S622 , the container model data is synchronized from the CMDB 610 .

[0120] In operation S623, a service deployment file is created based on the container model data obtained in operation S622.

[0121] In operation S624, based on the container model data obtained in operation S622, the sidecar service directory maintained in operation S621 is automatically matched.

[0122] In operation S625 , the sidecar configuration is automatically injected into the service deployment file created based on operation S623 .

[0123] It should be noted that the business container configuration may be deployed in the service deployment file by manual deployment.

[0124] In operation S626 , container publishing is performed.

[0125] In operation S627 , a service deployment API is called.

[0126] like Figure 6 As shown, it corresponds to the container cloud platform 630.

[0127] In operation S631, a container service is generated.

[0128] Through the above embodiments of the present disclosure, when the container application is put into production and released, the required auxiliary sidecar container is automatically injected into the same Pod where the main container of the container service is located, which makes the production process more convenient and faster, reduces the labor cost, time and error risk of manually configuring the sidecar container, and improves the production efficiency of container release. This method has the characteristics of automation, intelligence, efficiency, accuracy, and scalability.

[0129] Based on the above container management method, the present disclosure also provides a series of container management devices. Figures 7 to 9 The device is described in detail.

[0130] Figure 7 The structure block diagram of the first container management device applied to the production release module according to an embodiment of the present disclosure is schematically shown.

[0131] like Figure 7 As shown, the first container management device 700 of this embodiment includes a container model data reading module 710 , a target sidecar container configuration information acquisition module 720 , a target service deployment file generation module 730 and a first container management module 740 .

[0132] The container model data reading module 710 is used to call the first application program interface for transmitting container model data provided by the configuration management database, and read the basic container model data and container service configuration data of the target container recorded in the configuration management database, wherein the basic container model data includes basic attribute information of the target container, and the container service configuration data includes the sidecar container tag configured for the target container. In one embodiment, the container model data reading module 710 can be used to perform the operation S410 described above, which will not be repeated here.

[0133] The target sidecar container configuration information acquisition module 720 is used to obtain the target sidecar container configuration information corresponding to the sidecar container label from the predefined sidecar service directory according to the sidecar container label in response to determining that the production release module has obtained the container service configuration data. The sidecar service directory is pre-configured in the production release module. In one embodiment, the target sidecar container configuration information acquisition module 720 can be used to perform the operation S420 described above, which will not be repeated here.

[0134] The target service deployment file generation module 730 is used to generate a target service deployment file determined for the target container according to the target sidecar container configuration information and the basic container model data. In one embodiment, the target service deployment file generation module 730 can be used to perform the operation S430 described above, which will not be repeated here.

[0135] The first container management module 740 is used to call the second application program interface provided by the container cloud platform for deploying container services, so as to send the target service deployment file to the container cloud platform based on the second application program interface, and use the container cloud platform to manage the target container based on the target service deployment file. In one embodiment, the first container management module 740 can be used to perform the operation S440 described above, which will not be repeated here.

[0136] According to an embodiment of the present disclosure, the first container management device further includes a sidecar container function information acquisition module, a standardization module, and a sidecar service catalog construction module.

[0137] The sidecar container function information acquisition module is used to obtain the sidecar container function information used to configure the sidecar container.

[0138] The standardization module is used to convert the sidecar container function information into the sidecar container configuration information that meets the standardized configuration rules according to the standardized configuration rules displayed by the sidecar container in the container service.

[0139] The sidecar service directory building module is used to build a sidecar service directory according to the sidecar container configuration information of multiple types of sidecar containers.

[0140] According to an embodiment of the present disclosure, the sidecar service directory includes multiple sidecar container names, each of which has sidecar container configuration information for configuring the sidecar container represented by the sidecar container name. The target sidecar container configuration information acquisition module includes a target sidecar container name matching unit and a target sidecar container configuration information reading unit.

[0141] The target sidecar container name matching unit is used to determine a target sidecar container name that matches the sidecar container name information to be configured from the sidecar service directory according to the sidecar container name information to be configured represented by the sidecar container label.

[0142] The target sidecar container configuration information reading unit is used to read the sidecar container configuration information under the target sidecar container name from the sidecar service directory to obtain the target sidecar container configuration information.

[0143] According to an embodiment of the present disclosure, the target service deployment file generation module includes an initial service deployment file generation unit and a target sidecar container configuration information injection unit.

[0144] The initial service deployment file generation unit is used to generate an initial service deployment file of a target container according to basic container model data, wherein basic attribute information is recorded in the initial service deployment file.

[0145] The target sidecar container configuration information injection unit is used to inject the target sidecar container configuration information into the initial service deployment file in response to the determined target sidecar container configuration information to obtain the target service deployment file.

[0146] According to an embodiment of the present disclosure, the initial service deployment file generating unit includes a service container configuration subunit.

[0147] The business container configuration subunit is used to generate an initial service deployment file according to the basic container model data and the business container configuration information in response to receiving the business container configuration information configured for the target container.

[0148] Figure 8 The structural block diagram of the second container management device applied to CMDB according to an embodiment of the present disclosure is schematically shown.

[0149] like Figure 8 As shown, the second container management device 800 of this embodiment includes a container model data acquisition module 810 and a container model data sending module 820 .

[0150] The container model data acquisition module 810 is used to acquire the basic container model data and container service configuration data of the target container based on the configuration management database, wherein the basic container model data includes the basic attribute information of the target container, and the container service configuration data includes the sidecar container label configured for the target container. In one embodiment, the container model data acquisition module 810 can be used to perform the operation S310 described above, which will not be repeated here.

[0151] The container model data sending module 820 is used to call the first application program interface for transmitting container model data provided by the configuration management database, send the basic container model data and the container service configuration data to the production release module, and in response to determining that the production release module has obtained the container service configuration data, obtain the target sidecar container configuration information corresponding to the sidecar container label from the predefined sidecar service directory according to the sidecar container label, and generate a target service deployment file determined for the target container according to the target sidecar container configuration information and the basic container model data, and call the second application program interface for deploying the container service provided by the container cloud platform, so as to send the target service deployment file to the container cloud platform based on the second application program interface, and use the container cloud platform to manage the target container based on the target service deployment file, wherein the sidecar service directory is pre-configured in the production release module. In one embodiment, the container model data sending module 820 can be used to perform the operation S320 described above, which will not be repeated here.

[0152] According to an embodiment of the present disclosure, the container model data acquisition module includes a basic container model data reading unit and a container service configuration data generating unit.

[0153] The basic container model data reading unit is used to call the third application program interface provided by the container cloud platform for transmitting the basic container model data, and read the basic container model data of the target container from the container data published by the container cloud platform.

[0154] The container service configuration data generating unit is configured to generate container service configuration data related to the basic container model data in response to receiving the sidecar container label information for the container service configuration represented by the basic container model data.

[0155] Fig. 9 The structural block diagram of a third container management device applied to a container cloud platform according to an embodiment of the present disclosure is schematically shown.

[0156] like Fig. 9 As shown, the third container management device 900 of this embodiment includes a target service deployment file acquisition module 910 and a second container management module 920 .

[0157] The target service deployment file acquisition module 910 is used to obtain the target service deployment file determined for the target container based on the second application program interface in response to determining that the second application program interface for deploying the container service provided by the container cloud platform is called, wherein the target service deployment file is generated by using the commissioning and publishing module to obtain the target sidecar container configuration information corresponding to the sidecar container label from the predefined sidecar service directory according to the sidecar container label, and according to the target sidecar container configuration information and the read basic container model data, the sidecar container label is determined according to the read container service configuration data of the target container, the basic container model data includes the basic attribute information of the target container, the basic container model data and the container service configuration data are read by calling the first application program interface for transmitting the container model data provided by the configuration management database by the commissioning and publishing module, the basic container model data and the container service configuration data of the target container are already recorded in the configuration management database, and the sidecar service directory is pre-configured in the commissioning and publishing module. In one embodiment, the target service deployment file module 910 can be used to perform the operation S510 described above, which will not be repeated here.

[0158] The second container management module 920 is used to manage the target container based on the target service deployment file. In one embodiment, the second container management module 920 can be used to perform the operation S520 described above, which will not be described in detail here.

[0159] According to an embodiment of the present disclosure, the second container management module includes a basic container service information deployment unit and a first target sidecar container configuration information injection unit.

[0160] A basic container service information deployment unit is used to deploy the basic container service information of the target container in the container cloud platform according to the basic container model data in response to determining that the target container is not published in the container cloud platform, wherein the basic container service information includes container scheduling instance information.

[0161] The first target sidecar container configuration information injection unit is used to automatically inject the target sidecar container configuration information into the container scheduling instance represented by the container scheduling instance information.

[0162] According to an embodiment of the present disclosure, the second container management module includes a second target sidecar container configuration information injection unit.

[0163] The second target sidecar container configuration information injection unit is used to automatically inject the target sidecar container configuration information into the container scheduling instance of the target container in response to determining that the target container has been published in the container cloud platform and the target container information published by the target container in the container cloud platform does not include the target sidecar container configuration information.

[0164] According to an embodiment of the present disclosure, any multiple modules among the container model data reading module 710, the target sidecar container configuration information acquisition module 720, the target service deployment file generation module 730 and the first container management module 740, or the container model data acquisition module 810 and the container model data sending module 820, or the target service deployment file acquisition module 910 and the second container management module 920 can be combined into one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the container model data reading module 710, the target sidecar container configuration information acquisition module 720, the target service deployment file generation module 730 and the first container management module 740, or the container model data acquisition module 810 and the container model data sending module 820, or the target service deployment file acquisition module 910 and the second container management module 920 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware and firmware or in a suitable combination of any of them. Alternatively, at least one of the container model data reading module 710, the target sidecar container configuration information acquisition module 720, the target service deployment file generation module 730 and the first container management module 740, or the container model data acquisition module 810 and the container model data sending module 820, or the target service deployment file acquisition module 910 and the second container management module 920 can be at least partially implemented as a computer program module, which can perform corresponding functions when the computer program module is executed.

[0165] Fig.10 A block diagram of an electronic device suitable for implementing a container management method according to an embodiment of the present disclosure is schematically shown.

[0166] like Fig.10As shown, the electronic device 1000 according to an embodiment of the present disclosure includes a processor 1001, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage part 1008 to a random access memory (RAM) 1003. The processor 1001 may include, for example, a general-purpose microprocessor (such as a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (for example, an application-specific integrated circuit (ASIC)), etc. The processor 1001 may also include an onboard memory for caching purposes. The processor 1001 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0167] In RAM 1003, various programs and data required for the operation of electronic device 1000 are stored. Processor 1001, ROM 1002 and RAM 1003 are connected to each other via bus 1004. Processor 1001 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 1002 and / or RAM 1003. It should be noted that the program can also be stored in one or more memories other than ROM 1002 and RAM 1003. Processor 1001 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in the one or more memories.

[0168] According to an embodiment of the present disclosure, the electronic device 1000 may further include an input / output (I / O) interface 1005, which is also connected to the bus 1004. The electronic device 1000 may further include one or more of the following components connected to the input / output (I / O) interface 1005: an input portion 1006 including a keyboard, a mouse, etc.; an output portion 1007 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 1008 including a hard disk, etc.; and a communication portion 1009 including a network interface card such as a LAN card, a modem, etc. The communication portion 1009 performs communication processing via a network such as the Internet. A drive 1010 is also connected to the input / output (I / O) interface 1005 as needed. A removable medium 1011, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1010 as needed, so that a computer program read therefrom is installed into the storage portion 1008 as needed.

[0169] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present disclosure is implemented.

[0170] According to an embodiment of the present disclosure, a computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, may include but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, an apparatus or a device. For example, according to an embodiment of the present disclosure, a computer-readable storage medium may include the ROM 1002 and / or RAM 1003 described above and / or one or more memories other than ROM 1002 and RAM 1003.

[0171] The embodiment of the present disclosure also includes a computer program product, which includes a computer program, and the computer program contains program code for executing the method shown in the flowchart. When the computer program product is run in a computer system, the program code is used to enable the computer system to implement the container management method provided by the embodiment of the present disclosure.

[0172] The above functions defined in the system / device of the embodiment of the present disclosure are performed when the computer program is executed by the processor 1001. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0173] In one embodiment, the computer program may rely on tangible storage media such as optical storage devices, magnetic storage devices, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of signals on a network medium, and downloaded and installed through the communication part 1009, and / or installed from the removable medium 1011. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0174] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 1009, and / or installed from the removable medium 1011. When the computer program is executed by the processor 1001, the above functions defined in the system of the embodiment of the present disclosure are performed. According to the embodiment of the present disclosure, the system, device, means, module, unit, etc. described above can be implemented by a computer program module.

[0175] According to an embodiment of the present disclosure, the program code for executing the computer program provided by the embodiment of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, Java, C++, python, "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on the remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect through the Internet).

[0176] The flow charts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0177] It will be appreciated by those skilled in the art that the features described in the various embodiments of the present disclosure may be combined and / or combined in a variety of ways, even if such combinations or combinations are not explicitly described in the present disclosure. In particular, without departing from the spirit and teachings of the present disclosure, the features described in the various embodiments of the present disclosure may be combined and / or combined in a variety of ways. All of these combinations and / or combinations fall within the scope of the present disclosure.

[0178] The embodiments of the present disclosure are described above. However, these embodiments are only for illustrative purposes and are not intended to limit the scope of the present disclosure. Although the embodiments are described above, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. Without departing from the scope of the present disclosure, those skilled in the art may make a variety of substitutions and modifications, which should all fall within the scope of the present disclosure.

Claims

1. A container management method, characterized in that: The method comprises: Calling a first application program interface for transmitting container model data provided by the configuration management database, and reading basic container model data and container service configuration data of the target container recorded in the configuration management database, wherein the basic container model data includes basic attribute information of the target container, and the container service configuration data includes a sidecar container label configured for the target container; In response to determining that the production release module has obtained the container service configuration data, according to the sidecar container label, obtaining target sidecar container configuration information corresponding to the sidecar container label from a predefined sidecar service directory, wherein the sidecar service directory is pre-configured in the production release module; Generate a target service deployment file determined for the target container according to the target sidecar container configuration information and the basic container model data; and A second application programming interface for deploying container services provided by the container cloud platform is called, so that the target service deployment file is sent to the container cloud platform based on the second application programming interface, and the target container is managed by the container cloud platform based on the target service deployment file.

2. The method according to claim 1, characterized in that The method further includes: before acquiring target sidecar container configuration information corresponding to the sidecar container label from a predefined sidecar service directory according to the sidecar container label, Get the sidecar container capability information used to configure the sidecar container; According to the standardized configuration rules represented by the sidecar container in the container service, converting the sidecar container function information into sidecar container configuration information that satisfies the standardized configuration rules; and The sidecar service directory is constructed according to the sidecar container configuration information of multiple types of sidecar containers.

3. The method according to claim 1, characterized in that The sidecar service directory includes a plurality of sidecar container names, each of which has sidecar container configuration information for configuring the sidecar container represented by the sidecar container name; and acquiring, according to the sidecar container label, the target sidecar container configuration information corresponding to the sidecar container label from the predefined sidecar service directory includes: According to the sidecar container name information to be configured represented by the sidecar container tag, determining a target sidecar container name matching the sidecar container name information to be configured from the sidecar service directory; and The sidecar container configuration information under the target sidecar container name is read from the sidecar service directory to obtain the target sidecar container configuration information.

4. The method according to claim 1, characterized in that: The generating a target service deployment file determined for the target container according to the target sidecar container configuration information and the basic container model data comprises: generating an initial service deployment file of the target container according to the basic container model data, wherein the basic attribute information is recorded in the initial service deployment file; and In response to the target sidecar container configuration information being determined, the target sidecar container configuration information is injected into the initial service deployment file to obtain the target service deployment file.

5. The method according to claim 4, characterized in that The generating the initial service deployment file of the target container according to the basic container model data comprises: In response to receiving the business container configuration information configured for the target container, the initial service deployment file is generated according to the basic container model data and the business container configuration information.

6. A container management method, characterized in that: The method comprises: Acquire basic container model data and container service configuration data of the target container based on the configuration management database, wherein the basic container model data includes basic attribute information of the target container, and the container service configuration data includes a sidecar container label configured for the target container; and A first application programming interface for transmitting container model data provided by the configuration management database is called, and the basic container model data and the container service configuration data are sent to the production release module, in response to determining that the production release module has obtained the container service configuration data, according to the sidecar container label, the target sidecar container configuration information corresponding to the sidecar container label is obtained from the predefined sidecar service directory, and a target service deployment file determined for the target container is generated according to the target sidecar container configuration information and the basic container model data, and a second application programming interface for deploying container services provided by the container cloud platform is called, so as to send the target service deployment file to the container cloud platform based on the second application programming interface, and use the container cloud platform to manage the target container based on the target service deployment file, wherein the sidecar service directory is pre-configured in the production release module.

7. The method according to claim 6, characterized in that The step of obtaining the basic container model data and container service configuration data of the target container based on the configuration management database includes: Calling a third application programming interface provided by the container cloud platform for transmitting basic container model data, and reading the basic container model data of the target container from the container data published by the container cloud platform; and In response to receiving the sidecar container label information for the container service configuration represented by the basic container model data, container service configuration data related to the basic container model data is generated.

8. A container management method, characterized in that: The method comprises: In response to determining that a second application program interface for deploying a container service provided by the container cloud platform is called, based on the second application program interface, a target service deployment file determined for a target container is obtained, wherein the target service deployment file is generated by obtaining target sidecar container configuration information corresponding to the sidecar container label from a predefined sidecar service directory according to the sidecar container label by using the commissioning and publishing module, and according to the target sidecar container configuration information and the read basic container model data, the sidecar container label is determined according to the read container service configuration data of the target container, the basic container model data includes basic attribute information of the target container, the basic container model data and the container service configuration data are read by calling a first application program interface for transmitting container model data provided by a configuration management database by the commissioning and publishing module, the basic container model data and the container service configuration data of the target container are already recorded in the configuration management database, and the sidecar service directory is pre-configured in the commissioning and publishing module; and The target container is managed based on the target service deployment file.

9. The method according to claim 8, characterized in that The managing the target container based on the target service deployment file comprises: In response to determining that the target container is not published in the container cloud platform, deploying basic container service information of the target container in the container cloud platform according to the basic container model data, wherein the basic container service information includes container scheduling instance information; and The target sidecar container configuration information is automatically injected into the container scheduling instance represented by the container scheduling instance information.

10. The method according to claim 8, characterized in that The managing the target container based on the target service deployment file comprises: In response to determining that the target container has been published in the container cloud platform, and the target container information published by the target container in the container cloud platform does not include the target sidecar container configuration information, the target sidecar container configuration information is automatically injected into the container scheduling instance of the target container.

11. A container management device, characterized in that: The device comprises: A container model data reading module, configured to call a first application program interface for transmitting container model data provided by a configuration management database, and read basic container model data and container service configuration data of a target container recorded in the configuration management database, wherein the basic container model data includes basic attribute information of the target container, and the container service configuration data includes a sidecar container label configured for the target container; A target sidecar container configuration information acquisition module is configured to, in response to determining that the production release module has obtained the container service configuration data, acquire the target sidecar container configuration information corresponding to the sidecar container label from a predefined sidecar service directory according to the sidecar container label, wherein the sidecar service directory is pre-configured in the production release module; a target service deployment file generation module, configured to generate a target service deployment file determined for the target container according to the target sidecar container configuration information and the basic container model data; and The first container management module is used to call a second application program interface provided by the container cloud platform for deploying container services, so as to send the target service deployment file to the container cloud platform based on the second application program interface, and use the container cloud platform to manage the target container based on the target service deployment file.

12. A container management device, characterized in that: The device comprises: A container model data acquisition module, configured to acquire basic container model data and container service configuration data of a target container based on a configuration management database, wherein the basic container model data includes basic attribute information of the target container, and the container service configuration data includes a sidecar container label configured for the target container; and A container model data sending module is used to call a first application program interface for transmitting container model data provided by the configuration management database, and send the basic container model data and container service configuration data to the production release module, in response to determining that the production release module has obtained the container service configuration data, obtain the target sidecar container configuration information corresponding to the sidecar container label from a predefined sidecar service directory according to the sidecar container label, and generate a target service deployment file determined for the target container according to the target sidecar container configuration information and the basic container model data, and call a second application program interface for deploying container services provided by the container cloud platform, so as to send the target service deployment file to the container cloud platform based on the second application program interface, and use the container cloud platform to manage the target container based on the target service deployment file, wherein the sidecar service directory is pre-configured in the production release module.

13. A container management device, characterized in that: The device comprises: a target service deployment file acquisition module, configured to, in response to determining that a second application program interface for deploying a container service provided by the container cloud platform is called, acquire a target service deployment file determined for a target container based on the second application program interface, wherein the target service deployment file is generated by acquiring target sidecar container configuration information corresponding to the sidecar container label from a predefined sidecar service directory according to the sidecar container label by using the commissioning and publishing module, and according to the target sidecar container configuration information and the read basic container model data, wherein the sidecar container label is determined according to the read container service configuration data of the target container, the basic container model data includes basic attribute information of the target container, the basic container model data and the container service configuration data are read by calling a first application program interface for transmitting container model data provided by a configuration management database by the commissioning and publishing module, the basic container model data and the container service configuration data of the target container are already recorded in the configuration management database, and the sidecar service directory is pre-configured in the commissioning and publishing module; and The second container management module is used to manage the target container based on the target service deployment file.

14. An electronic device comprising: one or more processors; a memory for storing one or more computer programs, It is characterized in that the one or more processors execute the one or more computer programs to implement the steps of the method according to any one of claims 1 to 10.

15. A computer-readable storage medium having a computer program or instruction stored thereon, characterized in that: When the computer program or instruction is executed by a processor, the steps of the method according to any one of claims 1 to 10 are implemented.

16. A computer program product comprising a computer program or instructions, characterized in that When the computer program or instruction is executed by a processor, the steps of the method according to any one of claims 1 to 10 are implemented.

Images