WO2021017301A1 - Procédé et appareil de gestion sur la base d'une grappe kubernetes, et support de mémoire lisible par ordinateur - Google Patents

Procédé et appareil de gestion sur la base d'une grappe kubernetes, et support de mémoire lisible par ordinateur Download PDF

Info

Publication number
WO2021017301A1
WO2021017301A1 PCT/CN2019/118007 CN2019118007W WO2021017301A1 WO 2021017301 A1 WO2021017301 A1 WO 2021017301A1 CN 2019118007 W CN2019118007 W CN 2019118007W WO 2021017301 A1 WO2021017301 A1 WO 2021017301A1
Authority
WO
WIPO (PCT)
Prior art keywords
cluster
kubernetes
business
configuration information
control
Prior art date
Application number
PCT/CN2019/118007
Other languages
English (en)
Chinese (zh)
Inventor
琚汝强
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2021017301A1 publication Critical patent/WO2021017301A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/04—Network management architectures or arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network

Definitions

  • 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.
  • 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.
  • 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.
  • 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.
  • 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
  • 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.
  • 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.
  • 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.
  • 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;
  • FIG. 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;
  • FIG. 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.
  • This application provides a management method based on a Kubernetes cluster.
  • 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.
  • 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.
  • the management method based on the Kubernetes cluster includes:
  • Step A Determine the configuration information required by the Kubernetes cluster.
  • 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
  • the control cluster is also called a service management cluster.
  • 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;
  • 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.;
  • VPC virtual private cloud
  • the configuration information of the Kubernetes application includes: Kubernetes version.
  • step A includes:
  • Step B Activate the corresponding container service according to the configuration information.
  • step B includes:
  • control cluster is used to deploy and manage each application program in the business cluster.
  • 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. .
  • 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.
  • 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.
  • 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;
  • 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.
  • the step "create a control cluster in the designated VPC" includes a monitoring step, wherein the monitoring step includes:
  • the cloud host performance index includes: the host's CPU usage rate, MEM usage rate, etc.
  • the monitoring step further includes: collecting the existence and survivability indicators of Kubernetes components and containers.
  • 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.
  • control cluster and the business cluster include a monitoring agent
  • 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 .
  • the monitoring agent is a monitoring program.
  • 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.
  • 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.
  • the alarm message can be sent to relevant personnel in the form of email, telephone, short message, etc.
  • 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.
  • 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.
  • Kubernetes service nodes can also be added or deleted later.
  • the step C4 includes:
  • the components required by the Kubernetes service node may be: flannel, docker, kube-proxy, application container, etc.
  • docker is an open source application container engine for running containers.
  • 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.
  • the service container can be scheduled to the designated node in the VPC, after the step C4, the method further includes:
  • 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.
  • the step D includes: configuring each application program with configuration items of the selected node.
  • the configuration item includes: specifying the spec.nodeSelector field in the deployment.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • SMC smart media card
  • 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. .
  • 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.
  • CPU central processing unit
  • 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.
  • a standard wired interface and a wireless interface such as a WI-FI interface
  • 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.
  • 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 "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;
  • 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 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.;
  • the configuration information of the Kubernetes application includes: Kubernetes version.
  • step A includes:
  • VPC Virtual Private Cloud
  • Step B Activate the corresponding container service according to the configuration information.
  • step B includes:
  • control cluster is used to deploy and manage each application program in the business cluster.
  • 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. .
  • 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.
  • 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.
  • 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;
  • 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.
  • the step "create a control cluster in the designated VPC" includes a monitoring step, wherein the monitoring step includes:
  • the cloud host performance index includes: the host's CPU usage rate, MEM usage rate, etc.
  • the monitoring step further includes: collecting the existence and survivability indicators of Kubernetes components and containers.
  • 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.
  • control cluster and the business cluster include a monitoring agent
  • 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 .
  • the monitoring agent is a monitoring program.
  • 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.
  • 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.
  • the alarm message can be sent to relevant personnel in the form of email, telephone, short message, etc.
  • 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.
  • Step C Create a corresponding business cluster according to the configuration information.
  • 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.
  • Kubernetes service nodes can also be added or deleted later.
  • the step C4 includes:
  • the components required by the Kubernetes service node may be: flannel, docker, kube-proxy, application container, etc.
  • docker is an open source application container engine for running containers.
  • the service container can be scheduled to the designated node in the VPC, after the step C4, the method further includes:
  • 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.
  • the step D includes: configuring each application program with configuration items of the selected node.
  • the configuration item includes: specifying the spec.nodeSelector field in the deployment.
  • 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.
  • 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.
  • FIG. 4 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.
  • 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.
  • cAdvisor 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.
  • 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.
  • the deployment module 40 is also used to configure the configuration items of the selected node for each application.
  • the configuration item includes: specifying the spec.nodeSelector field in the deployment.
  • 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.
  • 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.
  • 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
  • Step D Deploy the corresponding application container according to the configuration information.
  • step A includes:
  • the step B includes: creating a control cluster in the designated VPC.
  • the step of "creating a control cluster in the designated VPC" includes a monitoring step, wherein the monitoring step includes:
  • the monitoring step further includes: collecting the existence and survivability indicators of Kubernetes components and containers.
  • 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.
  • 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.
  • step C4 it further includes:
  • Step C5 Configure designated service labels for all nodes.
  • step D includes: configuring configuration items of the selected node for each application.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)

Abstract

La présente invention concerne un procédé et un appareil de gestion sur la base d'une grappe Kubernetes, et un support de stockage lisible par ordinateur. Le procédé consiste à : déterminer des informations de configuration requises par une grappe Kubernetes, ouvrir un service de conteneur, créer une grappe de services, et déployer un conteneur d'application, l'étape d'ouverture d'un service de conteneur consistant à : créer une grappe de commande dans un VPC spécifié, et les informations de configuration comprenant : des informations de configuration d'une ressource de base, des informations de configuration d'une taille de grappe, des informations de configuration d'un réseau de grappes, et des informations de configuration d'une application Kubernetes. Le procédé résout le problème technique de la commutation entre un déploiement hébergé en nuage et un déploiement en conteneurs. En créant uniquement une grappe de services, un service en conteneurs peut être déployé à l'intérieur de celle-ci, et un utilisateur n'a pas besoin de maîtriser des connaissances professionnelles concernant Kubernetes, ce qui permet de réduire les coûts d'apprentissage de l'utilisateur et de faciliter la gestion de service.
PCT/CN2019/118007 2019-07-30 2019-11-13 Procédé et appareil de gestion sur la base d'une grappe kubernetes, et support de mémoire lisible par ordinateur WO2021017301A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910704915.3 2019-07-30
CN201910704915.3A CN110531987A (zh) 2019-07-30 2019-07-30 基于Kubernetes集群的管理方法、装置及计算机可读存储介质

Publications (1)

Publication Number Publication Date
WO2021017301A1 true WO2021017301A1 (fr) 2021-02-04

Family

ID=68660594

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/118007 WO2021017301A1 (fr) 2019-07-30 2019-11-13 Procédé et appareil de gestion sur la base d'une grappe kubernetes, et support de mémoire lisible par ordinateur

Country Status (2)

Country Link
CN (1) CN110531987A (fr)
WO (1) WO2021017301A1 (fr)

Families Citing this family (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10812337B2 (en) 2018-06-15 2020-10-20 Vmware, Inc. Hierarchical API for a SDDC
US10942788B2 (en) 2018-06-15 2021-03-09 Vmware, Inc. Policy constraint framework for an sddc
US11086700B2 (en) 2018-08-24 2021-08-10 Vmware, Inc. Template driven approach to deploy a multi-segmented application in an SDDC
CN111327681A (zh) * 2020-01-21 2020-06-23 北京工业大学 一种基于Kubernetes的云计算数据平台构建方法
CN111367950B (zh) * 2020-02-28 2023-08-08 上海欣巴自动化科技股份有限公司 一种基于Kubernetes的分布式AGV调度系统及调度方法
CN111427625B (zh) * 2020-03-23 2023-03-24 中国—东盟信息港股份有限公司 一种基于动态路由构建Kubernetes容器云外部负载均衡器的方法
WO2021196080A1 (fr) 2020-04-01 2021-10-07 Vmware Information Technology (China) Co., Ltd. Déploiement automatique d'éléments de réseau pour éléments de calcul hétérogènes
CN111787063B (zh) * 2020-06-02 2023-05-16 深圳前海移联科技有限公司 一种业务服务的通道路由管理方法
CN113839974A (zh) * 2020-06-23 2021-12-24 海尔数字科技（上海）有限公司 容器平台计费方法及系统
CN113872997B (zh) * 2020-06-30 2022-08-26 华为技术有限公司 基于容器集群服务的容器组pod重建方法及相关设备
CN111782370B (zh) * 2020-06-30 2022-12-06 平安科技（深圳）有限公司 一种kubernetes多集群管理系统、方法、终端及存储介质
CN111859428B (zh) * 2020-07-22 2022-07-19 成都安恒信息技术有限公司 一种基于容器化的密钥存储方法及系统
US11803408B2 (en) 2020-07-29 2023-10-31 Vmware, Inc. Distributed network plugin agents for container networking
US11863352B2 (en) 2020-07-30 2024-01-02 Vmware, Inc. Hierarchical networking for nested container clusters
CN111897541B (zh) * 2020-08-03 2021-08-17 汇链通供应链科技(上海)有限公司 一种云环境下自动化部署资源的软件交互平台及方法
CN111984270A (zh) * 2020-08-20 2020-11-24 第四范式（北京）技术有限公司 应用部署方法和系统
CN112015753B (zh) * 2020-08-31 2023-10-31 北京易捷思达科技发展有限公司 适于容器化部署开源云平台的监控系统和方法
CN112187925A (zh) * 2020-09-28 2021-01-05 江苏银承网络科技股份有限公司 用于大数据平台的离线集群管理方法及装置
CN112527449B (zh) * 2020-11-19 2024-07-02 北京浪潮数据技术有限公司 一种集群节点标签创建方法、系统及电子设备和存储介质
CN112565475B (zh) * 2020-12-01 2023-07-11 成都精灵云科技有限公司 容器集群业务层添加新节点的ip地址分配方法
CN112671602B (zh) * 2020-12-14 2023-07-04 北京金山云网络技术有限公司 边缘节点的数据处理方法、装置、系统、设备和存储介质
CN112328456B (zh) * 2021-01-04 2021-12-03 北京电信易通信息技术股份有限公司 一种基于服务发现的集群资源监控系统
US11606254B2 (en) 2021-06-11 2023-03-14 Vmware, Inc. Automatic configuring of VLAN and overlay logical switches for container secondary interfaces
CN113419819B (zh) * 2021-06-25 2023-09-08 重庆紫光华山智安科技有限公司 容器管理方法、装置、设备及介质
CN113568684A (zh) * 2021-09-23 2021-10-29 中国电子科技集团公司第十五研究所 一种应用托管方法、装置、设备及大数据系统
CN113934711B (zh) * 2021-12-16 2022-03-15 天津南大通用数据技术股份有限公司 一种自动化部署gbase8s集群的方法
US11902245B2 (en) 2022-01-14 2024-02-13 VMware LLC Per-namespace IP address management method for container networks
US11848910B1 (en) 2022-11-11 2023-12-19 Vmware, Inc. Assigning stateful pods fixed IP addresses depending on unique pod identity
US11831511B1 (en) 2023-01-17 2023-11-28 Vmware, Inc. Enforcing network policies in heterogeneous systems

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109491674A (zh) * 2018-11-07 2019-03-19 李斌 一种在Kubernetes集群中自动部署服务的方法与系统
US20190095253A1 (en) * 2017-09-22 2019-03-28 Vmware, Inc. Cluster updating using temporary update-monitor pod
CN109885316A (zh) * 2019-02-18 2019-06-14 国家计算机网络与信息安全管理中心 基于kubernetes的hdfs-hbase部署方法及装置
CN109981351A (zh) * 2019-03-06 2019-07-05 浪潮通用软件有限公司 一种私有云部署方法

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105376303B (zh) * 2015-10-23 2018-11-06 深圳前海达闼云端智能科技有限公司 一种Docker实现系统及其通信方法
CN108549580B (zh) * 2018-03-30 2023-04-14 平安科技（深圳）有限公司 自动部署Kubernetes从节点的方法及终端设备
CN108809722B (zh) * 2018-06-13 2022-03-22 郑州云海信息技术有限公司 一种部署Kubernetes集群的方法、装置和存储介质
CN109150987B (zh) * 2018-07-27 2021-11-30 北京友普信息技术有限公司 基于主机层和容器层的两层式容器集群弹性扩容方法
CN109800055A (zh) * 2018-12-27 2019-05-24 北京航天智造科技发展有限公司 容器调度编排方法和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190095253A1 (en) * 2017-09-22 2019-03-28 Vmware, Inc. Cluster updating using temporary update-monitor pod
CN109491674A (zh) * 2018-11-07 2019-03-19 李斌 一种在Kubernetes集群中自动部署服务的方法与系统
CN109885316A (zh) * 2019-02-18 2019-06-14 国家计算机网络与信息安全管理中心 基于kubernetes的hdfs-hbase部署方法及装置
CN109981351A (zh) * 2019-03-06 2019-07-05 浪潮通用软件有限公司 一种私有云部署方法

Also Published As

Publication number Publication date
CN110531987A (zh) 2019-12-03

Similar Documents

Publication Publication Date Title
WO2021017301A1 (fr) Procédé et appareil de gestion sur la base d'une grappe kubernetes, et support de mémoire lisible par ordinateur
WO2021017279A1 (fr) Procédé et appareil de gestion de la sécurité de grappe fondés sur kubernetes et un domaine de réseau, et support de stockage
US11683221B1 (en) Automatic generation of template for provisioning services in a hosted computing environment
US20210314273A1 (en) Enabling multi-tenant virtual servers in a cloud system
CN104360878B (zh) 一种应用软件部署的方法及装置
WO2016117697A1 (fr) Procédé, dispositif et programme pour une gestion et une orchestration de virtualisation de fonction de réseau
WO2023142054A1 (fr) Procédé de surveillance et d'alarme de performance orienté microservice de conteneur et système d'alarme
CN112925647A (zh) 云边协同系统、集群资源的控制方法及装置
CN110908658A (zh) 一种“微服务+微应用”系统、数据处理方法及装置
CN104160376A (zh) 虚拟机的离线准备
CN110324169A (zh) 一种接口管理的方法和装置
CN103685608A (zh) 一种自动配置安全虚拟机ip地址的方法及装置
CN106293847B (zh) 一种虚拟化平台服务支撑的方法
US10908970B1 (en) Data interface for secure analytic data system integration
TW201243617A (en) Cloud computing-based service management system
CN115378944B (zh) 一种网络系统及服务网格配置方法、存储介质和电子设备
CN106330546A (zh) 一种在私有云环境中应用集群部署的系统和方法
CN108009010B (zh) 瘦客户端的管理装置、系统、方法、电子设备、存储介质
CN113486095A (zh) 一种民航空管跨网安全数据交换管理平台
CN110417741A (zh) 一种过滤安全组的方法和装置
US11336502B2 (en) Deriving network device and host connection
EP4024761A1 (fr) Procédé et appareil de communication pour multiples domaines de gestion
CN112068953A (zh) 一种云资源精细化管理溯源系统及方法
US11561995B2 (en) Multitenant database instance view aggregation
CN114756301A (zh) 日志处理方法、装置和系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19939489

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19939489

Country of ref document: EP

Kind code of ref document: A1