WO2021017301A1

WO2021017301A1 - Management method and apparatus based on kubernetes cluster, and computer-readable storage medium

Info

Publication number: WO2021017301A1
Application number: PCT/CN2019/118007
Authority: WO
Inventors: 琚汝强
Original assignee: 平安科技（深圳）有限公司
Priority date: 2019-07-30
Filing date: 2019-11-13
Publication date: 2021-02-04
Also published as: CN110531987A

Abstract

A management method and apparatus based on a Kubernetes cluster, and a computer-readable storage medium. The method comprises: determining configuration information required by a Kubernetes cluster, opening a container service, creating a service cluster, and deploying an application container, wherein the step "opening a container service" comprises: creating a control cluster in a specified VPC, and the configuration information comprises: configuration information of a basic resource, configuration information of a cluster size, configuration information of a cluster network, and configuration information of a Kubernetes application. The method solves the technical problem of how to switch from cloud host deployment to containerized deployment. By only creating a service cluster, a containerized service can be deployed therein, and a user does not need to master professional knowledge of Kubernetes, thereby reducing the learning costs of the user and facilitating service management.

Description

Management method, device and computer readable storage medium based on Kubernetes cluster

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office on July 30, 2019, the application number is 201910704915.3, and the invention title is "Kubernetes cluster-based management methods, devices and computer-readable storage media". The entire content Incorporated in this application by reference.

Technical field

This application relates to the field of cloud deployment technology, and in particular to a management method, device and computer-readable storage medium based on a Kubernetes cluster.

Background technique

Kubernetes is an open source container orchestration engine, and it is also a containerized application used to manage multiple hosts in the cloud platform. Kubernetes supports automated deployment, large-scale scalability, and application containerized management. When deploying an application in a production environment, multiple instances of the application are usually deployed to load balance application requests. In Kubernetes, we can create multiple containers, each container runs an application instance, and then through the built-in load balancing strategy to achieve the management, discovery, and access to this group of application instances, and these details do not require operation and maintenance Personnel to carry out complex manual configuration and processing.

At present, most public cloud vendors provide container services, and all provide enterprise-level container application management services based on Kubernetes, and support one-click deployment of Kubernetes clusters. Container Service provides a general-purpose Kubernetes-based container application management platform, but the current platform only provides a general environment for managing containers, and exposes too much Kubernetes expertise to users, which makes the learning cost of users higher. It is not convenient for users to switch from the original cloud host deployment to containerized deployment.

Summary of the invention

This application provides a management method, device and computer-readable storage medium based on a Kubernetes cluster, the main purpose of which is to solve the technical problem of how to switch from cloud host deployment to containerized deployment.

In order to achieve the above objective, this application provides a management method based on a Kubernetes cluster. The method includes the following steps: determining configuration information required by the Kubernetes cluster; wherein the Kubernetes cluster includes a business cluster and a control cluster, and the configuration information includes Node configuration items; enable corresponding container services according to the configuration information; create corresponding business clusters according to the configuration information; deploy corresponding application containers according to the configuration information; wherein, the container services are enabled according to the configuration information The steps include: creating a control cluster in a designated virtual private cloud (Virtual Private Cloud, VPC); wherein, the control cluster is used to deploy and manage each application program in the business cluster; The step of information deployment of the corresponding application container includes: configuring each application in the business cluster with the configuration items of the selected node; the step of creating the corresponding business cluster according to the configuration information includes: specifying the nodes included in the business cluster Data and business name; call the cloud host creation interface; create the cloud host; add all the cloud hosts to the business cluster as the nodes of the business container.

In order to achieve the above objective, this application also provides a management device based on a Kubernetes cluster. The device includes a memory and a processor. The memory stores a management program based on the Kubernetes cluster that can run on the processor. When the management program based on the Kubernetes cluster is executed by the processor, the steps of the management method based on the Kubernetes cluster as described above are implemented.

In addition, in order to achieve the above-mentioned purpose, this application also provides a computer-readable storage medium on which a management program based on a Kubernetes cluster is stored, and the management program based on a Kubernetes cluster can be used by one or more The processor executes to implement the steps of the management method based on the Kubernetes cluster as described above.

The Kubernetes cluster-based management method, device and computer-readable storage medium proposed in this application can create a control cluster, create a business cluster, and deploy in a designated VPC by enabling the container service after configuring the configuration information required by the cluster. Application container, without the need to create control clusters, create business clusters, deploy application containers and other deployment operations in the cloud host, thus realizing the switch from cloud host deployment to containerized deployment, which is convenient for business management.

Description of the drawings

FIG. 1 is a schematic flow diagram of a management method based on a Kubernetes cluster provided by an embodiment of this application;

FIG. 2 is a schematic flowchart of step C in FIG. 1;

3 is a schematic diagram of the internal structure of a management device based on a Kubernetes cluster provided by an embodiment of the application;

4 is a schematic diagram of modules of a management program based on a Kubernetes cluster in a management device based on a Kubernetes cluster provided by an embodiment of the application.

The realization, functional characteristics, and advantages of the purpose of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings.

Detailed ways

It should be understood that the specific embodiments described here are only used to explain the application, and are not used to limit the application.

This application provides a management method based on a Kubernetes cluster. In this embodiment, the banking system includes a configuration management system and a banking business subsystem, and the banking system has a project path corresponding to each project. Referring to FIG. 1, it is a schematic flowchart of a management method based on a Kubernetes cluster provided by an embodiment of this application. The method can be executed by a device, and the device can be implemented by software and/or hardware.

In this embodiment, the management method based on the Kubernetes cluster includes:

Step A: Determine the configuration information required by the Kubernetes cluster. Wherein, the Kubernetes cluster includes a business cluster and a control cluster. The service cluster is used to provide an operating environment for container applications, the control cluster is used to deploy and manage each application or service in the service cluster, and the control cluster is also called a service management cluster.

Furthermore, the "determining the configuration information required by the Kubernetes cluster" in step A may include, but is not limited to: configuration information of basic resources, configuration information of the cluster size, configuration information of the cluster network, and configuration of nodes Configuration information of items and Kubernetes applications;

Wherein, the configuration information of the basic resources includes: whether the cluster is highly available, availability zone, cloud host billing method, cluster area, cloud host mirroring, key pair, node specifications, and external network;

The configuration information of the cluster scale refers to the configuration information of the Kubernetes cluster scale, which includes: the number of master nodes and the number of slave nodes;

The configuration information of the cluster network is the configuration information of the Kubernetes cluster network, which includes: business network type, network segment address, subnet mask, gateway, virtual private cloud (VPC) that requires container service, network Plugins, etc.;

The configuration information of the Kubernetes application includes: Kubernetes version.

Further, the step A includes:

Determine the VPC that needs to activate the container service;

Determine whether the Kubernetes cluster is highly available; and

Determine the Kubernetes version.

Step B: Activate the corresponding container service according to the configuration information.

Further, the step B includes:

Create a control cluster in the specified VPC. Wherein, the control cluster is used to deploy and manage each application program in the business cluster.

Furthermore, the control cluster includes at least one group of kubernetes control plane components, and each group of kubernetes control plane components may include, but are not limited to, kube-apiserver, kube-controller-manager, kube-scheduler, Etcd, etc. .

The components of the kubernetes control plane are explained as follows:

kube-apiserver: API server, used to expose Kubernetes API; any resource request/call operation is performed through the interface provided by kube-apiserver;

kube-controller-manager: controller manager;

kube-scheduler: Container scheduler, used to monitor newly created Pods that are not assigned to nodes, and select a node for Pod;

Etcd: Key-value database, used to store cluster data.

Furthermore, the control cluster further includes at least one set of kubernetes service components, and each set of kubernetes service components may include, but is not limited to, components such as kube-proxy, kube-dns, tiller, addons, and flannel.

Among them, the kubernetes service component is explained as follows:

kube-proxy: Forward proxy, which implements Kubernetes service abstraction by maintaining network rules on the host and performing connection forwarding;

kube-dns: refers to the cluster DNS (Domain Name Server), which is a domain name server, used to provide DNS records for Kubernetes services;

tiller: is the server-side component of Helm, and Helm is the package management tool of Kubernetes;

addons: refers to addons, which are used to implement cluster pod and services functions;

flannel: It is a network plug-in in the kubernetes cluster.

Preferably, the step "create a control cluster in the designated VPC" includes a monitoring step, wherein the monitoring step includes:

Collect cloud host performance indicators; and

Display the interface graphics based on the collected cloud host performance indicators.

Wherein, in an embodiment, the cloud host performance index includes: the host's CPU usage rate, MEM usage rate, etc.

Further, the monitoring step further includes: collecting the existence and survivability indicators of Kubernetes components and containers.

Further, the monitoring step includes the monitoring of the control cluster node and the monitoring of the service cluster; specifically, the monitoring step includes: monitoring the survivability of all components and containers on the control cluster node; in the monitoring step It also includes: monitoring the application containers on the business cluster.

Specifically, in this embodiment, the control cluster and the business cluster include a monitoring agent, and the cloud host performance index is collected by the monitoring agent running on the control cluster and the business cluster, and the collected cloud host performance index is displayed on the interface graphic . Among them, the monitoring agent is a monitoring program.

Further, the step of "creating a control cluster in the designated VPC" further includes: a log step; specifically, the log step includes: generating a log when the container service module creates the control cluster;

The logs include cloud host logs, management cluster component logs, and pod logs.

Preferably, in order to facilitate the user to view the logs of his concern without logging in to the cloud host, the log step further includes: converging all logs to the log cloud through the monitoring agent.

The step of "creating a control cluster in a designated VPC" also includes an alerting step: when a component of the control cluster is abnormal, or a component or a pod in the business cluster is abnormal, an alert message is sent to relevant personnel. Preferably, the alarm message can be sent to relevant personnel in the form of email, telephone, short message, etc.

Further, the alerting step includes: when the viability of all components and containers on the control cluster node is abnormal, sending an alert message to relevant personnel. The alerting step further includes: sending an alert message to relevant personnel when the alert of the application container on the business cluster is abnormal, for example, sending an alert message to the relevant personnel when the pod is abnormal.

Step C: Create a corresponding business cluster according to the configuration information.

Further, referring to Figure 2, the step C includes:

Step C1: Specify the number of nodes and business names included in the business cluster;

Step C2: Call the cloud host to create an interface;

Step C3: Create a cloud host;

Step C4: Add all cloud hosts to the business cluster as nodes running on the business container.

Wherein, in the process of performing step C1, Kubernetes service nodes can also be added or deleted later.

Specifically, the step C4 includes:

After creating the cloud host, add the cloud host to the business cluster;

Install the components required by the Kubernetes business node on the cloud host;

Store cluster nodes, network and other information in Etcd.

Preferably, the components required by the Kubernetes service node may be: flannel, docker, kube-proxy, application container, etc. Among them, docker is an open source application container engine for running containers.

Preferably, in this embodiment, an Etcd storage system is used to store the information of each node. The Etcd can quickly and effectively add or delete the current information of each Kubernetes node.

Further, in order to facilitate the creation of the core application, the service container can be scheduled to the designated node in the VPC, after the step C4, the method further includes:

Step C5: Configure designated service labels for all nodes. For example, app=core.

Further, in order to isolate the application program, the step C includes: creating a namespace resource object. Among them, one or more applications are deployed to a business cluster.

Step D: Deploy the corresponding application container according to the configuration information.

Preferably, in order to ensure that the application container can be successfully scheduled to the designated node after the application container is successfully created, the step D includes: configuring each application program with configuration items of the selected node. Preferably, in this embodiment, the configuration item includes: specifying the spec.nodeSelector field in the deployment.

Among them, deployment is a resource object of Kubernetes, which is used to better solve the problem of Pod scheduling; pod represents an application; deployment is used to manage Kubernetes stateless applications; spec.nodeSelector allows pods to be scheduled to configure specific labels On the host.

Preferably, one or more applications have their own dedicated operating environment, and the one or more applications are isolated from other applications; the resources of the application will not be preempted by other applications, and abnormal problems between the two applications , It is only possible because of abnormal interface calls, not because of resource preemption; through this isolation method, the efficiency of problem location can be improved, which is conducive to collaboration between teams.

The Kubernetes cluster-based management method proposed in this application solves the technical problem of how to switch from cloud host deployment to containerized deployment, does not require users to master Kubernetes professional knowledge, and reduces user learning costs; this application manages business through business clusters, Let many traditional users quickly use the Kubernetes-based container service to manage container applications, which facilitates rapid deployment from cloud host deployment to containerized deployment; this application also creates business clusters based on business modules to facilitate management of business modules; users are using In the process, you only need to create your own business cluster, and you can deploy containerized services in it.

The application also provides a management device based on a Kubernetes cluster. Referring to FIG. 3, it is a schematic diagram of the internal structure of a Kubernetes cluster-based management device provided by an embodiment of this application.

In this embodiment, the management device based on the Kubernetes cluster may be a PC (Personal Computer, personal computer), or a terminal device such as a smart phone, a tablet computer, or a portable computer. The Kubernetes cluster-based management device includes at least a memory 11, a processor 12, a network interface 13, and a communication bus 14.

Wherein, the memory 11 includes at least one type of computer-readable storage medium, and the computer-readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), magnetic memory, and magnetic disk. , CD, etc. In some embodiments, the memory 11 may be an internal storage unit of a management device based on a Kubernetes cluster, such as a hard disk of the management device based on a Kubernetes cluster. In other embodiments, the memory 11 may also be an external storage device of a management device based on a Kubernetes cluster, such as a plug-in hard disk or a smart media card (SMC) equipped on a management device based on a Kubernetes cluster. Secure Digital (SD) card, Flash Card, etc. Further, the memory 11 may also include both an internal storage unit of a management device based on a Kubernetes cluster and an external storage device. The memory 11 can be used not only to store application software and various data installed in the management device based on the Kubernetes cluster, such as the code of the management program based on the Kubernetes cluster, etc., but also to temporarily store the data that has been output or will be output. .

In some embodiments, the processor 12 may be a central processing unit (CPU), controller, microcontroller, microprocessor, or other data processing chip, which is used to run data stored in the memory 11 Program code or processing data, such as executing management programs based on Kubernetes clusters.

The network interface 13 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface), and is usually used to establish a communication connection between the Kubernetes cluster-based management device and other electronic devices.

The communication bus 14 is used to realize the connection and communication between these components.

Figure 3 only shows a Kubernetes cluster-based management device with components 11 to 14 and a Kubernetes cluster-based management program. Those skilled in the art can understand that the structure shown in Figure 3 does not constitute management of a Kubernetes-based cluster The definition of the device may include fewer or more components than shown, or a combination of certain components, or different component arrangements.

In the embodiment of the Kubernetes cluster-based management device shown in FIG. 3, the storage 11 stores a management program based on the Kubernetes cluster; when the processor 12 executes the management program based on the Kubernetes cluster stored in the storage 11 Implement the following steps:

Step A: Determine the configuration information required by the Kubernetes cluster.

The configuration information of the cluster size includes: the number of master nodes and the number of slave nodes;

The configuration information of the cluster network includes: business network type, network segment address, subnet mask, gateway, VPC that needs to activate container service, network plug-in, etc.;

Further, the step A includes:

Determine the VPC (Virtual Private Cloud) that needs to activate the container service;

Determine whether the Kubernetes cluster is highly available; and

Determine the Kubernetes version.

Further, the step B includes:

The components of the kubernetes control plane are explained as follows:

kube-controller-manager: controller manager;

Etcd: Key-value database, used to store cluster data.

Furthermore, the control cluster also includes at least one set of kubernetes service components, and each set of kubernetes service components may include, but is not limited to, components such as kube-proxy, kube-dns, tiller, addons, and flannel.

Among them, the kubernetes service component is explained as follows:

flannel: It is a network plug-in in the kubernetes cluster.

Collect cloud host performance indicators; and

Further, the alarm step includes: controlling the alarm of the cluster node and the alarm of the business cluster; specifically, the alarm step includes: when the viability of all components and containers on the control cluster node is abnormal, sending an alarm message Relevant personnel.

The alerting step further includes: sending an alert message to relevant personnel when the application container on the business cluster is abnormal, for example, sending an alert message to the relevant personnel when the pod is abnormal.

Further, the step C includes:

Step C2: Call the cloud host to create an interface;

Step C3: Create a cloud host;

Specifically, the step C4 includes:

After creating the cloud host, add the cloud host to the business cluster;

Store cluster nodes, network and other information in Etcd.

For example, referring to FIG. 4, which is a schematic diagram of program modules of a Kubernetes cluster-based management program in an embodiment of a Kubernetes cluster-based management device of this application. In this embodiment, the management program based on the Kubernetes cluster can be divided into a configuration module 10, a container service module 20, a creation module 30, a deployment module 40, a monitoring module 50, an alarm module 60, and a log module 70, exemplarily :

The configuration module 10 is used to determine configuration information required by the Kubernetes cluster. The configuration module 10 is also used to determine the VPC that needs to activate the container service, determine whether the Kubernetes cluster is highly available, and determine the Kubernetes version.

The container service module 20 is configured to activate corresponding container services according to the configuration information.

The creation module 30 is used to create a corresponding business cluster according to the configuration information.

The deployment module 40 is configured to deploy a corresponding application container according to the configuration information.

The monitoring module 50 is used to collect cloud host performance indicators, and is used to display interface graphics according to the collected cloud host performance indicators.

The monitoring module 50 adopts cAdvisor, which is a daemon process for collecting, aggregating, and outputting container operation indicators. Various performance data of Docker in the Kubernetes cluster can be obtained through cAdvisor.

The alarm module 60 is configured to send an alarm message to relevant personnel when an abnormality occurs in a component of the control cluster, or when an abnormality occurs in a component or a pod in the business cluster.

The log module 70 is configured to generate a log when the container service module creates a control cluster.

The creation module 30 is also used to specify the number of nodes and business names contained in the business cluster; it is also used to call the cloud host creation interface after specifying the number of nodes and business names contained in the business cluster; and to call the cloud host creation Create a cloud host after the interface; it is used to add all the cloud hosts to the business cluster after the cloud host is created, as a node for the business container to run.

Further, in order to facilitate the creation of the core application, the service container can be scheduled to the designated node in the VPC, and the creation module 30 is also used to configure designated service labels for all nodes.

Preferably, in order to ensure that the application container can be successfully scheduled to the designated node after the application container is successfully created, the deployment module 40 is also used to configure the configuration items of the selected node for each application. Preferably, in this embodiment, the configuration item includes: specifying the spec.nodeSelector field in the deployment.

The above-mentioned configuration module 10, container service module 20, creation module 30, deployment module 40, monitoring module 50, alarm module 60, and log module 70 implement functions or operation steps that are substantially the same as those in the foregoing embodiment when executed. This will not be repeated here.

In addition, an embodiment of the present application also proposes a computer-readable storage medium, which stores a management program based on a Kubernetes cluster, and the management program based on a Kubernetes cluster can be executed by one or more processors To achieve the following operations:

Step A: Determine the configuration information required by the Kubernetes cluster;

Step B: Activate the corresponding container service according to the configuration information;

Step C: Create a corresponding business cluster according to the configuration information;

Wherein, the step A includes:

Determine the VPC that needs to activate the container service;

Determine whether the Kubernetes cluster is highly available; and

Determine the Kubernetes version.

The step B includes: creating a control cluster in the designated VPC.

Preferably, the step of "creating a control cluster in the designated VPC" includes a monitoring step, wherein the monitoring step includes:

Collect cloud host performance indicators; and

Further, the step of "creating a control cluster in the designated VPC" further includes a log step, wherein the log step includes: generating a log when the container service module creates the control cluster;

The step of "creating a control cluster in a designated VPC" also includes an alerting step: when a component of the control cluster is abnormal, or a component or a pod in the business cluster is abnormal, an alert message is sent to relevant personnel.

Preferably, the step C includes:

Step C2: Call the cloud host to create an interface;

Step C3: Create a cloud host; and

Further, after the step C4, it further includes:

Step C5: Configure designated service labels for all nodes.

Further, the step D includes: configuring configuration items of the selected node for each application.

The specific implementation of the computer-readable storage medium of this application is basically the same as the above-mentioned embodiments of the Kubernetes cluster-based management device and method, and will not be repeated here.

The Kubernetes cluster-based management method, device, and computer-readable storage medium proposed in this application enable the container service after configuring the configuration information required by the cluster, create a business cluster, deploy application containers, and create a control cluster in a designated VPC ; This application solves the technical problem of how to switch from cloud host deployment to containerized deployment, does not require users to master Kubernetes professional knowledge, and reduces user learning costs; this application manages services through business clusters, allowing many traditional users to quickly use The container service based on Kubernetes is used to manage container applications to facilitate rapid deployment from cloud host deployment to containerized deployment; this application also creates business clusters based on business modules to facilitate management of business modules; users only need to create their own during use Business clusters, and containerized services can be deployed in them.

It should be noted that the serial numbers of the above embodiments of the present application are only for description, and do not represent the advantages and disadvantages of the embodiments. And the term "including" or any other variants thereof in this article is intended to cover non-exclusive inclusion, so that a process, device, article or method including a series of elements not only includes those elements, but also includes those that are not explicitly listed Other elements, or also include elements inherent to this process, device, article, or method. If there are no more restrictions, the element defined by the sentence "including one..." does not exclude the existence of other identical elements in the process, device, article, or method that includes the element.

Through the description of the above embodiments, those skilled in the art can clearly understand that the method of the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is better.的实施方式。 Based on this understanding, the technical solution of this application essentially or the part that contributes to the existing technology can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM/RAM) as described above. , Magnetic disk, optical disk), including several instructions to make a terminal device (which can be a mobile phone, a computer, a server, or a network device, etc.) execute the method described in each embodiment of the present application.

The above are only preferred embodiments of this application, and do not limit the scope of this application. Any equivalent structure or equivalent process transformation made using the content of the description and drawings of this application, or directly or indirectly used in other related technical fields , The same reason is included in the scope of patent protection of this application.

Claims

A management method based on Kubernetes cluster, characterized in that, the management method based on Kubernetes cluster includes the following steps:

Determining configuration information required by a Kubernetes cluster; wherein the Kubernetes cluster includes a business cluster and a control cluster, and the configuration information includes configuration items of nodes;

Activate the corresponding container service according to the configuration information;

Create a corresponding business cluster according to the configuration information;

Deploy a corresponding application container according to the configuration information;

Wherein, the step of opening the corresponding container service according to the configuration information includes: creating a control cluster in a designated virtual private cloud VPC; wherein, the control cluster is used to deploy and manage each application in the business cluster program;

The step of deploying the corresponding application container according to the configuration information includes: configuring each application in the business cluster with configuration items of the selected node;

The step of creating a corresponding business cluster according to the configuration information includes:

Specify the number of nodes and business names included in the business cluster;

Call the cloud host to create an interface;

Create a cloud host;

Add all cloud hosts to the business cluster as nodes running on business containers.
The Kubernetes cluster-based management method of claim 1, wherein the control cluster includes at least one group of kubernetes control plane components, and each group of kubernetes control plane components includes: kube-apiserver, kube-controller-manager , Kube-scheduler, Etcd.
The Kubernetes cluster-based management method according to claim 1 or 2, wherein the step of determining the configuration information required by the Kubernetes cluster comprises:

Determine the virtual private cloud VPC that needs to activate the container service;

Determine whether the Kubernetes cluster is highly available; and

Determine the Kubernetes version.
The Kubernetes cluster-based management method according to claim 1 or 2, wherein the step of creating a control cluster in a designated VPC includes a monitoring step, and the monitoring step includes:

Collect cloud host performance indicators; and

Display the interface graphics based on the collected cloud host performance indicators.
The Kubernetes cluster-based management method according to claim 4, wherein the monitoring step further comprises: collecting the existence and survivability indicators of Kubernetes components and containers.
The Kubernetes cluster-based management method according to claim 1 or 2, wherein the step of creating a control cluster in a designated VPC includes: a log step, and the log step includes: generating a log when the control cluster is created .
The Kubernetes cluster-based management method according to claim 1 or 2, wherein the step of creating a control cluster in a designated VPC includes an alerting step, wherein the alerting step includes: when a component of the control cluster appears When there is an exception, or when a component or pod in the business cluster is abnormal, send an alert message to the relevant personnel

The alerting step further includes: when the viability of all components and containers on the control cluster node is abnormal and/or

When the application container on the business cluster is abnormal, an alert message is sent to the relevant personnel. .
The Kubernetes cluster-based management method according to claim 1, wherein after the step of adding all cloud hosts to the business cluster as a node running as a business container, the corresponding configuration information is created according to the configuration information. The steps of business clustering also include: configuring designated business labels for all nodes.
A management device based on a Kubernetes cluster, characterized in that the device includes a memory and a processor, the memory stores a Kubernetes cluster-based management program that can run on the processor, and the Kubernetes cluster-based management program When executed by the processor, the following steps are implemented:

Determining configuration information required by a Kubernetes cluster; wherein the Kubernetes cluster includes a business cluster and a control cluster, and the configuration information includes configuration items of nodes;

Activate the corresponding container service according to the configuration information;

Create a corresponding business cluster according to the configuration information;

Deploy a corresponding application container according to the configuration information;

Wherein, the step of opening the corresponding container service according to the configuration information includes: creating a control cluster in a designated virtual private cloud VPC; wherein, the control cluster is used to deploy and manage each application in the business cluster program;

The step of deploying the corresponding application container according to the configuration information includes: configuring each application in the business cluster with configuration items of the selected node;

The step of creating a corresponding business cluster according to the configuration information includes:

Specify the number of nodes and business names included in the business cluster;

Call the cloud host to create an interface;

Create a cloud host;

Add all cloud hosts to the business cluster as nodes running on business containers.
The Kubernetes cluster-based management device according to claim 9, wherein the control cluster includes at least one group of kubernetes control plane components, and each group of kubernetes control plane components includes: kube-apiserver, kube-controller-manager , Kube-scheduler, Etcd.
The Kubernetes cluster-based management device according to claim 9 or 10, wherein the step of determining the configuration information required by the Kubernetes cluster comprises:

Determine the virtual private cloud VPC that needs to activate the container service;

Determine whether the Kubernetes cluster is highly available; and

Determine the Kubernetes version.
The Kubernetes cluster-based management device according to claim 9 or 10, wherein the step of creating a control cluster in a designated VPC includes a monitoring step, and the monitoring step includes:

Collect cloud host performance indicators; and

Display the interface graphics based on the collected cloud host performance indicators.
The Kubernetes cluster-based management device according to claim 12, wherein the monitoring step further comprises: collecting the existence and survivability indicators of Kubernetes components and containers.
The Kubernetes cluster-based management device according to claim 9 or 10, wherein the step of creating a control cluster in a designated VPC comprises: a logging step, and the logging step comprises: generating a log when the control cluster is created .
The Kubernetes cluster-based management device according to claim 9 or 10, wherein the step of creating a control cluster in a designated VPC includes an alerting step, wherein the alerting step includes: when a component of the control cluster appears When there is an exception, or when a component or pod in the business cluster is abnormal, send an alert message to the relevant personnel

The alerting step also includes: when the viability of all components and containers on the control cluster node is abnormal and/or

When the application container on the business cluster is abnormal, an alert message is sent to the relevant personnel. .
The Kubernetes cluster-based management device according to claim 9, characterized in that, after the step of adding all cloud hosts to the business cluster as a node running as a business container, the corresponding configuration information is created according to the configuration information. The steps of business clustering also include: configuring designated business labels for all nodes.
A computer-readable storage medium, characterized in that a Kubernetes cluster-based management program is stored on the computer-readable storage medium, and the Kubernetes cluster-based management program can be executed by one or more processors to achieve the following step:

Determining configuration information required by a Kubernetes cluster; wherein the Kubernetes cluster includes a business cluster and a control cluster, and the configuration information includes configuration items of nodes;

Activate the corresponding container service according to the configuration information;

Create a corresponding business cluster according to the configuration information;

Deploy a corresponding application container according to the configuration information;

Wherein, the step of opening the corresponding container service according to the configuration information includes: creating a control cluster in a designated virtual private cloud VPC; wherein, the control cluster is used to deploy and manage each application in the business cluster program;

The step of deploying the corresponding application container according to the configuration information includes: configuring each application in the business cluster with configuration items of the selected node;

The step of creating a corresponding business cluster according to the configuration information includes:

Specify the number of nodes and business names included in the business cluster;

Call the cloud host to create an interface;

Create a cloud host;

Add all cloud hosts to the business cluster and serve as nodes running on business containers.
The computer-readable storage medium of claim 17, wherein the control cluster includes at least one group of kubernetes control plane components, and each group of kubernetes control plane components includes: kube-apiserver, kube-controller-manager, kube-scheduler, Etcd.
The management device based on a Kubernetes cluster according to claim 17 or 18, wherein the step of determining the configuration information required by the Kubernetes cluster comprises:

Determine the virtual private cloud VPC that needs to activate the container service;

Determine whether the Kubernetes cluster is highly available; and

Determine the Kubernetes version.
The computer-readable storage medium according to claim 17 or 18, wherein the step of creating a control cluster in a designated VPC includes a monitoring step, and the monitoring step includes:

Collect cloud host performance indicators; and

Display the interface graphics based on the collected cloud host performance indicators.