Container cloud platform expansion method, electronic device and computer-readable storage medium

Abstract

The present application discloses a method for expanding the capacity of a container cloud platform, an electronic device, and a computer-readable storage medium, the method comprising: obtaining a node configuration file, determining the address information and basic components configured by the node configuration file for the newly added management node to be expanded; constructing a platform environment for the newly added management node and generating a newly added management node in the platform environment; wherein, in the platform environment, other management nodes other than the set platform management node are cleared before generating the newly added management node, and the newly generated newly added management node is configured with an operation management service; based on the address information and basic components, creating a component configuration file on the platform management node, synchronizing the component configuration file to the newly added management node, and using the operation management service on the newly added management node to load the component configuration file. Through the above method, the present application can improve the convenience of expanding the capacity of the container cloud platform.

Description

Technical Field

[0001] The present application relates to the technical field of data platforms, and in particular to a container cloud platform expansion method, an electronic device, and a computer-readable storage medium. Background Art

[0002] With the advent of the data age, lightweight container cloud platforms have been widely used. However, in the face of growing load demands, conventional container cloud platforms often cannot meet the requirements of high availability and high performance, so it is necessary to expand the capacity of the container cloud platform. In the prior art, when expanding the capacity of the container cloud platform, developers still need to configure it in the background, which makes it inconvenient to expand the capacity of the container cloud platform. In view of this, how to improve the convenience of expanding the container cloud platform has become an urgent problem to be solved. Summary of the invention

[0003] The main technical problem solved by the present application is to provide a container cloud platform expansion method, an electronic device and a computer-readable storage medium, which can improve the convenience of container cloud platform expansion.

[0004] To solve the above technical problems, the first aspect of the present application provides a method for expanding a container cloud platform, the method comprising: obtaining a node configuration file, determining the address information and basic components configured in the node configuration file for a newly added management node to be expanded; building a platform environment for the newly added management node and generating the newly added management node in the platform environment; wherein, in the platform environment, other management nodes other than the already set platform management nodes are cleared before generating the newly added management node, and the newly generated newly added management node is configured with an operation management service; based on the address information and the basic components, creating a component configuration file on the platform management node, synchronizing the component configuration file to the newly added management node, and loading the component configuration file using the operation management service on the newly added management node.

[0005] To solve the above technical problem, the second aspect of the present application provides an electronic device, which includes: a memory and a processor coupled to each other, wherein the memory stores program data, and the processor calls the program data to execute the method described in the first aspect.

[0006] In order to solve the above technical problem, the third aspect of the present application provides a computer-readable storage medium on which program data is stored. When the program data is executed by a processor, the method described in the first aspect is implemented.

[0007] The above scheme obtains the node configuration file configured for the newly added management node to be expanded, determines the address information and basic components included in the node configuration file, and thus clarifies the configuration requirements of the newly added management node. A platform environment on the container cloud platform is constructed for the newly added management node and a newly added management node is generated in the platform environment, wherein, in the platform environment of the container cloud platform, other management nodes other than the set platform management nodes are cleared before the newly added management nodes are generated, thereby ensuring the reentrancy of the entire process, and each time before the new management node is generated, the same platform environment is available, and the newly generated new management node is configured with an operation management service. Based on the address information and basic components, a component configuration file is created for the newly added management node on the set platform management node, the component configuration file is synchronized to the newly added management node, and the component configuration file is loaded using the operation management service on the newly added management node to obtain the newly added management node other than the platform management node, so that the container cloud platform meets the requirements of high availability and high performance. Therefore, after obtaining the node configuration file, the new management node can be expanded on the container cloud platform in the entire process, thereby improving the convenience of expanding the container cloud platform. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. 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 creative work. Among them:

[0009] Figure 1 It is a flow chart of an implementation method of a container cloud platform expansion method of the present application;

[0010] Figure 2 It is a topological diagram of an implementation method of the container cloud platform expansion method of the present application;

[0011] Figure 3 It is a flow chart of another implementation method of the container cloud platform expansion method of the present application;

[0012] Figure 4 It is a flowchart of an implementation method of configuring a new management node in this application;

[0013] Figure 5 It is a structural schematic diagram of an embodiment of the electronic device of the present application;

[0014] Figure 6 It is a structural schematic diagram of an implementation method of a computer-readable storage medium of the present application. DETAILED DESCRIPTION

[0015] 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, and different implementation methods can be adaptively combined. 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.

[0016] The terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship. In addition, "many" in this article means two or more than two.

[0017] The container cloud platform expansion method provided in the present application is used to expand the management node of the container cloud platform, and the new management node is expanded on the basis of the platform management node. The execution subject corresponding to the container cloud platform expansion method provided in the present application is a processing unit that can call the container cloud platform.

[0018] It should be noted that the management node originally set up by the container cloud platform is the platform management node. In order to adapt to the voting mechanism of the container cloud platform, the sum of all platform management nodes and newly added management nodes is an odd number. Normally, the number of platform management nodes that have been set up is an odd number, and the number of newly added management nodes is an even number. The container cloud platform expansion method provided in this application is particularly suitable for a stand-alone platform with only one management node, and is converted to a cluster version platform with multiple management nodes. In addition, on the basis of setting up multiple platform management nodes, adding more management nodes is also applicable to the technical solution of this application.

[0019] See also Figure 1 , Figure 1 It is a flow chart of an implementation method of a container cloud platform expansion method of the present application, the method comprising:

[0020] S101: Obtain a node configuration file, and determine that the node configuration file is address information and basic components configured for a newly added management node to be expanded.

[0021] Specifically, a node configuration file configured for the newly added management node to be expanded is obtained, and the address information and basic components included in the node configuration file are determined, so as to clarify the configuration requirements of the newly added management node.

[0022] In some implementation scenarios, a manager is used to obtain a node configuration file and parse the node configuration file to determine that the node configuration file is address information and basic components configured for a new management node to be expanded.

[0023] In some implementation scenarios, a node configuration file is obtained, the node configuration file is converted into a format that matches the container cloud platform, and address information and basic components configured for a new management node to be expanded are obtained from the converted node configuration file.

[0024] It can be understood that the address information is related to the physical address of the newly added management node, and the basic component is related to the component subclass required by the management node.

[0025] In a specific implementation scenario, the address information includes the first node address of the platform management node and the second node address of the newly added management node. The basic components include at least the distributed key-value storage system Etcd, the virtual address VIP, the interface service Apiserver, the scheduler Scheduler and the controller ControllerManager as component subclasses.

[0026] In a specific implementation scenario, the address information includes the first node address of the platform management node, the second node address of the newly added management node and the virtual address VIP, and the basic components include at least the distributed key-value storage system Etcd, the interface service Apiserver, the scheduler Scheduler and the controller ControllerManager as component subclasses.

[0027] S102: construct a platform environment for the newly added management node and generate the newly added management node in the platform environment; wherein, in the platform environment, other management nodes except the set platform management nodes are cleared before generating the newly added management node, and the newly generated new management node is configured with an operation management service.

[0028] Specifically, a platform environment on the container cloud platform is built for the newly added management node and a newly added management node is generated within the platform environment.

[0029] It should be noted that in the platform environment of the container cloud platform, other management nodes except the already set platform management nodes are cleared before generating new management nodes, so as to ensure the reentrancy of the entire process. Each time a new management node is generated, the same platform environment is available, and the newly generated new management node is configured with the running management service Kubelet.

[0030] In some implementation scenarios, it is determined whether the container cloud platform includes other management nodes in addition to the set platform management nodes. If so, the corresponding management nodes are removed, new management nodes are regenerated on the container cloud platform based on the configuration files, and the management services are reconfigured and run on the new management nodes.

[0031] In some implementation scenarios, the container cloud platform corresponds to a preset node address of a platform management node that has been set up, and a clear instruction is generated to clear the management nodes except the preset node address. The clear instruction is used to clear other management nodes except the platform management node, and a new management node is regenerated on the container cloud platform based on the configuration file. The container service is restarted on the new management node, and the restarted container service is used to configure the operation management service of the new management node.

[0032] S103: Based on the address information and basic components, create a component configuration file on the platform management node, synchronize the component configuration file to the newly added management node, and use the operation management service on the newly added management node to load the component configuration file.

[0033] Specifically, based on the address information and basic components, a component configuration file is created for the newly added management node on the already set platform management node, the component configuration file is synchronized to the newly added management node, and the component configuration file is loaded using the running management service on the newly added management node to obtain the newly added management node in addition to the platform management node, so that the container cloud platform meets the requirements of high availability and high performance.

[0034] In some implementation scenarios, for each newly added management node, a component configuration file corresponding to the newly added management node is created on the platform management node based on the address information and basic components of the newly added management node, the component configuration file is synchronized to a specified directory in the newly added management node, and the component configuration file in the specified directory is loaded using the running management service on the newly added management node.

[0035] In some implementation scenarios, based on the address information and basic components of each newly added management node, a component configuration file corresponding to each newly added management node is created on the platform management node, the component configuration file of each newly added management node is synchronized to the designated area of ​​the corresponding newly added management node, and the component configuration file in the designated area is loaded using the running management service on the newly added management node.

[0036] It is understandable that after obtaining the node configuration file, the capacity of the container cloud platform can be expanded in the entire process to obtain new management nodes, thereby improving the convenience of expanding the capacity of the container cloud platform.

[0037] In a specific implementation scenario, please refer to Figure 2 , Figure 2This is a topology diagram of an implementation method of the container cloud platform expansion method of the present application. The node configuration file is loaded using the binary manager on the container cloud platform, wherein the configuration file includes the node address of the newly added management node and each component subclass in the basic components and its corresponding component quota. The basic components include the distributed key-value storage system Etcd, the virtual address VIP, the interface service Apiserver, the scheduler Scheduler and the controller ControllerManager as component subclasses. Build a platform environment for the newly added management node, create a new management node in the platform environment and configure the component configuration file corresponding to each component subclass on the newly added management node, so as to embed this expansion process into the container cloud platform in a binary manner to realize automatic expansion.

[0038] It is understandable that the computing nodes managed in the expanded container cloud platform can be customized for expansion. The computing nodes correspond to the load balancing service Kube-proxy, the operation management service Kubelet and the container service Docker.

[0039] The above scheme obtains the node configuration file configured for the newly added management node to be expanded, determines the address information and basic components included in the node configuration file, and thus clarifies the configuration requirements of the newly added management node. A platform environment on the container cloud platform is constructed for the newly added management node and a newly added management node is generated in the platform environment, wherein, in the platform environment of the container cloud platform, other management nodes other than the set platform management nodes are cleared before the newly added management nodes are generated, thereby ensuring the reentrancy of the entire process, and each time before the new management node is generated, the same platform environment is available, and the newly generated new management node is configured with an operation management service. Based on the address information and basic components, a component configuration file is created for the newly added management node on the set platform management node, the component configuration file is synchronized to the newly added management node, and the component configuration file is loaded using the operation management service on the newly added management node to obtain the newly added management node other than the platform management node, so that the container cloud platform meets the requirements of high availability and high performance. Therefore, after obtaining the node configuration file, the new management node can be expanded on the container cloud platform in the entire process, thereby improving the convenience of expanding the container cloud platform.

[0040] See also Figure 3 , Figure 3 It is a flow chart of another implementation method of the container cloud platform expansion method of the present application, the method comprising:

[0041] S201: Obtain a node configuration file, and determine that the node configuration file is address information and basic components configured for a newly added management node to be expanded.

[0042] Specifically, a node configuration file configured for the newly added management node to be expanded is obtained, and the address information and basic components included in the node configuration file are determined, so as to clarify the configuration requirements of the newly added management node.

[0043] S202: In the distributed key-value storage system cluster of the container cloud platform, other management nodes other than the platform management node and their corresponding node key-value components are removed.

[0044] Specifically, in the distributed key-value storage system cluster of the container cloud platform, other nodes except the set platform management node are cleared, and the corresponding node key-value component etcd.manifest is removed to facilitate the reentrancy of the entire process. Even if the expansion process has been executed in the historical period but failed, the same platform environment will be available when the expansion process is executed again.

[0045] S203: Generate a new management node in the container cloud platform.

[0046] Specifically, based on the configuration file, a new management node indicated by the configuration file is generated in the container cloud platform.

[0047] In some implementation scenarios, generating new management nodes in a container cloud platform includes: obtaining the number of new management nodes indicated by a configuration file; generating new management nodes of the same number of nodes in the container cloud platform, and determining node labels of the new management nodes; wherein, when the new management nodes are generated by converting computing nodes in a distributed key-value storage system cluster, the node labels are converted from computing labels to management labels.

[0048] Specifically, the node number of the new management node indicated by the configuration file is obtained, a new management node matching the node number is generated in the container cloud platform, and the node label of the new management node is determined, thereby generating the new management node and ensuring the accuracy of the node label of the newly generated new management node.

[0049] It can be understood that the newly added management node can be directly created or converted from the computing node. Among them, the newly added management node directly created is matched with the management label as the node label, and the newly added management node converted from the computing node needs to convert the computing label into the management label in order to set an accurate node label.

[0050] S204: reconfigure the operation management service for the newly added management node, and obtain the platform environment constructed for the newly added management node and the newly added management node generated in the platform environment.

[0051] Specifically, the operation management service is reconfigured for the newly added management node, thereby ensuring that the operation management service in the newly added management node is also reentrant, and obtaining the platform environment constructed for the newly added management node and the newly added management node generated in the platform environment.

[0052] In some implementation scenarios, the operation management service is reconfigured for the newly added management node, including: terminating the existing operation management service on the newly added management node, and restarting the container service on the newly added management node; using the restarted container service to start a new container, and configuring the operation management service in the new container to the newly added management node; starting the current operation management service on the newly added management node.

[0053] Specifically, the existing operation management service is terminated on the newly added management node, and the container service on the newly added management node is restarted. The new container is started using the restarted container service, and the Kubelet and Kubectl related information in the new container is copied to the newly added management node, thereby reconfiguring the operation management service on the new management node.

[0054] Furthermore, the reconfigured operation management service on the newly added management node is started so that subsequent steps can utilize the operation management service.

[0055] S205: Based on the address information and basic components, create a component configuration file on the platform management node, synchronize the component configuration file to the newly added management node, and load the component configuration file using the operation management service on the newly added management node.

[0056] Specifically, based on the address information and basic components, a component configuration file is created for the newly added management node on the set platform management node, the component configuration file is synchronized to the newly added management node, and the component configuration file is loaded using the running management service on the newly added management node to obtain the newly added management node in addition to the platform management node.

[0057] In some implementation scenarios, the node configuration file also includes a communication port between the platform management node and the newly added management node, the address information includes a first node address of the platform management node and a second node address of the newly added management node, and the first node address is used to obtain the platform management node.

[0058] Specifically, the node configuration file also includes a communication port for communication between the platform management node and the newly added management node based on a preset protocol, and the address information includes a first node address of the platform management node and a second node address of the newly added management node. The first node address can be used to obtain the designated platform management node for generating the component configuration file.

[0059] Optionally, the protocol between the platform management node and the newly added management node may be a secure shell protocol (Secure Shell, SSH) or other communication protocols, and this application does not impose any specific restrictions on this.

[0060] It should be noted that, based on the address information and basic components, a component configuration file is created on the platform management node, the component configuration file is synchronized to the newly added management node, and the component configuration file is loaded using the operation management service on the newly added management node, including: based on the second node address and the basic components, creating a component configuration file corresponding to the newly added management node indicated by the second node address on the platform management node; synchronizing the component configuration file to the designated directory of the corresponding newly added management node using the communication port; and loading the component configuration file in the designated directory using the operation management service on the newly added management node.

[0061] Specifically, based on the second node address and the basic component, a component configuration file is created on the platform management node for the newly added management node indicated by the second node address, thereby obtaining an accurate component configuration file of the newly added management node on the platform management node.

[0062] Furthermore, the communication port between the platform management node and the newly added management node is used to synchronize the component configuration file to the designated directory of the corresponding newly added management node to ensure the accuracy of synchronization, and the running management service on the newly added management node is used to load the component configuration file in the designated directory, thereby configuring the components required by the node on the newly added management node to realize the functions of the newly added management node.

[0063] It should be noted that the address information also includes the virtual address of the newly added management node. The basic components include at least a distributed key-value storage system, a virtual address, an interface service, a scheduler, and a controller as component subclasses. The component subclasses are matched with component quotas, and each component subclass creates a matching component configuration file in turn.

[0064] Specifically, see Figure 4 , Figure 4 It is a flow chart of an implementation method of configuring a new management node in the present application. After building the platform environment, matching component configuration files are created for the component subclasses in sequence according to the component quotas of the component subclasses, thereby realizing the function of adding a new management node.

[0065] It can be understood that based on the configuration order of the above-mentioned component subclasses, the functional configuration of the newly added management node can be accurately and effectively performed, thereby realizing the various functions of the newly added management node and improving the reliability of the container cloud platform after expansion.

[0066] It should be noted that when the component subclass is a distributed key-value storage system, a component configuration file corresponding to the newly added management node indicated by the second node address is created on the platform management node based on the second node address and the basic component, including: generating a component certificate corresponding to the newly added management node indicated by the second node address on the platform management node based on the second node address and the component quota matching each component subclass; using the component certificate to add the newly added management node to the distributed storage key-value system cluster, and obtaining a component configuration file corresponding to the distributed key-value storage system on the newly added management node.

[0067] Specifically, based on the second node address and the component quota that matches each component subclass, a corresponding component certificate is generated on the platform management node for the newly added management node indicated by the second node address.

[0068] Furthermore, the distributed key-value storage system adopts a role-based consensus algorithm (Replicated And Fault Tolerant, RAFT) protocol, selects a new management node corresponding to the corresponding second node address, and uses the component certificate to add the new management node to the distributed storage key-value system cluster as a follower, and obtains the component configuration file corresponding to the distributed key-value storage system on the new management node.

[0069] It can be understood that the distributed key-value storage system can be expanded by changing the cluster status in the component configuration file corresponding to the new distributed key-value storage system to an existing status, copying this file to the specified directory, and waiting for Kubelet to pull up this static pod.

[0070] It can be understood that when the component subclass is one of the virtual address, interface service, scheduler and controller, a component configuration file corresponding to the newly added management node indicated by the second node address is created on the platform management node based on the second node address and the basic component, including: based on the second node address, the virtual address and the component quota matching the component subclass, a component configuration file corresponding to the corresponding component subclass of the newly added management node indicated by the second node address is created on the platform management node.

[0071] Specifically, on the platform management node, for the component subclasses sorted after the virtual address, based on the component quota matching the second node address, the virtual address and the component subclass, a component configuration file corresponding to the corresponding component subclass is created for the newly added management node indicated by the second node address, thereby implementing the functions corresponding to each component subclass in turn.

[0072] It can be understood that on the platform management node, based on the virtual address in the configuration file, the second node address of the newly added management node and the component quota of the virtual address, a yaml file corresponding to the virtual address VIP is generated as the component configuration file, and then this component configuration file is copied to the specified directory of the newly added management node through the scp command, and wait for Kubelet to pull up the VIP pod to load the corresponding component configuration file.

[0073] Furthermore, on the platform management node, a yaml file of the interface service Apiserver is generated as a component configuration file according to the virtual address in the configuration file, the second node address of the newly added management node, and the component quota of the interface service. Then, the component configuration file is copied to the specified directory of the newly added management node through the scp command, and Kubelet is waited to start the Apiserver pod to load the corresponding component configuration file.

[0074] Similarly, on the platform management node, generate the scheduler Scheduler yaml file as the component configuration file based on the virtual address in the configuration file, the second node address of the newly added management node, and the component quota of the scheduler. Then use the scp command to copy this component configuration file to the specified directory of the newly added management node, and wait for Kubelet to pull up the Scheduler pod to load the corresponding component configuration file.

[0075] Furthermore, on the platform management node, a yaml file of the manager ControllerManager is generated as a component configuration file based on the virtual address in the configuration file, the second node address of the newly added management node, and the component quota of the manager. This component configuration file is then copied to the specified directory of the newly added management node through the scp command, and Kubelet is waited for to start the ControllerManager pod to load the corresponding component configuration file.

[0076] It is understandable that the component configuration files corresponding to each component subclass can be configured in sequence according to the order, thereby realizing automatic expansion of the management node and improving the convenience of expansion of the container cloud platform.

[0077] In this embodiment, in the distributed key-value storage system cluster of the container cloud platform, other nodes except the set platform management node are cleared, and the corresponding node key-value components are removed to facilitate the reentrancy of the entire process, and the operation management service is reconfigured for the newly added management node, thereby ensuring that the operation management service in the newly added management node is also reentrant. Based on the second node address and the basic component, a component configuration file is created on the platform management node for the newly added management node indicated by the second node address, so as to obtain the accurate component configuration file of the newly added management node on the platform management node, and the communication port between the platform management node and the newly added management node is used to synchronize the component configuration file to the designated directory of the corresponding newly added management node to ensure the accuracy of synchronization, and the operation management service on the newly added management node is used to load the component configuration file in the designated directory, so as to configure the components required by the node on the newly added management node, realize automatic expansion of the management node, and improve the convenience of expansion of the container cloud platform.

[0078] See also Figure 5 , Figure 5 It is a structural diagram of an embodiment of an electronic device of the present application, wherein the electronic device 30 includes a memory 301 and a processor 302 coupled to each other, wherein the memory 301 stores program data (not shown), and the processor 302 calls the program data to implement the method in any of the above embodiments. For descriptions of related contents, please refer to the detailed description of the above method embodiments, which will not be repeated here.

[0079] See also Figure 6 , Figure 6 It is a structural diagram of an embodiment of a computer-readable storage medium of the present application. The computer-readable storage medium 40 stores program data 400. When the program data 400 is executed by a processor, the method in any of the above embodiments is implemented. For descriptions of related contents, please refer to the detailed description of the above method embodiments, which will not be repeated here.

[0080] It should be noted that the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present implementation scheme.

[0081] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0082] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially 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. The computer software product is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) or a processor to execute all or part of the steps of each implementation method of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program code.

[0083] The above description is only an implementation method of the present application, and does not limit the protection scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly used in other related technical fields, are also included in the protection scope of the present application.

Claims

1. A container cloud platform expansion method, characterized in that: The method comprises: Obtain a node configuration file, and determine that the node configuration file is address information and basic components configured for a newly added management node to be expanded; A platform environment is constructed for the newly added management node and the newly added management node is generated in the platform environment; wherein, in the platform environment, other management nodes other than the already set platform management node are cleared before the newly added management node is generated, and the newly generated newly added management node is configured with an operation management service, and when the newly added management node is generated, the operation management service is reconfigured for the newly added management node; the node configuration file also includes a communication port between the platform management node and the newly added management node, and the address information includes a first node address of the platform management node and a second node address of the newly added management node, and the first node address is used to obtain the platform management node; Based on the address information and the basic component, a component configuration file is created on the platform management node, the component configuration file is synchronized to the newly added management node, and the component configuration file is loaded by using the operation management service on the newly added management node; specifically comprising: based on the second node address and the basic component, a component configuration file corresponding to the newly added management node indicated by the second node address is created on the platform management node; the component configuration file is synchronized to the designated directory of the corresponding newly added management node by using the communication port; the component configuration file under the designated directory is loaded by using the operation management service on the newly added management node; The address information also includes the virtual address of the newly added management node, the basic components include at least a distributed key-value storage system, a virtual address, an interface service, a scheduler, and a controller as component subclasses, and the component subclasses are matched with component quotas, and each of the component subclasses creates a matching component configuration file in turn; The component configuration file corresponding to the distributed key-value storage system is obtained based on the following steps: based on the second node address and the component quota matched by each of the component subclasses, generating a component certificate corresponding to the newly added management node indicated by the second node address on the platform management node; using the component certificate to add the newly added management node to the distributed storage key-value system cluster, and obtaining the component configuration file corresponding to the distributed key-value storage system on the newly added management node; wherein the cluster state in the component configuration file corresponding to the new distributed key-value storage system is changed to an existing state and copied to the designated directory; The component configuration files corresponding to the virtual address, the interface service, the scheduler and the controller are obtained based on the following steps: based on the second node address, the virtual address and the component quota matching the component subclass, a component configuration file corresponding to the corresponding component subclass of the newly added management node indicated by the second node address is created on the platform management node; wherein the component configuration files corresponding to the virtual address, the interface service, the scheduler and the controller are copied to the designated directory.

2. The container cloud platform expansion method according to claim 1, characterized in that: The step of constructing a platform environment for the newly added management node and generating the newly added management node in the platform environment includes: In the distributed key-value storage system cluster of the container cloud platform, other management nodes other than the platform management node and their corresponding node key-value components are removed; Generating the newly added management node in the container cloud platform; The operation management service is reconfigured for the newly added management node to obtain the platform environment constructed for the newly added management node and the newly added management node generated in the platform environment.

3. The container cloud platform expansion method according to claim 2, characterized in that: The generating the newly added management node in the container cloud platform includes: Obtain the number of newly added management nodes indicated by the configuration file; Generate the newly added management nodes of the number of nodes in the container cloud platform, and determine the node labels of the newly added management nodes; wherein, when the newly added management nodes are generated by converting the computing nodes in the distributed key-value storage system cluster, the node labels are converted from computing labels to management labels.

4. The container cloud platform expansion method according to claim 2, characterized in that: The reconfiguring the operation management service for the newly added management node includes: Terminate the existing running management service on the newly added management node, and restart the container service on the newly added management node; Using the restarted container service to start a new container, and configuring the operation management service in the new container to the newly added management node; Start the current running management service on the newly added management node.

5. An electronic device, characterized in that: include: A memory and a processor coupled to each other, wherein the memory stores program data, and the processor calls the program data to execute the method according to any one of claims 1 to 4.

6. A computer-readable storage medium having program data stored thereon, characterized in that: When the program data is executed by a processor, the method according to any one of claims 1 to 4 is implemented.

Images