WO2024113819A1 - Configuration method and apparatus for pod, device, and nonvolatile readable storage medium - Google Patents

Abstract

The present application relates to the technical field of containers, and discloses a configuration method and apparatus for a pod, a device, and a nonvolatile readable storage medium. An original service container template in a stateless controller is changed to be an initiation container template and a service application container template, and an adaptive parameter acquisition script is set in the initiation container template and used for automatically acquiring, in a pod to be created after an initiation container is first created, configuration parameters and generating a configuration file of said pod; a path of the configuration file is mounted in the service application container template, after a service application container is generated, the configuration file is acquired according to the path, and an application configuration is completed according to the configuration parameters. Differentiation of adaptive configuration parameters is implemented when a single stateless controller creates pods, and the pods in the same stateless controller in a k8s cluster can dynamically generate and load different configuration parameters according to the position where the pods are located, thus reducing application deployment complexity in k8s, and improving flexibility of containers in k8s.

Description

Container group configuration method, device, equipment and non-volatile readable storage medium

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to a Chinese patent application filed with the China Patent Office on November 30, 2022, with application number 202211518323.0 and application name “A method, device, equipment and readable storage medium for configuring a container group”, the entire contents of which are incorporated by reference in this application.

Technical Field

The present application relates to the field of container technology, and in particular to a configuration method, device, equipment and non-volatile readable storage medium for a container group.

Background technique

Kubernetes (also known as k8s) is an open source container cluster management system. Based on Docker (an open source container engine) technology, it provides a series of complete functions such as deployment and operation, resource scheduling, service discovery and dynamic scaling for containerized applications, improving the convenience of large-scale container cluster management.

As cloud native technology and the cloud market continue to mature, the complexity of applications managed by k8s will also increase. In the actual production process, for the k8s model that uses a stateless controller to create container groups through a unified template, there is a practical scenario problem that needs to be solved, that is, the differentiated adaptive parameter configuration problem of the container group.

Specifically, some programs in container groups need to have configuration information that matches their own operating environment. For example, when some programs run on nodes with multiple network cards, it is necessary to configure the network card address (ip, Internet Protocol) used; when some container groups run on nodes with graphics processing units (GPUs), additional GPU driver information needs to be configured, but not on ordinary nodes; when some container groups run on nodes with different hardware specifications, they need to adjust their own performance parameters such as the number of threads and super-resolution ratio according to the hardware configuration.

In this case, if the single container group template provided by the stateless controller or the default ConfigMap (configuration map) method of k8s is used to mount the configuration file for the container group, then all container groups created by the stateless controller will be mounted with the same configuration file, and the differentiated adaptive parameter configuration of the container group cannot be achieved. If you need to create container groups with different configurations, you can only use different stateless controllers to control them. For example, use Deployment A to control ordinary container groups and use Deployment B to control container groups on GPU nodes. On the one hand, this will increase the overall complexity of management. On the other hand, if there is another dimension of differentiated configuration, it is difficult to achieve orthogonal division between different stateless controllers. Finally, with the increase in the demand for differentiated configuration, for the deployment of multiple copies of the same application, as many differentiated configurations as there are stateless controllers are required to control them. This is similar to the traditional solution of specifying nodes for differentiated distribution, which loses the advantages of k8s dynamic scheduling and unified management.

If you use the method of binding different ConfigMaps to the stateless controller to achieve differentiated configuration for the container group under the same stateless controller, that is, as many ConfigMaps are bound to the stateless controller as there are differentiated configurations, a large amount of repetitive configuration code will appear, and the user side needs to change the business code in the business application container of the created container group to bind to different ConfigMaps, which will affect the business logic and make the implementation and management logic very troublesome. Moreover, the bound ConfigMap cannot be changed, which also loses the advantage of k8s dynamic scheduling.

Therefore, how to achieve differentiated adaptive configuration of container group parameters in a single stateless controller in a k8s cluster, so that the container group in the same stateless controller in the k8s cluster can dynamically generate and load different configuration parameters according to its own location, reduce the complexity of application deployment in k8s, and improve the flexibility of containers in k8s, is a technical problem that technical personnel in this field need to solve.

Summary of the invention

The purpose of this application is to provide a container group configuration method, device, equipment and non-volatile readable storage medium, which are used to realize differentiated adaptive configuration of container group parameters in a single stateless controller in a k8s cluster, so that the container group in the same stateless controller in the k8s cluster can dynamically generate and load different configuration parameters according to its own location, thereby reducing the complexity of application deployment in k8s and improving the flexibility of containers in k8s.

In order to solve the above technical problems, the present application provides a method for configuring a container group, which is applied to a node where a stateless controller is located, including:

After receiving the container group creation command, calling the preset initialization container template and the preset business application container template;

Using the initialization container template to create an initialization container for the container group, so that the initialization container runs the adaptive parameter acquisition script in the initialization container template to obtain configuration parameters and generate a configuration file for the container group;

A business application container is created for a container group using a business application container template, so that the business application container obtains a configuration file based on a path of the configuration file mounted in the business application container template, and completes application configuration according to configuration parameters.

Optionally, the configuration files are stored in the container group's temporary storage volume.

Optionally, the temporary storage volume is stored in the backend storage of the node where the container group is located.

Optionally, the temporary storage volume is stored in a temporary file system of the container group, and the temporary storage volume medium field of the temporary storage volume is defined as memory.

Optionally, the configuration file is stored in a shared storage space pre-allocated for the container group.

Optionally, initialize the container to obtain configuration parameters and generate a configuration file for the container group, including:

The initialization container obtains environment information of the node where the container group is located to determine the first configuration parameter;

The initialization container generates a configuration file according to the first configuration parameter.

Optionally, the initialization container obtains environment information of the node where the container group is located to determine the first configuration parameter, including:

The initialization container obtains environment information of the node where the container group is located based on the system directory of the node where the container group mounted in the initialization container template is located, so as to determine the first configuration parameter.

Optionally, the first configuration parameters include: system small computer system interface parameters, system control group parameters, and standard programming library module parameters.

Optionally, initialize the container to obtain configuration parameters and generate a configuration file for the container group, including:

The initialization container obtains environment information of the node where the container group is located to determine the first configuration parameter;

The initialization container obtains the address of the application configuration center recorded in the script based on the adaptive parameters, and uploads a configuration request including the first configuration parameter to the application configuration center;

The initialization container receives the second configuration parameter assigned by the application configuration center;

The initialization container generates a configuration file according to the first configuration parameter and the second configuration parameter.

Optionally, the second configuration parameter is one of a high performance configuration parameter, a high availability configuration parameter, a balanced configuration parameter, and a low power consumption configuration parameter.

Optionally, the second configuration parameter is an operation policy configuration parameter configured by an administrator and corresponding to the node where the container group is located.

Optionally, the second configuration parameter is an operation policy configuration parameter generated after calling a monitoring script to analyze the operation status of the node where the container group is located.

Optionally, the second configuration parameter is an operation policy configuration parameter periodically sent by the application configuration center after receiving the first configuration parameter.

Optionally, the second configuration parameter is an operation policy configuration parameter issued by the application configuration center after receiving the first configuration parameter when an operation state parameter of the node where the container group is located is monitored to change the operation state.

Optionally, the initialization container uploads a configuration request including the first configuration parameter to the application configuration center, including:

The initialization container periodically uploads configuration requests to the application configuration center.

Optionally, the initialization container uploads a configuration request including the first configuration parameter to the application configuration center, including:

After the first configuration parameter is changed, the initialization container uploads a configuration request including the changed first configuration parameter to the application configuration center.

Optionally, the business application container obtains the configuration file based on the path of the configuration file mounted in the business application container template, including:

The business application container obtains the configuration file based on the path of the configuration file written in the business configuration parameters of the business application container.

In order to solve the above technical problems, the present application also provides a container group configuration device, including:

The calling unit is configured to call a preset initialization container template and a preset Business application container template;

A first creation unit is configured to create an initialization container for the container group by using the initialization container template, so that the initialization container runs an adaptive parameter acquisition script in the initialization container template to acquire configuration parameters and generate a configuration file for the container group;

The second creation unit is configured to create a business application container for the container group using the business application container template, so that the business application container obtains the configuration file based on the path of the configuration file mounted in the business application container template, and completes the application configuration according to the configuration parameters.

In order to solve the above technical problems, the present application also provides a configuration device for a container group, including:

a memory arranged to store a computer program;

The processor is configured to execute a computer program, and when the computer program is executed by the processor, the steps of any of the above-mentioned methods for configuring a container group are implemented.

In order to solve the above technical problems, the present application also provides a non-volatile readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above container group configuration methods are implemented.

The configuration method of the container group provided in the present application changes the original business container template in the stateless controller to the initialization container template plus the business container template. The initialization container template is provided with an adaptive parameter acquisition script. In the container group to be created, after the initialization container is first created, the configuration parameters will be automatically acquired and the configuration file of the container group will be generated; the path of the configuration file is mounted in the business application container template. After the business application container is generated, the configuration file is acquired according to the path, and the application configuration is completed according to the configuration parameters. Differentiated adaptive configuration parameters are implemented when a single stateless controller creates a container group, so that the container group in the same stateless controller in the k8s cluster can dynamically generate and load different configuration parameters according to its own location, reducing the complexity of application deployment in k8s and improving the flexibility of containers in k8s.

The present application also provides a container group configuration device, equipment and non-volatile readable storage medium, which have the above-mentioned beneficial effects and are not described in detail here.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the embodiments of the present application or the technical solutions of the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

FIG1 is a flow chart of a method for configuring a container group provided in an embodiment of the present application;

FIG2 is a schematic diagram of a component deployment architecture provided in an embodiment of the present application;

FIG3 is a schematic diagram of the structure of a container group configuration device provided in an embodiment of the present application;

FIG. 4 is a schematic diagram of the structure of a container group configuration device provided in an embodiment of the present application.

Detailed ways

The core of this application is to provide a container group configuration method, device, equipment and non-volatile readable storage medium, which are used to realize differentiated adaptive configuration of container group parameters in a single stateless controller in a k8s cluster, so that the container group in the same stateless controller in the k8s cluster can dynamically generate and load different configuration parameters according to its own location, thereby reducing the complexity of application deployment in k8s and improving the flexibility of containers in k8s.

The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

FIG1 is a flow chart of a method for configuring a container group provided in an embodiment of the present application; FIG2 is a schematic diagram of a component deployment architecture provided in an embodiment of the present application.

As shown in FIG1 , the configuration method of the container group provided in the embodiment of the present application is applied to the node where the stateless controller is located, including:

S101: After receiving a container group creation command, calling a preset initialization container template and a preset business application container template.

S102: Create an initialization container for the container group using the initialization container template, so that the initialization container runs an adaptive parameter acquisition script in the initialization container template to acquire configuration parameters and generate a configuration file for the container group.

S103: Create a business application container for the container group using the business application container template, so that the business application container obtains the configuration file based on the path of the configuration file mounted in the business application container template, and completes the application configuration according to the configuration parameters.

In an optional implementation, the stateless controller is a controller component provided by k8s, running on a physical node in the container cluster. When providing services for business applications, the container groups (Pods) created by the stateless controller may also run on different physical nodes in the container cluster.

For S101, after the existing stateless controller uses a unified container group template to create a business application container, the business application container mounts the system directory required for the normal operation of the business application. However, in this way, multiple business application containers created by the stateless controller can only use the same configuration file. In the configuration method of the container group provided in the embodiment of the present application, the stateless controller that originally only had a business application container template is changed to an initialization container template and a business application container template. The first initialization container created in the container cluster obtains differentiated configuration parameters and generates configuration files for subsequently created business application containers to mount, thereby realizing differentiated configuration of different container groups. There is no need to mount ConfigMap, and it will not affect the business application logic.

Optionally, when creating a stateless load that requires differential configuration, use the k8s initialization container (Init- The container) mechanism is used to add an initialization container template to the container group template of the business application. The initialization template is mounted with a directory for writing configuration files, and is provided with an adaptive parameter acquisition script for acquiring configuration parameters to generate configuration files.

At the same time, the business application container template is modified to mount the directory where the configuration files are written to the business application container template, so that the created business application container can obtain differentiated configuration files.

For S102, the initialization container is the first container created in the container group mechanism of k8s, so it can be guaranteed that the initialization container runs before the business application container. After the initialization container is created, the adaptive parameter acquisition script is run to adaptively obtain the required configuration parameters according to the pre-written logic. For example, the initialization container obtains the configuration parameters and generates the configuration file of the container group, which may include: the initialization container obtains the environmental information of the node where the container group is located to determine the first configuration parameter; the initialization container generates the configuration file according to the first configuration parameter.

The initialization container obtains the environment information of the node where the container group is located to determine the first configuration parameter. The initialization container may obtain the environment information of the node where the container group is located based on the system directory of the node where the container group is located mounted in the initialization container template to determine the first configuration parameter.

That is, in the initialization container template, not only the directory pre-allocated for the configuration file is mounted, but also the system directory is mounted, and the running logic of the adaptive parameter acquisition script is set to determine the environment information of the node according to the system directory of the node where the container group where the initialization container is located is located, and then generate the configuration file.

The initialization container template is pre-mounted with directories for obtaining system information necessary for generating configuration files, which may include /etc/iscsi (system small computer system interface directory), /sys/fs/cgroup (system control group directory), /lib/modules (standard programming library module directory), etc. The first configuration parameters thus obtained may include: system small computer system interface parameters, system control group parameters, standard programming library module parameters, etc.

In order to implement the process of creating an initialization container and running an adaptive parameter acquisition script to generate a configuration file in S102, in the stateless controller, an initialization container template and a business application container template are added to the stateless load template that needs to dynamically generate a differentiated configuration, and its internal main logic includes at least:

Mount the directories required for dynamic configuration generation, such as /etc/iscsi (system small computer system interface directory), /sys/fs/cgroup (system control group directory), /lib/modules (standard programming library module directory), etc.

Mount the directory pre-allocated for the configuration file to write the generated configuration file and mount it as a shared volume for use in the business application container;

Develop business logic and automatically generate the required configuration files based on the information of the node where the container group is located;

Write the configuration file to a directory pre-allocated for configuration files.

The directory pre-allocated for the configuration file may be stored in a shared storage space pre-allocated for the container group. The shared storage space may come from any backend storage of the node where the container group is located, or other remote storage resources.

In addition to running the adaptive parameter acquisition script to generate the configuration file after the initialization container is created, the adaptive parameter acquisition script can also be designed to update the configuration parameters and the configuration file during the operation of the container group if the information source for obtaining the configuration parameters changes. For example, the first configuration parameter of the attribute of the node is obtained by mounting the system directory of the node. As the parameters in the system directory are updated, the first configuration parameter is adapted to the change and the configuration file is updated. After the container group is migrated, the system directory of the migrated node is obtained according to the system directory path, and the first configuration parameter is updated and the configuration file is updated.

For S103, according to the k8s mechanism, in the container group created by the stateless controller, the business application container is created after the initialization container, and according to the preset business application container template that mounts a directory pre-allocated for the configuration file, the created business application container is mounted to the directory pre-allocated for the configuration file. In this way, the configuration file created after the initialization container is started can be read through the shared volume directory to configure the business application according to the configuration file.

In S103, the business application container obtains the configuration file based on the path of the configuration file mounted in the business application container template. This may be: the business application container obtains the configuration file based on the path of the configuration file written in the business configuration parameters of the business application container.

Since the business application and the initialization configuration file process use different containers, the system directories required by each can be mounted separately. The business application container does not need to mount the system directory mounted simply for generating configuration files, preventing potential unauthorized access risks. The business application itself does not need to be modified, and there is no intrusion into the business application code.

As shown in Figure 2, the node 201 where the stateless controller is located is recorded as node 1, the node 202 where the container group 1 created by the stateless controller is located is recorded as node 2, and the node 203 where the container group 2 created by the stateless controller is located is recorded as node 3. Assume that node 2 is a node with an 8-core 32G CPU (Central Processing Unit) and a GPU, and node 3 is a node with an 8-core 32G CPU and a large page memory. Applying the configuration method of the container group provided in the embodiment of the present application, the stateless controller calls the preset initialization container template and the preset business application container template after running, and creates container group 1 and container group 2 in node 2 and node 3 respectively. In the container group 1 of node 2, the initialization container in container group 1 is first created. After the initialization container is created, the adaptive parameter acquisition script is run in node 2 to create configuration file 1 according to the properties of node 2, and then a business application container is created. The business application container and the initialization container mount the directory where the configuration file is located. After the business application container is created, the configuration file 1 is read. In container group 2 of node 3, the initialization container in container group 2 is first created. After the initialization container is created, the adaptive parameter acquisition script is run on node 3 to create configuration file 2 according to the properties of node 3, and then the business application container is created. The business application container and the initialization container mount the directory where the configuration file is located. After the business application container is created, the configuration file 2 is read. Through the differentiation of configuration file 1 and configuration file 2, the differentiated configuration of the business application of container group 1 and the business application of container group 2 is realized, and it can automatically adapt to the characteristics of the environment to which it belongs. When the container group is re-created or migrated, it can still adaptively obtain configuration parameters to achieve differentiated configuration.

The configuration method of the container group provided in the embodiment of the present application changes the original business container template in the stateless controller to the initialization container template plus the business container template. The initialization container template is provided with an adaptive parameter acquisition script. In the container group to be created, after the initialization container is first created, the configuration parameters will be automatically acquired and the configuration file of the container group will be generated; the path of the configuration file is mounted in the business application container template. After the business application container is generated, the configuration file is acquired according to the path, and the application configuration is completed according to the configuration parameters. Differentiated adaptive configuration parameters are implemented when a single stateless controller creates a container group, so that the container group in the same stateless controller in the k8s cluster can dynamically generate and load different configuration parameters according to its own location, reducing the complexity of application deployment in k8s and improving the flexibility of containers in k8s.

On the basis of the above embodiment, in order to facilitate container management of configuration files and container groups, in the configuration method of the container group provided in the embodiment of the present application, the temporary storage volume (emptyDir) of the container group is used as the directory for writing configuration files. Then, in S102, the configuration file is stored in the temporary storage volume of the container group.

As the name implies, emptyDir is an empty directory, and its life cycle is exactly the same as the container group to which it belongs. emptyDir can share files generated in a work project between different containers in the same container group. A volume of type emptyDir is created when a container group is assigned to a node. k8s will automatically assign a directory on the node, so there is no need to specify the corresponding directory file on the host node. The initial content of this directory is empty. When the container group is removed from the node, the data in emptyDir will be permanently deleted. And a container crash will not cause the data in emptyDir to be deleted.

In the embodiment of the present application, a temporary storage volume emptyDir is used to store the configuration file adaptively generated by the container group. The temporary storage volume emptyDir has the same life cycle as the container group to which it belongs, which facilitates management.

By default, emptyDir can use any type of backend storage provided by the node. In the configuration method of the container group provided in the embodiment of the present application, the temporary storage volume can be stored in the backend storage of the node where the container group is located. In this way, the temporary storage volume occupies the memory resources of the node where the container group is located.

In special scenarios, the temporary file system (tmpfs) of the container group can also be used as the available storage resource of emptyDir. The temporary storage volume can also be stored in the temporary file system of the container group, and the temporary storage volume medium (emptyDir.medium) field of the temporary storage volume is defined as memory. In this setting, the volume where the configuration file is located will consume the memory share of the container, but as a temporary file, it can be accessed externally to obtain the configuration information of the container group to implement the monitoring function.

On the basis of the above embodiment, in order to configure more complex configuration parameters for a container group under a single stateless controller, such as operation policy parameters, in the configuration method of a container group provided in an embodiment of the present application, initializing a container to obtain configuration parameters and generating a configuration file for the container group may include:

The initialization container obtains environment information of the node where the container group is located to determine the first configuration parameter;

The initialization container obtains the address of the application configuration center recorded in the script based on the adaptive parameters, and uploads a configuration request including the first configuration parameter to the application configuration center;

The initialization container receives the second configuration parameter assigned by the application configuration center;

The initialization container generates a configuration file according to the first configuration parameter and the second configuration parameter.

In an optional implementation, for application configuration files with higher loads that cannot be generated by the application itself based on system information, or that require more complex logical judgments, a service of an application configuration center can be designed. When the initialization container starts, it can obtain the current information of the node where it is located, initiate a request to the application configuration center as needed, obtain the configuration parameters dynamically calculated by the application configuration center, generate the required configuration files, and write them into the directory pre-allocated for the configuration files.

Deploy the application configuration center in the container cluster where the business applications that need to dynamically form differentiated configurations are located. The application configuration center can run on another node other than the node where the stateless controller is located and the node where the container group is located, such as the monitoring node.

The adaptive parameter acquisition script in the initialization container template is designed to obtain the attributes of the node as the first configuration parameter, and then upload the node information including the first configuration parameter to the application configuration center to obtain the second configuration parameter assigned by the application configuration center. The initialization container generates a configuration file based on the first configuration parameter and the second configuration parameter.

Then, in the initialization container template of the stateless controller, in addition to the internal main logic provided in the first embodiment of the present application, it also includes:

Develop business logic, carry node information, access the application configuration center of the container cluster, and the application configuration center obtains the second configuration parameter and returns it to the initialization container;

A configuration file is generated according to the first configuration parameter and the second configuration parameter, and is written into a directory pre-allocated for the configuration file.

The first configuration parameter is mainly system information of the node where the container group is located, which may include: system small computer system interface parameters, system control group parameters, standard programming library module parameters, etc.

The second configuration parameter may be an operation strategy configuration parameter, that is, a configuration parameter corresponding to an operation strategy divided according to the operation status of the node where the container group is located. The second configuration parameter may be one of: a high performance configuration parameter, a high availability configuration parameter, a balanced configuration parameter, and a low power consumption configuration parameter.

The second configuration parameter can be an operation policy configuration parameter corresponding to the node where the container group is located, configured by the administrator. Since the determination of the operation policy configuration parameter is relatively complex, the application configuration center can only serve as a platform for administrators to manage container groups, displaying the first configuration parameters of the nodes where different container groups are located on the platform for administrators to view, and the administrators can assign the second configuration parameters based on experience.

Optionally, an interface can be pre-developed in the application configuration center to allow system administrators to configure default configuration file templates for each application, such as high-performance templates, high-availability templates, balanced templates, low-power templates, etc. The administrator configures the policy and automatically analyzes the comprehensive level of the node where the container group is located through the request information from the container group, and selects the appropriate template for deployment. The line is issued.

It should be noted that the application configuration center needs to obtain the first configuration parameters of the node where the container group is located before learning the information of the node where the container group is located, and then assigning the second configuration parameters. However, according to the needs of the node where the container group is located, after the second configuration parameters are assigned for the first time, the node where the container group is located can upload the first configuration parameters on demand, and the node where the application configuration center is located can also issue the second configuration parameters according to the preset rules.

Then, in S102, the initialization container uploads the configuration request including the first configuration parameter to the application configuration center, which may be: the initialization container periodically uploads the configuration request to the application configuration center. That is, the initialization container may send the configuration request carrying the first configuration parameter to the application configuration center every first period, so that the application configuration center can confirm whether the second configuration parameter of the container group needs to be updated.

Alternatively, the initialization container uploading the configuration request including the first configuration parameter to the application configuration center in S102 may be: after the first configuration parameter is changed, the initialization container uploads the configuration request including the changed first configuration parameter to the application configuration center. That is, after the initialization container obtains the first configuration parameter just after being created, it monitors the change of the first configuration parameter, and after finding that the first configuration parameter has changed, it sends the configuration request carrying the first configuration parameter to the application configuration center, so that the application configuration center reallocates the second configuration parameter corresponding to the updated first configuration parameter.

As shown in Figure 2, the node 204 where the application configuration center is located is node 4. After the initialization container of container group 1 running on node 2 is created, the first configuration parameter of container group 1 is uploaded to the application configuration center, and the application configuration center sends the second configuration parameter to the initialization container. The initialization container of container group 1 generates configuration file 1 according to the first configuration parameter and the second configuration parameter. After the initialization container of container group 2 running on node 3 is created, the first configuration parameter of container group 2 is uploaded to the application configuration center, and the application configuration center sends the second configuration parameter to the initialization container. The initialization container of container group 2 generates configuration file 2 according to the first configuration parameter and the second configuration parameter. Through the application configuration center, complex differentiation between container group 1 and container group 2 is achieved.

The configuration method of the container group provided in the embodiment of the present application designs an application configuration center, designs the initialization container to upload the acquired first configuration parameters to the application configuration center after startup, the application configuration center assigns the second configuration parameters to the container group, and the initialization container generates a configuration file according to the first configuration parameters and the second configuration parameters, so that dynamic configuration can be performed according to the running status of the node, further improving the flexibility of the adaptive parameter configuration of the container group in a single stateless controller.

On the basis of the above embodiments, in the configuration method of the container group provided in the embodiment of the present application, the automatic allocation of the second configuration parameter can be realized based on the application configuration center. The application configuration center can be designed to automatically determine the second configuration parameter for the container group after analyzing the running status of the node where the container group is located based on the monitoring system. The second configuration parameter can be the running policy configuration parameter generated after calling the monitoring script to analyze the running status of the node where the container group is located.

In an optional implementation, the interface of the application configuration center is developed to connect to the monitoring system of the k8s cluster for dynamic perception. The current overall load level, business traffic, cluster size, etc. of the cluster provide a reference for dynamically generating configuration file content fields.

By connecting to the monitoring system of the k8s cluster, the application configuration center combines the first configuration parameters of the node where the initialization container is uploaded and the operating status of the node where the container group is located obtained by the monitoring system. It makes an automated comprehensive decision through more abundant performance parameters, dynamically generates the second configuration parameters that are most suitable for the container group, and distributes them.

In the above embodiment, it is mentioned that after the second configuration parameter is allocated for the first time, the node where the container group is located can upload the first configuration parameter as needed, and the node where the application configuration center is located can also send the second configuration parameter according to the preset rules. In the configuration method of the container group provided in the embodiment of the present application, the second configuration parameter can be the operation policy configuration parameter periodically sent by the application configuration center after receiving the first configuration parameter. That is, after receiving the first configuration parameter, the application configuration center can generate and send the second configuration parameter based on the operation status of the node where the container group is located and the first configuration parameter of the container group every second period.

Alternatively, the second configuration parameter may be an operation policy configuration parameter issued by the application configuration center after receiving the first configuration parameter when the operation status parameter of the node where the container group is located is monitored to change the operation status. That is, after receiving the first configuration parameter, the application configuration center determines whether it is necessary to update the second configuration parameter assigned to the container group based on the operation status of the node where the container group is located provided by the monitoring system and the first configuration parameter on a regular or real-time basis, and then issues the second configuration parameter to the node where the container group is located after updating the second configuration parameter.

The configuration method of the container group provided in the embodiment of the present application is to connect the application configuration center that provides operation strategy configuration parameters to the monitoring system of the k8s cluster by designing, so as to realize the operation status of the node where the container group is located and the first configuration parameters to generate the operation strategy configuration parameters for the container group, thereby improving the intelligence level of the adaptive parameter configuration of the container group in a single stateless controller.

The above describes in detail various embodiments corresponding to the method for configuring a container group. On this basis, the present application also discloses a container group configuration device, equipment and non-volatile readable storage medium corresponding to the above method.

FIG3 is a schematic diagram of the structure of a container group configuration device provided in an embodiment of the present application.

As shown in FIG3 , the configuration device of the container group provided in the embodiment of the present application includes:

The calling unit 301 is configured to call a preset initialization container template and a preset business application container template after receiving a container group creation command;

The first creation unit 302 is configured to create an initialization container for the container group by using the initialization container template, so that the initialization container runs an adaptive parameter acquisition script in the initialization container template to obtain configuration parameters and generate a configuration file for the container group;

The second creation unit 303 is configured to create a business application container for the container group using the business application container template, so that the business application container obtains the configuration file based on the path of the configuration file mounted in the business application container template, and Complete the application configuration.

Since the embodiments of the apparatus part correspond to the embodiments of the method part, please refer to the description of the embodiments of the method part for the embodiments of the apparatus part, which will not be repeated here.

FIG. 4 is a schematic diagram of the structure of a container group configuration device provided in an embodiment of the present application.

As shown in FIG4 , the configuration device of the container group provided in the embodiment of the present application includes:

A memory 410 configured to store a computer program 411;

The processor 420 is configured to execute the computer program 411. When the computer program 411 is executed by the processor 420, the steps of the method for configuring a container group in any one of the above embodiments are implemented.

Among them, the processor 420 may include one or more processing cores, such as a 3-core processor, an 8-core processor, etc. The processor 420 may be implemented in at least one hardware form of a digital signal processing DSP (Digital Signal Processing), a field-programmable gate array FPGA (Field-Programmable Gate Array), and a programmable logic array PLA (Programmable Logic Array). The processor 420 may also include a main processor and a coprocessor. The main processor is a processor for processing data in the awake state, also known as a central processing unit CPU (Central Processing Unit); the coprocessor is a low-power processor for processing data in the standby state. In some embodiments, the processor 420 may be integrated with a graphics processor GPU (Graphics Processing Unit), and the GPU is responsible for rendering and drawing the content that needs to be displayed on the display screen. In some embodiments, the processor 420 may also include an artificial intelligence AI (Artificial Intelligence) processor, which is used to process computing operations related to machine learning.

The memory 410 may include one or more non-volatile readable storage media, which may be non-transitory. The memory 410 may also include a high-speed random access memory, and a non-volatile memory, such as one or more disk storage devices, flash memory storage devices. In this embodiment, the memory 410 is at least configured to store the following computer program 411, wherein the computer program 411, after being loaded and executed by the processor 420, can implement the relevant steps in the configuration method of the container group disclosed in any of the aforementioned embodiments. In addition, the resources stored in the memory 410 may also include an operating system 412 and data 413, etc., and the storage method may be temporary storage or permanent storage. Among them, the operating system 412 may be Windows. Data 413 may include, but is not limited to, the data involved in the above method.

In some embodiments, the configuration device of the container group may further include a display screen 430 , a power supply 440 , a communication interface 450 , an input and output interface 460 , a sensor 470 , and a communication bus 480 .

Those skilled in the art will appreciate that the structure shown in FIG. 4 does not constitute a limitation on the configuration device of the container group, and may include more or fewer components than those shown in the figure.

The container group configuration device provided in the embodiment of the present application includes a memory and a processor. When the processor executes the program stored in the memory, it can implement the above container group configuration method, and the effect is the same as above.

It should be noted that the above-described device and equipment embodiments are merely schematic. For example, the division of modules is merely a logical function division. There may be other division methods in actual implementation, such as multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, indirect coupling or communication connection of devices or modules, which may be electrical, mechanical or other forms. The modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment.

In addition, each functional module in each embodiment of the present application can be integrated into a processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The above integrated modules can be implemented in the form of hardware or software functional modules.

If the integrated module is implemented in the form of a software function module and sold or used as an independent product, it can be stored in a non-volatile readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a non-volatile readable storage medium to execute all or part of the steps of the various embodiments of the present application.

To this end, an embodiment of the present application further provides a non-volatile readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the container group configuration method are implemented.

The non-volatile readable storage medium may include: a U disk, a mobile hard disk, a read-only memory ROM (Read-Only Memory), a random access memory RAM (Random Access Memory), a magnetic disk or an optical disk, and other media that can store program codes.

The computer program included in the non-volatile readable storage medium provided in this embodiment can implement the steps of the above container group configuration method when executed by the processor, and the effect is the same as above.

The above is a detailed introduction to a configuration method, device, equipment and non-volatile readable storage medium of a container group provided by the present application. The various embodiments in the specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same and similar parts between the embodiments can be referred to each other. For the devices, equipment and non-volatile readable storage medium disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the description is relatively simple, and the relevant parts can be referred to the method part description. It should be pointed out that for ordinary technicians in this technical field, without departing from the principles of the present application, several improvements and modifications can be made to the present application, and these improvements and modifications also fall within the scope of protection of the claims of the present application.

It should also be noted that, in this specification, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the statement "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

Claims (20)

A method for configuring a container group, characterized in that it is applied to a node where a stateless controller is located, and includes: After receiving the container group creation command, calling the preset initialization container template and the preset business application container template; Using the initialization container template to create an initialization container for the container group, so that the initialization container runs the adaptive parameter acquisition script in the initialization container template to obtain configuration parameters and generate a configuration file for the container group; The business application container template is used to create a business application container for the container group, so that the business application container obtains the configuration file based on the path of the configuration file mounted in the business application container template, and completes the application configuration according to the configuration parameters. The configuration method according to claim 1, characterized in that the configuration file is stored in a temporary storage volume of the container group. The configuration method according to claim 2 is characterized in that the temporary storage volume is stored in the backend storage of the node where the container group is located. The configuration method according to claim 2 is characterized in that the temporary storage volume is stored in a temporary file system of the container group, and the temporary storage volume media field of the temporary storage volume is defined as memory. The configuration method according to claim 1 is characterized in that the configuration file is stored in a shared storage space pre-allocated to the container group. The configuration method according to claim 1, wherein the initialization container obtains the configuration parameters and generates a configuration file for the container group, comprising: The initialization container obtains environment information of the node where the container group is located to determine a first configuration parameter; The initialization container generates the configuration file according to the first configuration parameters. The configuration method according to claim 6, wherein the initialization container obtains the environment information of the node where the container group is located to determine the first configuration parameter, including: The initialization container obtains environment information of the node where the container group is located based on the system directory of the node where the container group is located that is mounted in the initialization container template, so as to determine the first configuration parameter. The configuration method according to claim 6 is characterized in that the first configuration parameters include: system small computer system interface parameters, system control group parameters, and standard programming library module parameters. The configuration method according to claim 1, wherein the initialization container obtains the configuration parameters and generates a configuration file for the container group, comprising: The initialization container obtains environment information of the node where the container group is located to determine a first configuration parameter; The initialization container obtains the application configuration center address recorded in the script based on the adaptive parameters, and sends the application configuration The configuration center uploads a configuration request including the first configuration parameters; The initialization container receives a second configuration parameter allocated by the application configuration center; The initialization container generates the configuration file according to the first configuration parameter and the second configuration parameter. The configuration method according to claim 9 is characterized in that the second configuration parameter is one of a high performance configuration parameter, a high availability configuration parameter, a balanced configuration parameter, and a low power consumption configuration parameter. The configuration method according to claim 9, wherein the second configuration parameter is an operation policy configuration parameter configured by an administrator and corresponding to the node where the container group is located. The configuration method according to claim 9, characterized in that the second configuration parameter is an operation strategy configuration parameter generated after calling a monitoring script to analyze the operation status of the node where the container group is located. The configuration method according to claim 9 is characterized in that the second configuration parameter is an operation strategy configuration parameter periodically issued by the application configuration center after receiving the first configuration parameter. The configuration method according to claim 9 is characterized in that the second configuration parameter is an operation policy configuration parameter issued by the application configuration center after receiving the first configuration parameter when the operation status parameter of the node where the container group is located is monitored to change the operation status. The configuration method according to claim 9, characterized in that the initialization container uploads a configuration request including the first configuration parameter to the application configuration center, comprising: The initialization container periodically uploads the configuration request to the application configuration center. The configuration method according to claim 9, characterized in that the initialization container uploads a configuration request including the first configuration parameter to the application configuration center, comprising: After the first configuration parameter is changed, the initialization container uploads the configuration request including the changed first configuration parameter to the application configuration center. The configuration method according to claim 1, characterized in that the business application container obtains the configuration file based on the path of the configuration file mounted in the business application container template, comprising: The business application container obtains the configuration file based on the path of the configuration file written in the business configuration parameters of the business application container. A container group configuration device, characterized by comprising: A calling unit is configured to call a preset initialization container template and a preset business application container template after receiving a container group creation command; A first creation unit is configured to create an initialization container for a container group by using the initialization container template, so that the initialization container runs an adaptive parameter acquisition script in the initialization container template to acquire configuration parameters and generate a configuration file for the container group; The second creation unit is configured to use the business application container template to create a business application container for the container group, so that the business application container obtains the configuration file based on the path of the configuration file mounted in the business application container template, and completes the application configuration according to the configuration parameters. A container group configuration device, characterized by comprising: a memory arranged to store a computer program; A processor is configured to execute the computer program, and when the computer program is executed by the processor, the steps of the method for configuring a container group as claimed in any one of claims 1 to 17 are implemented. A non-volatile readable storage medium having a computer program stored thereon, characterized in that when the computer program is executed by a processor, the steps of the method for configuring a container group as claimed in any one of claims 1 to 17 are implemented.