CN116155979A

CN116155979A - Distributed container cluster management method and device, electronic equipment and storage medium

Info

Publication number: CN116155979A
Application number: CN202111376288.9A
Authority: CN
Inventors: 黄丹池; 何震苇; 林园致; 严丽云; 杨新章
Original assignee: China Telecom Corp Ltd
Current assignee: China Telecom Corp Ltd
Priority date: 2021-11-19
Filing date: 2021-11-19
Publication date: 2023-05-23

Abstract

The disclosure provides a distributed container cluster management method and device, electronic equipment and a storage medium, and relates to the technical field of computers. The distributed container cluster management method comprises the following steps: the method comprises the steps that a global cluster controller deploys cluster components at a center cloud node and an edge cloud node respectively according to a hierarchical structure, and deploys a terminal cluster working face component at a terminal cloud node; the cluster component comprises a cluster control plane component and a cluster working plane component; establishing an association relation between cluster control plane components, and uniformly managing the cluster control plane components based on the association relation; when a resource request is received, determining a target working surface component from the cluster working surface components and the terminal cluster working surface components so as to realize low-delay response of the resource request through the target working surface component. The technical scheme of the embodiment of the disclosure can realize unified management of the distributed container clusters, and can also realize low-delay response of resource requests by cross-node scheduling of resources through the target working surface component.

Description

Distributed container cluster management method and device, electronic equipment and storage medium

Technical Field

The present disclosure relates to the field of computer technology, and in particular, to a distributed container cluster management method, a distributed container cluster management device, an electronic apparatus, and a computer readable storage medium.

Background

With the continuous development of container cluster construction technology in the cloud computing field, distributed container cluster management also becomes an important factor affecting the development of the cloud computing field.

However, in the related method for constructing the distributed container clusters, the container clusters of the center cloud, the edge cloud and the terminal cloud are mostly constructed by adopting different cloud platform technologies, so that the container clusters among the center cloud, the edge cloud and the terminal cloud are difficult to manage, and meanwhile, resource scheduling barriers exist among the center cloud, the edge cloud and the terminal cloud, so that the resource requirements of enterprises or users are difficult to meet in real time.

Therefore, the distributed container cluster management method capable of meeting the low-delay requirements of diversification of enterprise applications and resource scheduling is provided, and has important practical significance in the field of cloud computing.

It should be noted that the information disclosed in the above background section is only for enhancing understanding of the background of the present disclosure and thus may include information that does not constitute prior art known to those of ordinary skill in the art.

Disclosure of Invention

An object of an embodiment of the present disclosure is to provide a distributed container cluster management method, a distributed container cluster management device, an electronic apparatus, and a computer readable storage medium, so as to overcome the problems of high complexity of distributed container cluster management and high response delay of a resource request at least to some extent.

Other features and advantages of the present disclosure will be apparent from the following detailed description, or may be learned in part by the practice of the disclosure.

According to a first aspect of an embodiment of the present disclosure, there is provided a distributed container cluster management method, including: sequentially deploying cluster components at a center cloud node and an edge cloud node respectively according to a hierarchical structure through a global cluster controller, and deploying terminal cluster working face components at terminal cloud nodes; the cluster assembly comprises a cluster control surface assembly and a cluster working surface assembly; based on a service discovery mechanism, establishing an association relationship between a cluster control plane component in the central cloud node and a cluster control plane component in the edge cloud node, and uniformly managing the cluster control plane components based on the association relationship; when a resource request is received, a monitoring mechanism is adopted to acquire state data of the cluster working face component and the terminal cluster working face component, and a target working face component is determined from the cluster working face component and the terminal cluster working face component according to the state data so as to realize low-delay response of the resource request through the target working face component.

In some example embodiments of the disclosure, based on the foregoing scheme, the method further comprises: and sequentially deploying a standard container engine and a mirror warehouse at the central cloud node and the edge cloud node respectively through the global cluster controller according to the hierarchical structure, and deploying a custom container engine at the terminal node so as to provide a mirror image of the standard container engine and a mirror image of the custom container engine as well as a mirror image of the cluster component and a download service of a mirror image of the terminal cluster working face component through the mirror warehouse.

In some example embodiments of the disclosure, based on the foregoing scheme, the method further comprises: and deploying a distributed service registry at the central cloud node to register the cluster control plane component of the edge cloud node to the distributed service registry.

In some example embodiments of the present disclosure, based on the foregoing solution, the establishing an association relationship between a cluster control plane component in the central cloud node and a cluster control plane component in the edge cloud node, and managing the cluster control plane components in a unified manner based on the association relationship includes: acquiring cluster control plane component information in the edge cloud node from the distributed service registry by a member cluster controller of the cluster control plane component in the center cloud node, and accessing a cluster control plane component corresponding to the cluster control plane component information to the cluster control plane component in the center cloud node; based on the cluster control plane information, the cluster control plane components corresponding to the cluster control plane information and the cluster control plane components in the central cloud node, establishing an association relationship between the cluster control plane components in the central cloud node and the cluster control plane components in the edge cloud node, and uniformly managing the cluster control plane components based on the association relationship.

In some example embodiments of the disclosure, based on the foregoing scheme, the method further comprises: caching and transmitting configuration data of the cluster control plane component of the edge cloud node to the terminal cloud node; establishing an association relationship with a cluster control plane component in the edge cloud node according to the configuration data through a terminal cluster working plane component in the terminal cloud node; and configuring sharing of the cluster control plane components in the edge cloud nodes and the terminal cluster control plane components in the terminal cloud nodes based on the association relation.

In some example embodiments of the present disclosure, based on the foregoing solution, the acquiring, by using a listening mechanism, status data of the cluster face component and the terminal cluster face component, and determining, according to the status data, a target face component from the cluster face component and the terminal cluster face component includes: monitoring state data of a cluster working face in the central cloud node through a scheduler corresponding to a cluster control face component in the central cloud node, and sending a resource request to the scheduler corresponding to the cluster control face component in the edge cloud node when the state data is detected to be in a busy state; and when a dispatcher corresponding to the cluster control plane component in the edge cloud node monitors the resource request, acquiring state data of the cluster working plane component in the edge cloud node, and determining a target working plane component responding to the resource request based on the state data of the cluster working plane component in the edge cloud node and the state data of the terminal cluster working plane component.

In some example embodiments of the present disclosure, based on the foregoing solution, the determining, based on the state data of the cluster face component in the edge cloud node and the state data of the terminal cluster face component, a target face component that responds to the resource request includes: when the state data of the cluster working face component in the edge cloud node is detected to be in a busy state, distributing the resource request to the terminal cluster working face component through a scheduler in a cluster control face in the edge cloud node; and monitoring the state data of the terminal cluster working face component to determine a target working face component meeting the resource request from the cluster working face components according to the state data of the terminal cluster working face component.

According to a second aspect of embodiments of the present disclosure, there is provided a distributed container cluster management apparatus, including: the component deployment module is used for sequentially deploying cluster components at the center cloud node and the edge cloud node respectively according to a hierarchical structure through the global cluster controller, and deploying terminal cluster working face components at the terminal cloud node; the cluster assembly comprises a cluster control surface assembly and a cluster working surface assembly; the component management module is used for establishing an association relation between the cluster control plane components in the central cloud node and the cluster control plane components in the edge cloud node based on a service discovery mechanism, and uniformly managing the cluster control plane components based on the association relation; and the resource request response module is used for acquiring the state data of the cluster working face component and the terminal cluster working face component by adopting a monitoring mechanism when a resource request is received, and determining a target working face component from the cluster working face component and the terminal cluster working face according to the state data so as to schedule service data matched with the resource request through the target working face component and realize cross-node scheduling of the service data.

In some example embodiments of the present disclosure, based on the foregoing solution, the component deployment module further includes a container engine deployment unit, where the container engine deployment unit is configured to sequentially deploy, by using the global cluster controller, a standard container engine and a mirror warehouse at the central cloud node and the edge cloud node, respectively, according to the hierarchical structure, and deploy, by using the mirror warehouse, a custom container engine, so as to provide, by using the mirror warehouse, a mirror image of the standard container engine and a mirror image of the custom container engine, and a download service of a mirror image of the cluster component and a mirror image of the terminal cluster working surface component.

In some example embodiments of the present disclosure, based on the foregoing solution, the component management module further includes a service registry deployment unit configured to deploy a distributed service registry at the central cloud node to register the cluster control plane component of the edge cloud node to the distributed service registry.

In some example embodiments of the present disclosure, based on the foregoing solution, the component management module includes an association relationship establishing unit, where the association relationship establishing unit is configured to obtain, by using a member cluster controller of the cluster control plane component in the central cloud node, cluster control plane component information of the edge cloud node from the distributed service registry, and access a cluster control plane component corresponding to the cluster control plane component information to a cluster control plane component in the central cloud node; based on the cluster control plane information, the cluster control plane components corresponding to the cluster control plane information and the cluster control plane components in the central cloud node, establishing an association relationship between the cluster control plane components in the central cloud node and the cluster control plane components in the edge cloud node, and uniformly managing the cluster control plane components based on the association relationship.

In some example embodiments of the present disclosure, based on the foregoing solution, the distributed container cluster management apparatus further includes a component sharing module, where the component sharing module is configured to cache and send configuration data of a cluster control plane component of the edge cloud node to the terminal cloud node; establishing an association relationship with a cluster control plane component in the edge cloud node according to the configuration data through a terminal cluster working plane component in the terminal cloud node; and configuring sharing of the cluster control plane components in the edge cloud nodes and the terminal cluster control plane components in the terminal cloud nodes based on the association relation.

In some example embodiments of the present disclosure, based on the foregoing solutions, the resource request response module includes a resource request scheduling unit, where the resource request scheduling unit is configured to monitor, by a scheduler corresponding to a cluster control plane component in the central cloud node, status data of a cluster working plane in the central cloud node, and send, when the status data is detected to be in a busy state, a resource request to a scheduler corresponding to the cluster control plane component in the edge cloud node; when a dispatcher corresponding to a cluster control surface component in the edge cloud node monitors the resource request, acquiring state data of the cluster working surface component of the edge cloud node, and determining a target working surface component responding to the resource request based on the state data of the cluster working surface component of the edge cloud node and the state data of the terminal cluster working surface component.

In some example embodiments of the present disclosure, based on the foregoing solution, the resource request response module further includes a target working face component determining unit, where the target working face component determining unit is configured to allocate, when detecting that status data of a cluster working face component of the edge cloud node is in a busy state, the resource request to the terminal cluster working face component through a scheduler in a cluster control plane in the edge cloud node; and monitoring the state data of the terminal cluster working face component to determine a target working face component meeting the resource request from the cluster working face components according to the state data of the terminal cluster working face component.

According to a third aspect of embodiments of the present disclosure, there is provided an electronic device, comprising: a processor; and a memory having stored thereon computer readable instructions which when executed by the processor implement the distributed container cluster management method of any of the above.

According to a fourth aspect of embodiments of the present disclosure, there is provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements a distributed container cluster management method according to any one of the above.

The technical scheme provided by the embodiment of the disclosure can comprise the following beneficial effects:

according to the distributed container cluster management method in the example embodiment of the disclosure, cluster components are sequentially deployed at a center cloud node and an edge cloud node respectively according to a hierarchical structure through a global cluster controller, and terminal cluster working face components are deployed at terminal cloud nodes; the cluster assembly comprises a cluster control surface assembly and a cluster working surface assembly; based on a service discovery mechanism, establishing an association relationship between a cluster control plane component in a center cloud node and a cluster control plane component in an edge cloud node, and uniformly managing the cluster control plane components in the center cloud node and the edge cloud node based on the association relationship; when a resource request is received, a monitoring mechanism is adopted to acquire state data of cluster working face components in a central cloud node and an edge cloud node and state data of terminal cluster working face components, and a target working face component is determined from the cluster working face components in the central cloud node and the edge cloud node and the terminal cluster working face components according to the state data so as to realize low-delay response of the resource request through the target working face component. On the one hand, the association relation of the cluster control planes in the distributed container clusters can be established, and all the cluster control planes are managed uniformly based on the association relation, so that the management complexity of the cluster control planes in different cloud nodes is reduced, and the management efficiency of the distributed container clusters is improved; on the other hand, a target working face component can be determined from the central cloud node, the edge cloud node and the terminal cloud node by adopting a monitoring mechanism, so that the cross-node scheduling of the resources is realized by scheduling the resources corresponding to the resource requests through the target working face component, and further, the low-delay response of the resource requests is realized.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure. It will be apparent to those of ordinary skill in the art that the drawings in the following description are merely examples of the disclosure and that other drawings may be derived from them without undue effort. In the drawings:

FIG. 1 schematically illustrates a schematic diagram of a distributed container cluster management method flow in accordance with some embodiments of the present disclosure;

FIG. 2 schematically illustrates a schematic diagram of a distributed container cluster architecture, according to some embodiments of the present disclosure;

FIG. 3 schematically illustrates a schematic diagram of a cluster control plane component management method flow in accordance with some embodiments of the disclosure;

FIG. 4 schematically illustrates a schematic diagram of a component sharing method flow according to some embodiments of the present disclosure;

FIG. 5 schematically illustrates a schematic diagram of a resource request response method flow in accordance with some embodiments of the present disclosure;

FIG. 6 schematically illustrates a schematic diagram of a target work component determination method flow in accordance with some embodiments of the present disclosure;

FIG. 7 schematically illustrates a schematic diagram of a distributed container cluster management apparatus, according to some embodiments of the present disclosure;

FIG. 8 schematically illustrates a structural schematic diagram of a computer system of an electronic device, in accordance with some embodiments of the present disclosure;

fig. 9 schematically illustrates a schematic diagram of a computer-readable storage medium according to some embodiments of the present disclosure.

In the drawings, the same or corresponding reference numerals indicate the same or corresponding parts.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments may be embodied in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art.

Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the disclosed aspects may be practiced without one or more of the specific details, or with other methods, components, devices, steps, etc. In other instances, well-known methods, devices, implementations, or operations are not shown or described in detail to avoid obscuring aspects of the disclosure.

Moreover, the drawings are only schematic illustrations and are not necessarily drawn to scale. The block diagrams depicted in the figures are merely functional entities and do not necessarily correspond to physically separate entities. That is, the functional entities may be implemented in software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.

In the present exemplary embodiment, a distributed container cluster management method that can be applied to a server cluster is provided first. Fig. 1 schematically illustrates a schematic diagram of a distributed container cluster management method flow according to some embodiments of the present disclosure. Referring to fig. 1, the distributed container cluster management method may include the steps of:

in step S110, sequentially deploying cluster components at a center cloud node and an edge cloud node respectively according to a hierarchical structure through a global cluster controller, and deploying terminal cluster working face components at a terminal cloud node; the cluster assembly comprises a cluster control surface assembly and a cluster working surface assembly;

in step S120, based on a service discovery mechanism, establishing an association relationship between a cluster control plane component in the central cloud node and a cluster control plane component in the edge cloud node, and uniformly managing the cluster control plane components based on the association relationship;

In step S130, when a resource request is received, a monitoring mechanism is adopted to obtain state data of the cluster working face component and the terminal cluster working face component, and a target working face component is determined from the cluster working face component and the terminal cluster working face component according to the state data, so as to implement low-delay response of the resource request through the target working face component.

According to the distributed container cluster management method in the embodiment, on one hand, the association relation of the cluster control surfaces in the distributed container clusters can be established, the cluster control surfaces can be managed uniformly based on the association relation, the management complexity of the cluster control surfaces in different cloud nodes is reduced, and the management efficiency of the distributed container clusters is improved; on the other hand, a target working face component can be determined from the central cloud node, the edge cloud node and the terminal cloud node by adopting a monitoring mechanism, so that the cross-node scheduling of the resources is realized by scheduling the resources corresponding to the resource requests through the target working face component, and further, the low-delay response of the resource requests is realized.

Next, a distributed container cluster management method in the present exemplary embodiment will be further described.

In step S110, sequentially deploying cluster components at a center cloud node and an edge cloud node respectively according to a hierarchical structure through a global cluster controller, and deploying terminal cluster working face components at a terminal cloud node; the cluster component includes a cluster control plane component and a cluster work plane component.

In an example embodiment of the present disclosure, the hierarchy may refer to a distributed deployment structure of a distributed container cluster, for example, the hierarchy may be a distributed deployment structure of a distributed container cluster in which a global node is a root node, a central cloud node is a child node of the global node, an edge cloud node is a child node of the central cloud node, and a terminal cloud node is a child node of the edge cloud node, which is not limited in particular.

The full-function container cluster control plane component, the container cluster working plane component and the standard container engine can be deployed in the central cloud node through a global cluster controller in the global node according to a hierarchical structure, the lightweight container cluster control plane component, the lightweight container cluster working plane component and the standard container engine are deployed in the edge cloud node, the self-made container engine and the terminal cluster working plane component are deployed in the terminal cloud node such as a fat terminal, and the lightweight container engine and the terminal cluster working plane component are deployed in the thin terminal so as to support large-scale container resource scheduling by adopting the hierarchical structure.

In step S120, based on a service discovery mechanism, an association relationship between the cluster control plane component in the central cloud node and the cluster control plane component in the edge cloud node is established, and the cluster control plane components are uniformly managed based on the association relationship.

In an example embodiment of the present disclosure, the service discovery mechanism may refer to a mechanism that exposes subset group information to a superior cluster based on a distributed service registry, for example, the service discovery mechanism may be a mechanism that exposes a container cluster control plane of an edge cloud node to other superior clusters based on the distributed service registry as a child control plane member of a container cluster control plane of a central cloud node, and the service discovery mechanism may also be a mechanism that exposes a container cluster work plane of a terminal cloud node to a self control plane member of a container cluster control plane of an edge cloud node based on the distributed service registry, which is not limited in this embodiment.

The association relationship between the cluster control plane components in the center cloud node and the cluster control plane components in the edge cloud nodes can be established, and all the cluster control plane components in the center cloud node and the edge cloud nodes can be managed uniformly based on the association relationship. For example, a distributed service registry can be deployed in a central cloud node, so that the central cloud node can acquire information of all cluster control surface components in the edge cloud node from the distributed service registry, and the cluster control surface components corresponding to the information of all cluster control surface components in the edge cloud node are used as sub-control surface component members of the cluster control surface components in the central cloud node, thereby realizing unified management of all cluster control surfaces in the central cloud node and the edge cloud node, improving convenience in managing the cluster control surface components crossing the nodes, and further improving management efficiency of distributed container clusters.

Preferably, the association relationship between the cluster control plane components in the center cloud node and the cluster control plane components in the edge cloud node is established, and based on the association relationship, all the cluster control plane components in the center cloud node and the edge cloud node are managed in a unified manner, and meanwhile, a center cloud working plane management node for managing all the cluster working plane components in the center cloud node in a centralized manner can be deployed in the center cloud node, an edge cloud working plane management node for managing all the cluster working plane components in the edge node in a centralized manner is deployed in the edge cloud node, and terminal cluster working plane components in the terminal cloud node are incorporated into the edge cloud working plane management node, so that centralized management of all the cluster working plane components in the center cloud node and the edge cloud node and terminal cluster working plane components in the terminal cloud node is realized, management complexity of distributed container clusters is reduced, and convenience and effectiveness of distributed container cluster management are further improved.

In an example embodiment of the present disclosure, the listening mechanism may refer to a mechanism that a scheduler in a cluster control plane listens to whether a superior cluster sends a resource request, for example, the listening mechanism may be a mechanism that a scheduler in a cluster control plane component in an edge cloud node listens to whether a central cloud node sends a resource request, and the listening mechanism may also be a mechanism that, when the scheduler in the cluster control plane component in the edge cloud node cannot allocate the resource request to a cluster working plane component in the edge cloud node, sends the resource request to a terminal cluster working plane in the terminal cloud node, and of course, the listening mechanism may also be a mechanism that a scheduler in the cluster control plane listens to whether other superior clusters send the resource request, where the embodiment of the present invention is not limited in particular.

The status data may refer to status index data for measuring whether the cluster working face component or the terminal cluster working face component can meet the resource request, for example, the status data may be index data for measuring whether the cluster working face component in the central cloud node or the cluster working face component in the edge cloud node is in a busy state, and the status data may also be index data for measuring whether the terminal cluster working face component in the terminal cloud node is in a busy state, where the status data may also be other status index data for measuring whether the cluster working face component or the terminal cluster working face component can meet the resource request, and the embodiment is not limited in particular.

The state data of the cluster working face component and the terminal cluster working face component can be obtained through a monitoring mechanism, and a target working face component which can meet the resource request is determined from the cluster working face component and the terminal cluster working face component according to the state data so as to respond to the resource request with low delay through the target working face component. For example, the resource request may be sent to the cluster working face component in the central cloud node through the scheduler of the cluster control face component in the central cloud node, when all the cluster working face components in the central cloud node are in a busy state, the resource request is scheduled to the scheduler of the cluster control face component in the edge cloud node, and when the scheduler of the cluster control face component in the edge cloud node listens to the resource request sent by the scheduler of the cluster control face in the central cloud node, the resource request is sent to the local cluster working face component (the cluster working face component in the edge cloud node); if the cluster working face components in the edge cloud nodes are all in a busy state, the resource request is sent to the terminal cluster working face components in the terminal cloud nodes, so that a target working component which can meet the resource request is determined in the terminal cluster working face components, resources are scheduled through the target working component, low-delay response of the resource request is achieved, the satisfaction of the resource requirements of users or enterprises is improved, and the use experience of the users or enterprises is further improved.

In an example embodiment of the present disclosure, a standard container engine and a mirror warehouse may be sequentially deployed at a central cloud node and an edge cloud node, respectively, by a global cluster controller according to a hierarchical structure, and a custom container engine may be deployed at a terminal node, so as to provide a standard container engine mirror image and a custom container engine mirror image, and a cluster component mirror image and a download service of a terminal cluster working surface component mirror image through the mirror warehouse.

The mirror image warehouse in the central cloud node can synchronize component container mirror image files of the central cloud node from the global mirror image warehouse in the global cloud node, and the global cluster controller can deploy component container clusters in the central cloud node according to the component container mirror image files. Similarly, the mirror repository in the edge cloud node may synchronize component container mirror files of the edge cloud node from the mirror repository in the central cloud node and deploy component containers in the edge node based on the component container mirror files of the edge cloud.

The mirror image warehouse can be deployed on the central cloud node and the edge cloud nodes, so that the central cloud node can acquire the component container mirror image file of the central cloud node from the global mirror image warehouse, and the edge cloud node can acquire the component container mirror image file of the edge cloud node from the mirror image warehouse in the central cloud node. When the distributed container cluster is constructed, the component containers can be deployed in the central cloud node based on the component container image files in the image warehouse in the central cloud node; meanwhile, the component container image file of the image warehouse in the edge cloud node can be based, and the component container is deployed in the edge cloud node, so that the nearby downloading of the component container is realized, the time delay for installing the component container is reduced, and the construction efficiency of the distributed container cluster is improved.

Fig. 2 schematically illustrates a schematic diagram of a distributed container cluster architecture, according to some embodiments of the present disclosure. The distributed container cluster architecture 200 mainly includes a global node 210, a central cloud node 220, an edge cloud node 230, and a terminal cloud node 240.

The global node 210 includes a global cluster controller 211 and a global mirror warehouse 212, where the global cluster controller 211 is mainly used for deploying cluster control plane components and cluster working plane components at the central cloud node 220 and the edge cloud node 230, and standard container engines, and deploying terminal cluster working plane components and custom container engines at the terminal cloud node 240; the global mirror repository 212 is mainly used for providing component container mirror files for the central cloud node and the edge cloud node, and for providing a nearby download service of component container mirrors for the central cloud node, the edge cloud node, and the terminal cloud node. The central cloud node 220 includes cluster control plane components and cluster work plane components, as well as mirror warehouses and distributed service discovery mechanisms. Edge cloud node 230 includes cluster control plane components and cluster work plane components, as well as mirror repositories and distributed service discovery mechanisms.

Cluster control plane components including APIServer (resource configuration control service) buses, schedulers, controllers, member cluster controllers, databases, etc. The dispatcher, the controller, the member cluster controller and the database are in butt joint with the APIServer bus, and the APIServer bus interacts with the cluster working face. The member cluster controller is responsible for the access of the subordinate sub-clusters to the superior clusters and the life cycle management of the subordinate clusters, including cluster deployment, upgrading and telescoping. The scheduler is responsible for distributing the resource request to the working face node of the current level cluster or the lower level cluster scheduler, and meanwhile, the lower level scheduler monitors the resource request distributed to the current level scheduler by the upper level scheduler and preferentially schedules the resources of the same level. The cluster working face component is mainly used for maintaining a container environment for running applications and comprises an agent, a container engine and the like, wherein the agent is responsible for interacting with an APIServer bus of a control face, and the container engine provides a container environment of an application Pod (data structure).

The mirror image warehouse is mainly used for being in charge of the distributed storage of the mirror images of the cluster components in the center cloud or the edge cloud and providing nearby downloading service for the mirror images of all the components of the distributed container cluster. Specifically, the central mirror warehouse synchronizes the local component mirrors from the global mirror warehouse, and the edge mirror warehouse synchronizes the local mirrors from the central mirror warehouse.

The distributed service discovery is mainly used for registering the information of the subordinate sub-clusters to a distributed service registration center, and a member cluster controller of the superior cluster acquires the information of the subordinate clusters from the distributed service registration center and accesses the subordinate clusters to a superior cluster control plane.

In one example embodiment of the present disclosure, a distributed service registry may be deployed at a central cloud node to register cluster control plane components in edge cloud nodes to the distributed service registry of the central cloud node.

The distributed service registry may refer to a service center for providing cluster information registration, for example, the distributed service registry may be a service center for providing registration of lower-level subset group information to an upper-level cluster, and of course, the distributed service registry may also be a center for providing other cluster information registration services, which is not limited in particular in this embodiment.

The distributed service registration centers are deployed in the central cloud nodes, the cluster control surface assembly information in the edge cloud nodes is registered in the distributed service registration centers in the central cloud nodes, so that the central cloud nodes can acquire the cluster control surface assemblies in the edge cloud nodes from the distributed service registration centers, the association relation between the cluster control surface assemblies in the central cloud nodes and the cluster control surface assemblies in the edge cloud nodes is established based on a service discovery mechanism, unified management of all the cluster control surface assemblies in the central cloud nodes and the edge cloud nodes is realized based on the association relation, the management complexity of cross-node container clusters in the distributed container clusters is reduced, and the management efficiency of the distributed container clusters is further improved.

Fig. 3 schematically illustrates a schematic diagram of a cluster control plane component management method flow in accordance with some embodiments of the disclosure. Referring to fig. 3, the cluster control plane component management method may include the steps of:

in step S310, acquiring, by a member cluster controller of the cluster control plane component in the central cloud node, cluster control plane component information in the edge cloud node from the distributed service registry, and accessing a cluster control plane component corresponding to the cluster control plane component information to the cluster control plane component in the central cloud node;

in step S320, based on the cluster control plane information, and the cluster control plane components corresponding to the cluster control plane information and the cluster control plane components in the central cloud node, an association relationship between the cluster control plane components in the central cloud node and the cluster control plane components in the edge cloud node is established, and the cluster control plane components are uniformly managed based on the association relationship.

The cluster control plane component information may refer to attribute information of a cluster control plane component in an edge cloud node, for example, the cluster control plane component information may be protocol parameter information of the cluster control plane component in the edge cloud node, the cluster control plane component information may also be data transmission rule information of the cluster control plane component in the edge cloud node, and the cluster control plane component information may also be identification information of the cluster control plane component in the edge cloud node.

The distributed service registration center can be established in the central cloud node, all cluster control surface assembly information in the edge cloud node is registered in the distributed service registration center, so that the cluster control surface assemblies in the edge cloud node become sub-members of the cluster control surface assemblies in the central cloud node, a member cluster controller in the cluster control surface assemblies in the central cloud node can acquire the cluster control surface assembly information in the edge cloud node from the distributed service registration center, and according to the cluster control surface assembly information in the edge cloud node and the cluster control surface assemblies corresponding to the cluster control surface assembly information in the edge cloud node and the cluster control surface assemblies in the central cloud node, the association relation between the central cloud node and all the cluster control surface assemblies in the edge cloud node is established, and all the cluster control surface assemblies in the central cloud node and the edge cloud node are managed uniformly based on the association relation, so that the management complexity and the management cost of the cluster control surface assemblies of the cross-node are reduced, and the efficiency of managing distributed container clusters is improved.

Fig. 4 schematically illustrates a schematic diagram of a component sharing method flow according to some embodiments of the present disclosure. Referring to fig. 4, the component sharing method may include the steps of:

In step S410, the configuration data of the cluster control plane component in the edge cloud node is cached and sent to the terminal cloud node;

in step S420, an association relationship with the cluster control plane component in the edge cloud node is established according to the configuration data through the terminal cluster work plane component in the terminal cloud node;

in step S430, sharing of the cluster control plane component in the edge cloud node and the terminal cluster control plane component in the terminal cloud node is configured based on the association relationship.

The method comprises the steps that connection between a terminal cluster working face component in a terminal node and a cluster control face in an edge cloud node is unstable, state data of the terminal cluster working face can be reported to the cluster control face component in the edge cloud node through a proxy component interacting with the terminal cluster working face component, and configuration data of the cluster control face component in the edge cloud node is cached and sent to the terminal cloud node, so that stable connection between the terminal cluster working face component in the terminal cloud node and the cluster control face component in the edge cloud node is ensured through the state data of the cluster working face component in the terminal cloud node and the configuration data of the cluster control face component in the edge cloud node.

The configuration data of the cluster control surface components in the edge cloud nodes can be cached and sent to the terminal cloud nodes, and the state data of the terminal cluster working surfaces in the terminal cloud nodes can be reported to the edge cloud nodes to ensure stable connection of the cluster control surface components in the edge cloud nodes and the cluster working surfaces in the terminal cloud nodes, so that the sharing of the cluster control surface components in the edge cloud nodes and the terminal cluster control surface components in the terminal cloud nodes is configured, that is, the terminal cluster working surface components in the terminal cloud nodes can be connected with the cluster control surface components in the edge cloud nodes, the cluster control surface components in the edge cloud nodes are shared to the terminal cluster control surface components in the terminal cloud nodes, meanwhile, the terminal cluster working surfaces in the terminal cloud nodes can be used as part of the cluster working surface components in the edge cloud nodes, further, application services can be deployed for the terminal cluster working surface components in the terminal cloud nodes through a dispatcher of the edge cloud nodes, the interactivity between the terminal cloud nodes and the edge cloud nodes is improved, further, the resource request-spanning efficiency of a distributed container is improved, or the resource request of an enterprise is also improved, and the user experience of a user request is improved.

Fig. 5 schematically illustrates a schematic diagram of a resource request response method flow in accordance with some embodiments of the present disclosure. Referring to fig. 5, the resource request response method may include the steps of:

in step S510, monitoring, by a scheduler corresponding to a cluster control plane component in the central cloud node, status data of a cluster working plane in the central cloud node, and sending a resource request to the scheduler corresponding to the cluster control plane component in the edge cloud node when the status data is detected to be in a busy status;

in step S520, when the scheduler corresponding to the cluster control plane component in the edge cloud node listens to the resource request, state data of the cluster plane component of the edge cloud node is obtained, and a target plane component responding to the resource request is determined based on the state data of the cluster plane component in the edge cloud node and the state data of the terminal cluster plane component.

The resource request can be distributed to the current level cluster working face node through the schedulers of the cluster control face components in the cloud nodes from top to bottom in the hierarchical structure, and if all the cluster working face components in the current level cluster working face node are in a busy state, the resource request can be scheduled to the schedulers of the cluster control face components in the next level cloud nodes through the schedulers of the current level cluster control face components, and the resource request is further distributed by the schedulers of the cluster control face components in the next level cloud nodes.

The resource request can be preferentially scheduled to the cluster working face node in the central cloud node through a scheduler corresponding to the cluster control face component in the central cloud node, state data of the cluster working face component in the central cloud node is monitored, if the cluster working face component in an idle state exists in the central cloud node, the resource request can be distributed to the cluster working face component in the idle state, and the cluster working face component in the idle state schedules the resource data to respond to the resource request; if the cluster working face components in the central cloud node are all in a busy state, the resource request can be scheduled to the cluster control face components in the edge cloud node, the scheduler corresponding to the cluster control face components in the edge cloud node distributes the resource request to the cluster working face components in the edge cloud node and monitors the state data of the cluster working face components in the edge cloud node, and if the cluster working face components in the edge cloud node have the cluster working face components in the idle state, the cluster working face components in the idle state in the edge cloud node schedule the resource data to respond to the resource request; if all cluster working face components in the edge cloud nodes are in a busy state, the resource request can be scheduled to the terminal cluster working face components in the terminal cloud nodes, and a target working face component which can meet the resource request is determined in the terminal cluster working face components, so that cross-node scheduling of the resource request in the distributed container cluster is realized, low-delay response of the resource request is further realized, and use experience of users or enterprises is improved.

Fig. 6 schematically illustrates a schematic diagram of a target work component determination method flow according to some embodiments of the present disclosure. Referring to fig. 6, the target work component determination method may include the steps of:

in step S610, when it is detected that the status data of the cluster working face component of the edge cloud node is in a busy status, the resource request is allocated to the terminal cluster working face component by a scheduler of a cluster control face in the edge cloud node;

in step S620, status data of the terminal cluster working face component is monitored, so as to determine, from the cluster working face components, a target working face component that meets the resource request according to the status data of the terminal cluster working face component.

The target working component may refer to a working component in the distributed container cluster that satisfies the resource request, for example, the target working component may be a cluster control plane component in a central cloud node in the distributed container cluster that satisfies the resource request, or the target working component may be a cluster control plane component in an edge cloud node in the distributed container cluster that satisfies the resource request, or the target working component may be a terminal cluster control plane component in a terminal cloud node in the distributed container cluster that satisfies the resource request, where the target working component may be other working components in the distributed container cluster that satisfy the resource request, and this embodiment is not limited in particular.

The resource request can be distributed to the cluster face components in the edge cloud nodes by establishing connection between the cluster control face components in the edge cloud nodes and the terminal cluster face components in the terminal cloud nodes, a scheduler corresponding to the cluster control face components in the edge cloud nodes distributes the resource request to the terminal cluster face components in the terminal cloud nodes when the cluster face components in the edge cloud nodes are all in a busy state, monitors state data of the terminal cluster face components, and determines a target face component which can meet the resource request from the terminal cluster face components according to the state data so as to schedule the resource data through the target face components, thereby realizing low-delay response of the resource request.

It should be noted that although the steps of the methods of the present disclosure are illustrated in the accompanying drawings in a particular order, this does not require or imply that the steps must be performed in that particular order or that all of the illustrated steps be performed in order to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step to perform, and/or one step decomposed into multiple steps to perform, etc.

Furthermore, in the present exemplary embodiment, a distributed container cluster management apparatus is also provided. Referring to fig. 7, the distributed container cluster management apparatus 700 includes: component deployment module 710, component management module 720, resource request response module 730. Wherein: the component deployment module 710 is configured to sequentially deploy cluster components at a center cloud node and an edge cloud node respectively according to a hierarchical structure through a global cluster controller, and deploy terminal cluster working face components at terminal cloud nodes; the cluster assembly comprises a cluster control surface assembly and a cluster working surface assembly; the component management module 720 is configured to establish an association relationship between a cluster control plane component in the central cloud node and a cluster control plane component in the edge cloud node based on a service discovery mechanism, and uniformly manage the cluster control plane components based on the association relationship; and the resource request response module 730 is configured to acquire status data of the cluster working face component and the terminal cluster working face component by adopting a monitoring mechanism when a resource request is received, and determine a target working face component from the cluster working face component and the terminal cluster working face according to the status data, so as to schedule service data matched with the resource request through the target working face component, thereby realizing cross-node scheduling of the service data.

In some example embodiments of the present disclosure, based on the foregoing solution, the component deployment module 710 further includes a container engine deployment unit, where the container engine deployment unit is configured to sequentially deploy, by the global cluster controller, a standard container engine and a mirror warehouse at the central cloud node and the edge cloud node, respectively, according to the hierarchical structure, and deploy, by the terminal node, a custom container engine, so as to provide, by using the mirror warehouse, a mirror image of the standard container engine and a mirror image of the custom container engine, and a download service of a mirror image of the cluster component and a mirror image of the terminal cluster working surface component.

In some example embodiments of the present disclosure, based on the foregoing solution, the component management module 720 further includes a service registry deployment unit, where the service registry deployment unit is configured to deploy a distributed service registry at the central cloud node to register the cluster control plane component of the edge cloud node to the distributed service registry.

In some example embodiments of the present disclosure, based on the foregoing solution, the component management module 720 includes an association relationship establishing unit, where the association relationship establishing unit is configured to obtain, by a member cluster controller of the cluster control plane component in the central cloud node, cluster control plane component information of the edge cloud node from the distributed service registry, and access a cluster control plane component corresponding to the cluster control plane component information to a cluster control plane component in the central cloud node; based on the cluster control plane information, the cluster control plane components corresponding to the cluster control plane information and the cluster control plane components in the central cloud node, establishing an association relationship between the cluster control plane components in the central cloud node and the cluster control plane components in the edge cloud node, and uniformly managing the cluster control plane components based on the association relationship.

In some example embodiments of the present disclosure, based on the foregoing solution, the distributed container cluster management apparatus 700 further includes a component sharing module, where the component sharing module is configured to cache and send configuration data of a cluster control plane component of the edge cloud node to the terminal cloud node; establishing an association relationship with a cluster control plane component in the edge cloud node according to the configuration data through a terminal cluster working plane component in the terminal cloud node; and configuring sharing of the cluster control plane components in the edge cloud nodes and the terminal cluster control plane components in the terminal cloud nodes based on the association relation.

In some example embodiments of the present disclosure, based on the foregoing solutions, the resource request response module 730 includes a resource request scheduling unit, where the resource request scheduling unit is configured to monitor, by a scheduler corresponding to a cluster control plane component in the central cloud node, status data of a cluster working plane in the central cloud node, and send, when the status data is detected to be in a busy state, a resource request to the scheduler corresponding to the cluster control plane component in the edge cloud node; and when the dispatcher in the edge cloud node monitors the resource request, acquiring state data of the cluster working face component in the edge cloud node, and determining a target working face component responding to the resource request based on the state data of the cluster working face component in the edge cloud node and the state data of the terminal cluster working face component.

In some example embodiments of the present disclosure, based on the foregoing solution, the resource request response module 730 further includes a target working face component determining unit, where the target working face component determining unit is configured to allocate, when detecting that status data of a cluster working face component in the edge cloud node is in a busy state, the resource request to the terminal cluster working face component through a scheduler of a cluster control face in the edge cloud node; and monitoring the state data of the terminal cluster working face component to determine a target working face component meeting the resource request from the cluster working face components according to the state data of the terminal cluster working face component.

The specific details of each module of the distributed container cluster management device are described in detail in the corresponding distributed container cluster management method, so that the details are not repeated here.

It should be noted that although in the above detailed description several modules or units of a distributed container cluster management arrangement are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit in accordance with embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.

In addition, in an exemplary embodiment of the present disclosure, an electronic device capable of implementing the above distributed container cluster management method is also provided.

Those skilled in the art will appreciate that the various aspects of the present disclosure may be implemented as a system, method, or program product. Accordingly, various aspects of the disclosure may be embodied in the following forms, namely: an entirely hardware embodiment, an entirely software embodiment (including firmware, micro-code, etc.) or an embodiment combining hardware and software aspects may be referred to herein as a "circuit," module "or" system.

An electronic device 800 according to such an embodiment of the present disclosure is described below with reference to fig. 8. The electronic device 800 shown in fig. 8 is merely an example and should not be construed as limiting the functionality and scope of use of embodiments of the present disclosure.

As shown in fig. 8, the electronic device 800 is embodied in the form of a general purpose computing device. Components of electronic device 800 may include, but are not limited to: the at least one processing unit 810, the at least one storage unit 820, a bus 830 connecting the different system components (including the storage unit 820 and the processing unit 810), and a display unit 840.

Wherein the storage unit stores program code that is executable by the processing unit 810 such that the processing unit 810 performs steps according to various exemplary embodiments of the present disclosure described in the above section of the present specification. For example, the processing unit 810 may perform step S110 shown in fig. 1, sequentially deploy cluster components at a central cloud node and an edge cloud node respectively according to a hierarchical structure by using a global cluster controller, and deploy terminal cluster working surface components at terminal cloud nodes; the cluster assembly comprises a cluster control surface assembly and a cluster working surface assembly; step S120, based on a service discovery mechanism, establishing an association relationship between a cluster control plane component in the central cloud node and a cluster control plane component in the edge cloud node, and uniformly managing the cluster control plane components based on the association relationship; and step S130, when a resource request is received, acquiring state data of the cluster working face component and the terminal cluster working face component by adopting a monitoring mechanism, and determining a target working face component from the cluster working face component and the terminal cluster working face component according to the state data so as to realize low-delay response of the resource request through the target working face component.

Storage unit 820 may include readable media in the form of volatile storage units such as Random Access Memory (RAM) 821 and/or cache memory unit 822, and may further include Read Only Memory (ROM) 823.

The storage unit 820 may also include a program/utility 824 having a set (at least one) of program modules 825, such program modules 825 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.

Bus 830 may be one or more of several types of bus structures including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

The electronic device 800 may also communicate with one or more external devices 870 (e.g., keyboard, pointing device, bluetooth device, etc.), one or more devices that enable a user to interact with the electronic device 800, and/or any device (e.g., router, modem, etc.) that enables the electronic device 800 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 850. Also, electronic device 800 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet, through network adapter 860. As shown, network adapter 860 communicates with other modules of electronic device 800 over bus 830. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 800, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.

From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or in combination with the necessary hardware. Thus, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.) or on a network, and includes several instructions to cause a computing device (may be a personal computer, a server, a terminal device, or a network device, etc.) to perform the method according to the embodiments of the present disclosure.

In an exemplary embodiment of the present disclosure, a computer-readable storage medium having stored thereon a program product capable of implementing the method described above in the present specification is also provided. In some possible embodiments, the various aspects of the present disclosure may also be implemented in the form of a program product comprising program code for causing a terminal device to carry out the steps according to the various exemplary embodiments of the disclosure as described in the "exemplary methods" section of this specification, when the program product is run on the terminal device.

Referring to fig. 9, a program product 900 for implementing the distributed container cluster management method described above, which may employ a portable compact disc read-only memory (CD-ROM) and include program code, and which may run on a terminal device, such as a personal computer, is described according to an embodiment of the present disclosure. However, the program product of the present disclosure is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium would include the following: an electrical connection having one or more wires, a portable disk, a hard disk, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

The computer readable signal medium may include a data signal propagated in baseband or as part of a carrier wave with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Program code for carrying out operations of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).

Furthermore, the above-described figures are only schematic illustrations of processes included in the method according to the exemplary embodiments of the present disclosure, and are not intended to be limiting. It will be readily appreciated that the processes shown in the above figures do not indicate or limit the temporal order of these processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, for example, among a plurality of modules.

From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or in combination with the necessary hardware. Thus, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.) or on a network, and includes several instructions to cause a computing device (may be a personal computer, a server, a touch terminal, or a network device, etc.) to perform the method according to the embodiments of the present disclosure.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any adaptations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A method for cluster management of distributed containers, comprising:

sequentially deploying cluster components at a center cloud node and an edge cloud node respectively according to a hierarchical structure through a global cluster controller, and deploying terminal cluster working face components at terminal cloud nodes; the cluster assembly comprises a cluster control surface assembly and a cluster working surface assembly;

based on a service discovery mechanism, establishing an association relationship between a cluster control plane component in the central cloud node and a cluster control plane component in the edge cloud node, and uniformly managing the cluster control plane components based on the association relationship;

when a resource request is received, a monitoring mechanism is adopted to acquire state data of the cluster working face component and the terminal cluster working face component, and a target working face component is determined from the cluster working face component and the terminal cluster working face component according to the state data so as to realize low-delay response of the resource request through the target working face component.

2. The distributed container cluster management method of claim 1, further comprising:

and sequentially deploying a standard container engine and a mirror warehouse at the central cloud node and the edge cloud node respectively through the global cluster controller according to the hierarchical structure, and deploying a custom container engine at the terminal node so as to provide a mirror image of the standard container engine and a mirror image of the custom container engine as well as a mirror image of the cluster component and a download service of a mirror image of the terminal cluster working face component through the mirror warehouse.

3. The distributed container cluster management method of claim 1, further comprising:

and deploying a distributed service registry at the central cloud node to register the cluster control plane component of the edge cloud node to the distributed service registry.

4. The distributed container cluster management method according to claim 1, wherein the establishing an association relationship between a cluster control plane component in the central cloud node and a cluster control plane component in the edge cloud node, and managing the cluster control plane components in a unified manner based on the association relationship, comprises:

Acquiring cluster control plane component information in the edge cloud node from the distributed service registry by a member cluster controller of the cluster control plane component in the center cloud node, and accessing a cluster control plane component corresponding to the cluster control plane component information to the cluster control plane component in the center cloud node;

and establishing an association relationship between the cluster control plane components in the central cloud node and the cluster control plane components in the edge cloud node based on the cluster control plane information, the cluster control plane components corresponding to the cluster control plane information and the cluster control plane components of the central cloud node, and uniformly managing the cluster control plane components based on the association relationship.

5. The distributed container cluster management method of claim 1, further comprising:

caching the configuration of the cluster control plane component in the edge cloud node and sending the configuration to the terminal cloud node;

establishing an association relationship with a cluster control plane component in the edge cloud node according to the configuration data through a terminal cluster working plane component in the terminal cloud node;

And configuring sharing of the cluster control plane components in the edge cloud nodes and the terminal cluster control plane components in the terminal cloud nodes based on the association relation.

6. The distributed container cluster management method according to claim 1, wherein the acquiring state data of the cluster face component and the terminal cluster face component by using a listening mechanism, and determining a target face component from the cluster face component and the terminal cluster face according to the state data, includes:

monitoring state data of a cluster working face in the central cloud node through a scheduler corresponding to a cluster control face component in the central cloud node, and sending a resource request to the scheduler corresponding to the cluster control face component in the edge cloud node when the state data is detected to be in a busy state;

when a dispatcher corresponding to a cluster control surface component in the edge cloud node monitors the resource request, acquiring state data of the cluster working surface component of the edge cloud node, and determining a target working surface component responding to the resource request based on the state data of the cluster working surface component of the edge cloud node and the state data of the terminal cluster working surface component.

7. The distributed container cluster management method of claim 6, wherein the determining a target face component responsive to the resource request based on the state data of the cluster face component of the edge cloud node and the state data of the terminal cluster face component comprises:

when the state data of the cluster working face component in the edge cloud node is detected to be in a busy state, distributing the resource request to the terminal cluster working face component through a scheduler in a cluster control face in the edge cloud node;

and monitoring the state data of the terminal cluster working face component to determine a target working face component meeting the resource request from the cluster working face components according to the state data of the terminal cluster working face component.

8. A distributed container cluster management apparatus, comprising:

the component deployment module is used for sequentially deploying cluster components at the center cloud node and the edge cloud node respectively according to a hierarchical structure through the global cluster controller, and deploying terminal cluster working face components at the terminal cloud node; the cluster assembly comprises a cluster control surface assembly and a cluster working surface assembly;

The component management module is used for establishing an association relation between the cluster control plane components in the central cloud node and the cluster control plane components in the edge cloud node based on a service discovery mechanism, and uniformly managing the cluster control plane components based on the association relation;

and the resource request response module is used for acquiring the state data of the cluster working face component and the terminal cluster working face component by adopting a monitoring mechanism when a resource request is received, and determining a target working face component from the cluster working face component and the terminal cluster working face according to the state data so as to schedule service data matched with the resource request through the target working face component and realize cross-node scheduling of the service data.

9. An electronic device, comprising:

a processor; and

a memory having stored thereon computer readable instructions which when executed by the processor implement the distributed container cluster management method of any of claims 1 to 7.

10. A computer readable storage medium having stored thereon a computer program which when executed by a processor implements the distributed container cluster management method of any of claims 1 to 7.