CN115396441A - A kind of Kubernetes multi-cluster management method, device, equipment, storage medium - Google Patents

Abstract

The application discloses a Kubernetes multi-cluster management method, a Kubernetes multi-cluster management device, kubernetes multi-cluster management equipment and a Kubernetes multi-cluster management storage medium, which are applied to a main management cluster, relate to the technical field of cluster management and comprise the following steps: deploying preset agent programs for other Kubernets outside the master management cluster to obtain the slave management cluster; sending a management instruction to the slave management cluster so that the preset agent program can call a corresponding test case to collect cluster information of the slave management cluster and generate corresponding return information; and receiving returned information to realize management of the Kubernetes multi-cluster. The kubernets cluster is managed by deploying a pre-set agent. The main management cluster directly issues an instruction to a preset agent program. And directly accessing the K8S Apiserver by using a preset agent program, further controlling each cluster by using the API, and collecting data or controlling the cluster so as to realize management of the Kubernetes multi-cluster.

Description

A kind of Kubernetes multi-cluster management method, device, equipment, storage medium

technical field

The present invention relates to the technical field of cluster management, in particular to a Kubernetes multi-cluster management method, device, equipment, and storage medium.

Background technique

Whether it is a private cloud or a public cloud, there will be a large number of K8S (Kubernetes) clusters that need to be managed. These clusters do not have a unified management platform, which greatly increases the difficulty of operation and maintenance. Each cluster is different. Network plug-ins, different K8S versions, and even clusters for secondary development of K8S components, because existing solutions such as KubeFederation need to extend K8S API (ApplicationProgramInterface, application programming interface) when implementing multi-cluster management. Modify the original K8S API, and need to modify multiple configurations. The deployment is extremely complicated and cumbersome. For those who are not familiar with KubeFederation, the learning cost is extremely high, and the storage information is stored in the respective etcd through the K8S CRD, while These cluster information, authentication information, and user information are different for each cluster. This storage method is prone to information inconsistency, which eventually leads to problems in multi-cluster management. The existing patent CN202111462252.2 mentions unified management of multiple Kubernetes clusters through a custom declarative API. This method will make the API of the entire K8S too bloated, and a large number of CRDs need to be written and generated. When a CRD appears Problems can easily cause the entire cluster to crash and become unusable. In the existing patent CN202111018688.2, the cluster management scheduling module is used to manage multiple clusters, and a registration and management scheduling module needs to be developed separately.

To sum up, how to improve the efficiency of inter-cluster communication and management, avoid the problems of overly complex, unstable, and inconsistent cluster management, and realize simple, efficient, and consistent multi-cluster management are technical problems to be solved in this field.

Contents of the invention

In view of this, the object of the present invention is to provide a Kubernetes multi-cluster management method, device, equipment, and storage medium, which can improve the efficiency of inter-cluster communication and management, avoid the problems of too complicated, unstable, and inconsistent cluster management, and realize Simple, efficient, and consistent multi-cluster management. The specific plan is as follows:

In the first aspect, the application discloses a Kubernetes multi-cluster management method, which is applied to the main management cluster, including:

Deploying preset agents for other Kubernetes clusters other than the master management cluster to obtain slave management clusters;

Send a management instruction to the slave management cluster, so that the preset agent program calls the corresponding test case to collect the cluster information of the slave management cluster, and generates corresponding return information;

The feedback information is received to realize the management of Kubernetes multi-clusters.

Optionally, before deploying preset agents for other Kubernetes clusters other than the main management cluster, it also includes:

Deploy the preset master program to the Kubernetes cluster to obtain the master management cluster.

Optionally, the preset master program is deployed to the Kubernetes cluster to obtain the master management cluster, including:

Modify the configuration information of the Kubernetes cluster, and deploy the preset master program through the yaml file to obtain the master management cluster.

Optionally, before deploying preset agents for other Kubernetes clusters other than the main management cluster, it also includes:

Perform communication protocol encapsulation on the preset agent program.

Optionally, the receiving the feedback information to realize the management of Kubernetes multi-clusters includes:

Adding the cluster information of the slave management cluster through a graphical interface in advance;

Enter the kubeconfig of the cluster through the preset program interface to display the corresponding feedback information to manage Kubernetes multi-clusters.

Optionally, after receiving the feedback information to realize the management of Kubernetes multi-clusters, it also includes:

The target information in the returned information is saved in a local database based on user requirements.

In the second aspect, the present application discloses a Kubernetes multi-cluster management method, which is applied to the slave management cluster, including:

Receive the management instruction sent by the master management cluster, use the master management cluster to pre-call the corresponding test case for the preset agent deployed by the slave management cluster, collect the cluster information of the slave management cluster, and generate corresponding return information ;

Sending the feedback information to the main management cluster, so that the main management cluster can manage Kubernetes multi-clusters.

In a third aspect, the present application discloses a Kubernetes multi-cluster management device, which is applied to the main management cluster, including:

A program deployment module, configured to deploy preset agent programs for other Kubernetes clusters outside the main management cluster, so as to obtain slave management clusters;

An information collection module, configured to send a management instruction to the slave management cluster, so that the preset agent program calls a corresponding test case to collect the cluster information of the slave management cluster, and generates corresponding return information;

An information receiving module, configured to receive the feedback information, so as to realize the management of Kubernetes multi-clusters.

In a fourth aspect, the present application discloses an electronic device, comprising:

memory for storing computer programs;

The processor is configured to execute the computer program, so as to realize the steps of the aforementioned disclosed Kubernetes multi-cluster management method.

In a fifth aspect, the present application discloses a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, the steps of the aforementioned disclosed Kubernetes multi-cluster management method are implemented.

It can be seen that the present application discloses a Kubernetes multi-cluster management method, which is applied to the main management cluster, including: deploying preset agent programs for other Kubernetes clusters outside the main management cluster to obtain the slave management cluster; sending management instructions to all Describe from the management cluster, so that the preset agent calls the corresponding test case to collect the cluster information from the management cluster, and generate corresponding return information; receive the return information, to realize the management of Kubernetes multi-cluster . It can be seen that the present application manages the Kubernetes cluster by deploying a preset agent program. The main management cluster directly issues instructions to the preset agent program. Use the preset agent program to directly access the K8S Apiserver, and then use the API to control each cluster, collect data or control the cluster, so as to realize the management of Kubernetes multi-cluster.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only It is an embodiment of the present invention, and those skilled in the art can also obtain other drawings according to the provided drawings without creative work.

Fig. 1 is a flow chart of a kind of Kubernetes multi-cluster management method disclosed by the application;

Fig. 2 is a flow chart of a master cluster management agent cluster disclosed by the present application;

Fig. 3 is a kind of specific Kubernetes multi-cluster management method flowchart disclosed by the present application;

Fig. 4 fills in code for a kind of target cluster KubeConfig disclosed in this application;

Fig. 5 is another kind of specific Kubernetes multi-cluster management method flowchart disclosed in the present application;

Fig. 6 is a schematic structural diagram of a Kubernetes multi-cluster management device disclosed in the present application;

FIG. 7 is a structural diagram of an electronic device disclosed in the present application.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present invention, not all of them. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

Whether it is a private cloud or a public cloud, there will be a large number of K8S clusters that need to be managed. These clusters do not have a unified management platform, which greatly increases the difficulty of operation and maintenance. Each cluster is different, and different network plug-ins, Different K8S versions, and even clusters for secondary development of K8S components, because existing solutions such as KubeFederation need to expand the K8S API when implementing multi-cluster management. Modify the original K8S API, and need to modify multiple configurations. The deployment is extremely complicated and cumbersome. For those who are not familiar with KubeFederation, the learning cost is extremely high, and the storage information is stored in the respective etcd through the K8S CRD, while These cluster information, authentication information, and user information are different for each cluster. This storage method is prone to information inconsistency, which eventually leads to problems in multi-cluster management. The existing patent CN202111462252.2 mentions unified management of multiple Kubernetes clusters through a custom declarative API. This method will make the API of the entire K8S too bloated, and a large number of CRDs need to be written and generated. When a CRD appears Problems can easily cause the entire cluster to crash and become unusable. In the existing patent CN202111018688.2, the cluster management scheduling module is used to manage multiple clusters, and a registration and management scheduling module needs to be developed separately.

Therefore, this application discloses a Kubernetes multi-cluster management solution, which can improve the efficiency of inter-cluster communication and management, avoid the problems of overly complex, unstable and inconsistent cluster management, and realize simple, efficient and consistent multi-cluster management.

Referring to Fig. 1, the embodiment of the present invention discloses a Kubernetes multi-cluster management method, which is applied to the main management cluster, including:

Step S11: Deploy preset agent programs for other Kubernetes clusters other than the master management cluster, so as to obtain slave management clusters.

In this embodiment, as shown in FIG. 2 , use the program development language Golong to write the multi-cloud management agent program, and deploy the written multi-cloud management agent program to other Kubernetes clusters except the main management cluster, wherein, during the deployment process, It is necessary to modify the configuration in the slave management cluster in the yaml file. After the modification is completed, execute the corresponding deployment command in the slave management cluster to deploy the agent component to the agent cluster to obtain the slave management cluster. For example: deploy a kubernetes agent cluster. Modify the configuration in the agent cluster under the clusterdeployment.yaml file: modify Clustername: b-idc-sjzntest-20220215, modify clusterRole: agent and jwtSecret: "OrZpAUpoAxZRdOjiPQ1A4tRgXNnxtotD". After the modification is completed, deploy the agent component to the agent cluster by executing the command kubectlapply–fclusterdeployment.yaml in the agetn cluster. Among them, the implementation of the code from the management cluster is as follows:

In this embodiment, referring to FIG. 2 , before deploying preset agent programs for other Kubernetes clusters other than the master management cluster, it further includes: deploying a preset master program to the Kubernetes cluster to obtain a master management cluster. It is understandable that the program development language Golong is used to write the master program, and the written master program is deployed to the main management cluster. During the deployment process, the configuration in the main management cluster needs to be modified in the yaml file. The modification is completed through Execute the corresponding deployment command in the main management cluster to deploy the master program to the main management cluster. It is necessary to compile and package the image in advance, and then deploy the master program through the yaml file. For example: first deploy a kubernetes cluster, and then modify the clusterdeployment.yamlmaster cluster configuration, modify Clustername:host, modify clusterRole:host and jwtSecret:"" to be empty, and execute the command kubectlapply–f clusterdeployment.yaml in the master cluster to deploy the master component to the master cluster after the modification is completed. After the deployment is complete, use the command kubectl get secret clusterdeployment|grep-v"apiVersion"|grepjwtSecret to get jwtSecret, the main management cluster deployment code is as follows:

In this embodiment, before deploying the preset agent program for other Kubernetes clusters other than the main management cluster, it further includes: performing communication protocol encapsulation on the preset agent program. It can be understood that, by encapsulating the communication technology in the agent, the agent can directly use the agent to issue instructions to the kube-apiserver, which saves the cumbersome steps of communicating with the CRD for managing the slave management cluster.

Step S12: sending a management instruction to the slave management cluster, so that the preset agent program invokes a corresponding test case to collect the cluster information of the slave management cluster, and generates corresponding return information.

In this embodiment, the master directly issues instructions to the agent. The agent directly accesses the K8S apiserver. Manipulate the agent cluster, display the agent cluster data, and manage the agent cluster. It is understandable that the master issues instructions to the multi-cloud management agent through the interface, and the multi-cloud management agent interface command calls the K8S API to complete the management and control of the agent cluster, and generates corresponding feedback information. It should be noted that, This embodiment does not need to expand the API of K8S when implementing multi-cluster management, neither the agent nor the master is pouring in, and there is no need to add or modify API resources of K8S, or modify the original K8Sapi or modify multiple configurations. The master issues corresponding management instructions to the agent so that the agent can directly call the original K8S API for management or control. The deployment is simple, the learning cost is low, a large number of custom resources are saved, the CRD is streamlined, and various problems caused by CRD failures are avoided. kind of problem.

Step S13: Receive the feedback information, so as to realize the management of Kubernetes multi-clusters.

In this embodiment, the multi-cloud management agent returns information to the master cluster to display resource information or return processing results, which can improve the efficiency of inter-cluster communication and management, realize multi-cluster management through agent and master communication, and achieve multi-cluster management through master cluster To manage the agent cluster.

In this embodiment, after receiving the returned information to realize the management of Kubernetes multi-clusters, it further includes: saving the target information in the returned information to a local database based on user requirements. It can be understood that when the returned information includes the corresponding target information required by the user, the target information needs to be stored accordingly.

It can be seen that the present application discloses a Kubernetes multi-cluster management method, which is applied to the main management cluster, including: deploying preset agent programs for other Kubernetes clusters outside the main management cluster to obtain the slave management cluster; sending management instructions to all Describe from the management cluster, so that the preset agent calls the corresponding test case to collect the cluster information from the management cluster, and generate corresponding return information; receive the return information, to realize the management of Kubernetes multi-cluster . It can be seen that the present application manages the Kubernetes cluster by deploying a preset agent program. The main management cluster directly issues instructions to the preset agent program. Use the preset agent program to directly access the K8S Apiserver, and then use the API to control each cluster, collect data or control the cluster, so as to realize the management of Kubernetes multi-cluster.

Referring to FIG. 3 , the embodiment of the present invention discloses a specific Kubernetes multi-cluster management method, which is applied to the main management cluster. Compared with the previous embodiment, this embodiment further explains and optimizes the technical solution. specific:

Step S21: modify the configuration information of the Kubernetes cluster, and deploy a preset master program through a yaml file to obtain the master management cluster.

In this embodiment, the configuration information of the Kubernetes cluster is modified in advance. Since there is no direct communication between the existing Kubernetes multi-clusters, if the master management cluster is used to manage other slave management clusters, the Kubernetes multi-cluster For the management and control of K8S, it is necessary to modify the configuration information of the Kubernetes cluster accordingly, and deploy the self-developed back-end program to the Kubernetes cluster to realize K8S multi-cloud management. Therefore, it is necessary to modify the yaml file of the pre-deployed Kubernetes cluster , and then deploy a preset master program in the Kubernetes cluster to obtain the master management cluster.

Step S22: Deploy preset agent programs for other Kubernetes clusters other than the master management cluster, so as to obtain slave management clusters.

Step S23: sending a management instruction to the slave management cluster, so that the preset agent program invokes a corresponding test case to collect the cluster information of the slave management cluster, and generates corresponding return information.

Wherein, for more detailed processing procedures in steps S22 and S23, please refer to the foregoing disclosed embodiments, and details are not repeated here.

Step S24: add the cluster information of the slave management cluster through the graphical interface in advance; input the kubeconfig of the cluster through the preset program interface, so as to display the corresponding returned information to realize the management of the Kubernetes multi-cluster.

In this embodiment, the master and the agent will automatically identify the information. In the master cluster, the cluster information can be obtained by commanding kubectl getcluster, and then realize the control and management of the slave management cluster. The development platform uses react to write the front end of the platform, and uses the graphical Interface to manage multi-cloud management agent clusters. Add the corresponding cluster through the graphical interface. Referring to Figure 4, inputting the kubeconfig of the agent cluster enables the master cluster to manage multiple clusters, and the master cluster directly saves the agent cluster information in the mysql database. Due to the direct connection to the mysql database, the cluster information is stored in the database, whether it is modifying the agent cluster or the master cluster, it will be synchronized to the database, avoiding that the storage information of the previous cluster is stored in the respective ETCD through the K8S CRD, and these clusters Information, authentication information, user information, etc. are different for each cluster. This storage method is prone to information inconsistency, which will eventually lead to problems in multi-cluster management. In , the key information is stored through the mysql database, which avoids the data inconsistency problem in ETCD storage.

It can be seen that this application stores the associated information in the database through the master and the multi-cloud management agent, which avoids the problem of data inconsistency in ETCD storage, and the implementation of the embodiment of the application has fewer modules in the process of implementing management control from the management cluster. Reduce the learning cost of K8S multi-cluster management. No need for CRD deployment, no bloated K8S api extension, directly encapsulate the function in the program to achieve multi-cluster management, no need for ETCD, no need to store data in ETCD, just deploy agent and master programs.

Referring to FIG. 5 , the embodiment of the present invention discloses a specific Kubernetes multi-cluster management method, which is applied to slave management clusters. Compared with the previous embodiment, this embodiment further explains and optimizes the technical solution. specific:

Step S31: Receive the management instruction sent by the master management cluster, use the master management cluster to pre-call the corresponding test case for the preset agent program deployed by the slave management cluster to collect the cluster information of the slave management cluster, and generate the corresponding Return information.

In this embodiment, the slave management cluster receives the management command sent by the master management cluster through the interface, and calls the API of the Kubernetes cluster based on the agent program deployed in the slave management cluster in advance to collect the cluster information of the slave management cluster, and generates a corresponding response pass on information.

Step S32: Send the feedback information to the main management cluster, so that the main management cluster can realize the management of Kubernetes multi-clusters.

In this embodiment, the feedback information is sent to the main management cluster, and based on user requirements, the corresponding cluster information is selected and stored directly in the mysql database instead of in the respective ETCD of the Kubernetes cluster, so as to avoid the Inconsistencies in information caused by different data storage methods lead to problems in multi-cluster management.

It can be seen that the present application discloses a Kubernetes multi-cluster management method, which is applied to the main management cluster, including: deploying preset agent programs for other Kubernetes clusters outside the main management cluster to obtain the slave management cluster; sending management instructions to all Describe from the management cluster, so that the preset agent calls the corresponding test case to collect the cluster information from the management cluster, and generate corresponding return information; receive the return information, to realize the management of Kubernetes multi-cluster . It can be seen that the present application manages the Kubernetes cluster by deploying a preset agent program. The main management cluster directly issues instructions to the preset agent program. Use the preset agent program to directly access the K8S Apiserver, and then use the API to control each cluster, collect data or control the cluster, so as to realize the management of Kubernetes multi-cluster.

Referring to Figure 6, the embodiment of the present invention discloses a specific Kubernetes multi-cluster management device, which is applied to the main management cluster, including:

The program deployment module 11 is used for deploying preset agent programs for other Kubernetes clusters outside the main management cluster, so as to obtain the slave management cluster;

An information collection module 12, configured to send a management instruction to the slave management cluster, so that the preset agent program invokes a corresponding test case to collect the cluster information of the slave management cluster, and generate corresponding return information;

The information receiving module 13 is configured to receive the feedback information, so as to realize the management of Kubernetes multi-clusters.

It can be seen that the present application discloses a Kubernetes multi-cluster management method, which is applied to the main management cluster, including: deploying preset agent programs for other Kubernetes clusters outside the main management cluster to obtain the slave management cluster; sending management instructions to all Describe from the management cluster, so that the preset agent calls the corresponding test case to collect the cluster information from the management cluster, and generate corresponding return information; receive the return information, to realize the management of Kubernetes multi-cluster . It can be seen that the present application manages the Kubernetes cluster by deploying a preset agent program. The main management cluster directly issues instructions to the preset agent program. Use the preset agent program to directly access the K8S Apiserver, and then use the API to control each cluster, collect data or control the cluster, so as to realize the management of Kubernetes multi-cluster.

In some specific implementation manners, the program deployment module 11 may specifically include:

The cluster deployment sub-module is used to deploy the preset master program to the Kubernetes cluster to obtain the master management cluster.

In some specific implementation manners, the cluster deployment submodule may specifically include:

An information modification unit, configured to modify the configuration information of the Kubernetes cluster, and deploy the preset master program through a yaml file to obtain the master management cluster.

In some specific implementation manners, the program deployment module 11 may specifically include:

A protocol encapsulation unit, configured to perform communication protocol encapsulation on the preset agent program.

In some specific implementation manners, the information receiving module 13 may specifically include:

The information receiving unit is used to pre-add the cluster information of the slave management cluster through a graphical interface; input the kubeconfig of the cluster through a preset program interface, so as to display corresponding feedback information to realize the management of Kubernetes multi-clusters.

In some specific implementation manners, the information receiving module 13 may specifically include:

The information saving unit is configured to save the target information in the returned information into a local database based on user requirements.

Further, the embodiment of the present application also discloses an electronic device. FIG. 7 is a structural diagram of an electronic device 20 according to an exemplary embodiment. The content in the figure should not be regarded as any limitation on the application scope of the present application.

FIG. 7 is a schematic structural diagram of an electronic device 20 provided by an embodiment of the present application. The electronic device 20 may specifically include: at least one processor 21 , at least one memory 22 , a power supply 23 , a communication interface 24 , an input/output interface 25 and a communication bus 26 . Wherein, the memory 22 is used to store a computer program, and the computer program is loaded and executed by the processor 21 to implement relevant steps in the Kubernetes multi-cluster management method disclosed in any of the foregoing embodiments. In addition, the electronic device 20 in this embodiment may specifically be an electronic computer.

In this embodiment, the power supply 23 is used to provide working voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol it follows is applicable Any communication protocol in the technical solution of the present application is not specifically limited here; the input and output interface 25 is used to obtain external input data or output data to the external, and its specific interface type can be selected according to specific application needs, here Not specifically limited.

Wherein, the processor 21 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and the like. The processor 21 may be implemented in at least one hardware form among DSP (Digital Signal Processing, digital signal processing), FPGA (Field-Programmable Gate Array, field programmable gate array), and PLA (Programmable Logic Array, programmable logic array). Processor 21 may also include a main processor and a coprocessor, the main processor is a processor for processing data in a wake-up state, also called CPU (Central Processing Unit, central processing unit); the coprocessor is used for A low-power processor that processes data during standby. In some embodiments, the processor 21 may be integrated with a GPU (Graphics Processing Unit, image processor), and the GPU is used for rendering and drawing the content to be displayed on the display screen. In some embodiments, the processor 21 may further include an AI (Artificial Intelligence, artificial intelligence) processor, where the AI processor is configured to process computing operations related to machine learning.

In addition, the memory 22, as a resource storage carrier, can be a read-only memory, random access memory, magnetic disk or optical disk, etc., and the resources stored thereon can include operating system 221, computer program 222, etc., and the storage method can be temporary storage or permanent storage. .

Wherein, the operating system 221 is used to manage and control each hardware device and computer program 222 on the electronic device 20, so as to realize the calculation and processing of the massive data 223 in the memory 22 by the processor 21, which can be Windows Server, Netware, Unix, Linux, etc. In addition to computer programs that can be used to complete the Kubernetes multi-cluster management method performed by the electronic device 20 disclosed in any of the foregoing embodiments, the computer program 222 can further include computer programs that can be used to complete other specific tasks. The data 223 may not only include data received by the electronic device and transmitted from an external device, but may also include data collected by its own input and output interface 25 and the like.

Further, the present application also discloses a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, the aforementioned disclosed Kubernetes multi-cluster management method is implemented. Regarding the specific steps of the method, reference may be made to the corresponding content disclosed in the foregoing embodiments, and details are not repeated here.

Each embodiment in this specification is described in a progressive manner, each embodiment focuses on the difference from other embodiments, and the same or similar parts of each embodiment can be referred to each other. As for the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and for the related information, please refer to the description of the method part.

Professionals can further realize that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, computer software or a combination of the two. In order to clearly illustrate the possible For interchangeability, in the above description, the composition and steps of each example have been generally described according to their functions. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application. The steps of the methods or algorithms described in connection with the embodiments disclosed herein may be directly implemented by hardware, software modules executed by a processor, or a combination of both. Software modules can be placed in random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other Any other known storage medium.

Finally, it should also be noted that in this text, relational terms such as first and second etc. are only used to distinguish one entity or operation from another, and do not necessarily require or imply that these entities or operations, any such actual relationship or order exists. Furthermore, the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article or apparatus comprising a set of elements includes not only those elements, but also includes elements not expressly listed. other elements of or also include elements inherent in such a process, method, article, or device. Without further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article or apparatus comprising said element.

A kind of Kubernetes multi-cluster management method, device, equipment, and storage medium provided by the present invention have been introduced in detail above. In this paper, specific examples have been used to illustrate the principle and implementation of the present invention. The description of the above embodiments is only used To help understand the method of the present invention and its core idea; at the same time, for those of ordinary skill in the art, according to the idea of the present invention, there will be changes in the specific implementation and scope of application. In summary, this specification The content should not be construed as a limitation of the invention.

Claims (10)

1. A Kubernetes multi-cluster management method is applied to a main management cluster and comprises the following steps:

deploying preset agent programs for other Kubernets clusters outside the main management cluster to obtain a slave management cluster;

sending a management instruction to the slave management cluster so that the preset agent program calls a corresponding test case to collect cluster information of the slave management cluster and generate corresponding return information;

and receiving the returned information to realize management of the Kubernetes multi-cluster.

2. The kubernets multi-cluster management method according to claim 1, wherein before deploying a preset agent program for another kubernets cluster outside the primary management cluster, the method further comprises:

and deploying a preset master program for the Kubernetes cluster to obtain a main management cluster.

3. The kubernets multi-cluster management method of claim 2, wherein the deploying a preset master program to the kubernets cluster to obtain a master management cluster comprises:

and modifying the configuration information of the Kubernetes cluster, and deploying the preset master program through a yaml file to obtain the main management cluster.

4. The kubernets multi-cluster management method according to claim 1, wherein before deploying a preset agent program for another kubernets cluster outside the primary management cluster, the method further comprises:

and carrying out communication protocol encapsulation on the preset agent program.

5. The kubernets multi-cluster management method according to claim 1, wherein the receiving the backhaul information to implement management of kubernets multi-cluster includes:

adding cluster information of the slave management cluster through a graphical interface in advance;

and inputting kubeconfig of the cluster through a preset program interface so as to display corresponding return information to realize management of the Kubernets multi-cluster.

6. The kubernets multi-cluster management method according to any one of claims 1 to 5, wherein after receiving the backhaul information to implement management of kubernets multi-cluster, the method further comprises:

and storing the target information in the returned information into a local database based on the user requirement.

7. A Kubernetes multi-cluster management method is applied to a slave management cluster and comprises the following steps:

receiving a management instruction sent by a master management cluster, calling a corresponding test case for a preset agent deployed by the slave management cluster by using the master management cluster in advance to collect cluster information of the slave management cluster, and generating corresponding return information;

and sending the return information to the main management cluster so that the main management cluster can manage the Kubernetes multi-cluster.

8. A Kubernetes multi-cluster management device is applied to a main management cluster and comprises the following components:

the program deployment module is used for deploying preset agent programs for other Kubernets outside the master management cluster to obtain the slave management cluster;

the information collection module is used for sending a management instruction to the slave management cluster so that the preset agent program can call a corresponding test case to collect cluster information of the slave management cluster and generate corresponding return information;

and the information receiving module is used for receiving the returned information so as to realize management of the Kubernetes multi-cluster.

9. An electronic device, comprising:

a memory for storing a computer program;

a processor for executing the computer program to implement the steps of the kubernets multi-cluster management method according to any one of claims 1 to 7.

10. A computer-readable storage medium for storing a computer program; wherein the computer program when executed by a processor implements the steps of a kubernets multi-cluster management method as claimed in any one of claims 1 to 7.

Images