技术领域technical field
本发明涉及云部署技术领域，尤其涉及一种基于Kubernetes集群的管理方法、装置及计算机可读存储介质。The present invention relates to the technical field of cloud deployment, in particular to a Kubernetes cluster-based management method, device and computer-readable storage medium.
背景技术Background technique
Kubernetes是开源的一个容器编排引擎，也是一个用于管理云平台中多个主机上的容器化的应用。Kubernetes支持自动化部署、大规模可伸缩、应用容器化管理。在生产环境中部署一个应用程序时，通常要部署该应用的多个实例以便对应用请求进行负载均衡。在Kubernetes中，我们可以创建多个容器，每个容器里面运行一个应用实例，然后通过内置的负载均衡策略，实现对这一组应用实例的管理、发现、访问，而这些细节都不需要运维人员去进行复杂的手工配置和处理。Kubernetes is an open source container orchestration engine and an application for managing containerization on multiple hosts in a cloud platform. Kubernetes supports automated deployment, large-scale scalability, and application container management. When an application is deployed in a production environment, multiple instances of the application are usually deployed to load balance application requests. In Kubernetes, we can create multiple containers, run an application instance in each container, and then use the built-in load balancing strategy to realize the management, discovery, and access of this group of application instances, and these details do not require operation and maintenance. personnel to perform complex manual configuration and processing.
目前大部分公有云厂商都有提供容器服务，且都提供了基于Kubernetes的企业级容器应用管理服务，支持一键部署Kubernetes集群。容器服务提供了一个通用的基于Kubernetes的容器应用管理平台，但目前这样的平台，只提供了一个管理容器的通用环境，并且将太多Kubernetes专业知识暴露给用户，使得用户的学习成本较高，不方便用户从原来的云主机部署，切换到容器化部署。At present, most public cloud vendors provide container services, and they 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, resulting in high learning costs for users. It is inconvenient for users to switch from the original cloud host deployment to containerized deployment.
发明内容Contents of the invention
本发明提供一种基于Kubernetes集群的管理方法、装置及计算机可读存储介质，其主要目的旨在解决如何从云主机部署切换到容器化部署的技术问题。The present invention provides a Kubernetes cluster-based management method, device and computer-readable storage medium, the main purpose of which is to solve the technical problem of how to switch from cloud host deployment to containerized deployment.
为实现上述目的，本发明提供一种基于Kubernetes集群的管理方法，该方法包括如下步骤：In order to achieve the above object, the present invention provides a management method based on Kubernetes cluster, the method may further comprise the steps:
确定Kubernetes集群所需的配置信息；其中，所述Kubernetes集群包括业务集群和控制集群，所述配置信息包括节点的配置项；Determine the configuration information required by the 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;
根据所述配置信息部署相应的应用容器；Deploying corresponding application containers according to the configuration information;
其中，所述根据所述配置信息开通容器服务的步骤包括：在指定的虚拟私有云(Virtual Private Cloud，VPC)中创建控制集群；其中，所述控制集群用于部署和管理所述业务集群内的每个应用程序；Wherein, the step of activating the container service according to the configuration information includes: creating a control cluster in a designated virtual private cloud (Virtual Private Cloud, VPC); wherein, the control cluster is used to deploy and manage the for each application;
所述根据所述配置信息部署相应的应用容器的步骤包括：给业务集群内的每个应用程序配置好选择节点的配置项；The step of deploying the corresponding application container according to the configuration information includes: configuring the configuration item of the selected node for each application program in the business cluster;
所述根据所述配置信息创建相应的业务集群的步骤包括：The step of creating a corresponding business cluster according to the configuration information includes:
指定业务集群所包含的节点数和业务名称；Specify the number of nodes and business names contained in the business cluster;
调用云主机创建接口；Call the cloud host to create the interface;
创建云主机；Create a cloud host;
将所有云主机添加到业务集群中，作为业务容器运行的节点。Add all cloud hosts to the business cluster as nodes running business containers.
可选地，所述控制集群包括至少一组kubernetes控制面的组件，每组kubernetes控制面的组件包括：kube-apiserver、kube-controller-manager、kube-scheduler、Etcd。Optionally, the control cluster includes at least one set of kubernetes control plane components, each set of kubernetes control plane components includes: kube-apiserver, kube-controller-manager, kube-scheduler, Etcd.
可选地，所述确定Kubernetes集群所需的配置信息的步骤包括：Optionally, the step of determining the required configuration information of the Kubernetes cluster includes:
确定需要开通容器服务的VPC(Virtual Private Cloud，虚拟私有云)；Determine the VPC (Virtual Private Cloud, virtual private cloud) that needs to open the container service;
确定Kubernetes集群是否为高可用；及determine whether the Kubernetes cluster is highly available; and
确定Kubernetes版本。Determine the Kubernetes version.
可选地，所述在指定的VPC中创建控制集群的步骤包括监控步骤，所述监控步骤包括：Optionally, the step of creating a control cluster in the specified VPC includes a monitoring step, and the monitoring step includes:
采集云主机性能指标；及Collect cloud host performance indicators; and
根据采集到的云主机性能指标做界面图形展示。Graphical interface display based on the collected cloud host performance indicators.
可选地，所述监控步骤还包括：采集Kubernetes组件和容器的存在性、存活性指标。Optionally, the monitoring step further includes: collecting existence and survivability indicators of Kubernetes components and containers.
可选地，所述在指定的VPC中创建控制集群的步骤包括：日志步骤，所述日志步骤包括：当创建控制集群时生成日志。Optionally, the step of creating a control cluster in the specified VPC includes: a log step, and the log step includes: generating a log when the control cluster is created.
可选地，所述在指定的VPC中创建控制集群的步骤还包括警报步骤，其中，所述警报步骤包括：当控制集群的组件出现异常时，或者业务集群中的组件或者pod出现异常时，发送警报消息给相关人员；Optionally, the step of creating a control cluster in the specified VPC further includes an alarm step, wherein the alarm step includes: when a component of the control cluster is abnormal, or a component or pod in the business cluster is abnormal, Send alert messages to relevant personnel;
所述警报步骤还包括：当控制集群节点上的所有组件和容器的存活性出现异常和/或The alerting step also includes: when the survivability 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 alarm message is sent to relevant personnel.
可选地，在所述将所有云主机添加到业务集群中作为业务容器运行的节点的步骤之后，所述根据所述配置信息创建相应的业务集群的步骤还包括：给所有节点配置指定的业务标签。Optionally, after the step of adding all cloud hosts to the service cluster as nodes running as service containers, the step of creating a corresponding service cluster according to the configuration information further includes: configuring all nodes with specified service Label.
为实现上述目的，本发明还提供一种基于Kubernetes集群的管理装置，所述装置包括存储器和处理器，所述存储器存储有可在所述处理器上运行的基于Kubernetes集群的管理程序，所述基于Kubernetes集群的管理程序被所述处理器执行时实现如上所述基于Kubernetes集群的管理方法的步骤。To achieve the above object, the present invention 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 a Kubernetes cluster that can run on the processor, and the When the management program based on the Kubernetes cluster is executed by the processor, the above-mentioned steps of the management method based on the Kubernetes cluster are implemented.
此外，为实现上述目的，本发明还提供一种计算机可读存储介质，所述计算机可读存储介质上存储有基于Kubernetes集群的管理程序，所述基于Kubernetes集群的管理程序可被一个或者多个处理器执行，以实现如上所述基于Kubernetes集群的管理方法的步骤。In addition, in order to achieve the above object, the present invention 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 controlled by one or more The processor executes to realize the steps of the management method based on the Kubernetes cluster as described above.
本发明提出的基于Kubernetes集群的管理方法、装置及计算机可读存储介质，通过在配置集群所需的配置信息后开通容器服务，从而可以在指定的VPC中创建控制集群、创建业务集群、并部署应用容器，而不需要在云主机中进行创建控制集群、创建业务集群、部署应用容器等部署操作，从而实现了从云主机部署切换到容器化部署，方便业务管理。The management method, device and computer-readable storage medium based on the Kubernetes cluster proposed by the present invention can create a control cluster, create a business cluster, and deploy in a specified VPC by enabling the container service after configuring the configuration information required by the cluster. Application containers do not need to be deployed in the cloud host to create control clusters, create business clusters, deploy application containers, etc., so as to realize the switch from cloud host deployment to containerized deployment, which is convenient for business management.
附图说明Description of drawings
图1为本发明一实施例提供的基于Kubernetes集群的管理方法的流程示意图；Fig. 1 is the schematic flow chart of the management method based on Kubernetes cluster that an embodiment of the present invention provides;
图2为图1中的步骤C的流程示意图；Fig. 2 is a schematic flow chart of step C in Fig. 1;
图3为本发明一实施例提供的基于Kubernetes集群的管理装置的内部结构示意图；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 present invention;
图4为本发明一实施例提供的基于Kubernetes集群的管理装置中基于Kubernetes集群的管理程序的模块示意图。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 present invention.
本发明目的的实现、功能特点及优点将结合实施例，参照附图做进一步说明。The realization of the purpose of the present invention, functional characteristics and advantages 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 present invention, not to limit the present invention.
本发明提供一种基于Kubernetes集群的管理方法。本实施例中，银行系统中包括配置管理系统和银行业务子系统，银行系统中有对应每一项目的项目路径。参照图1所示，为本发明一实施例提供的基于Kubernetes集群的管理方法的流程示意图。该方法可以由一个装置执行，该装置可以由软件和/或硬件实现。The invention provides a management method based on Kubernetes cluster. In this embodiment, the banking system includes a configuration management system and a banking business subsystem, and there is an item path corresponding to each item in the banking system. Referring to FIG. 1 , it is a schematic flowchart of a Kubernetes cluster-based management method provided by an embodiment of the present invention. The method may be performed by a device, and the device may be implemented by software and/or hardware.
在本实施例中，所述基于Kubernetes集群的管理方法包括：In this embodiment, the management method based on the Kubernetes cluster includes:
步骤A：确定Kubernetes集群所需的配置信息。其中，所述Kubernetes集群包括业务集群和控制集群。所述业务集群用于为容器应用提供运行环境，所述控制集群用于部署和管理业务集群内的每个应用程序或者业务等，所述所述控制集群也称为业务管理集群。Step A: Determine the configuration information required for 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, and the control cluster is used to deploy and manage each application program or service in the service cluster, and the control cluster is also called a service management cluster.
更进一步地，所述步骤A中所述“确定Kubernetes集群所需的配置信息”可以包括，但不限于包括：基础资源的配置信息、集群规模的配置信息、集群网络的配置信息、节点的配置项和Kubernetes应用的配置信息；Furthermore, the "determining the configuration information required by the Kubernetes cluster" in the step A may include, but is not limited to include: configuration information of basic resources, configuration information of cluster scale, configuration information of cluster network, configuration of nodes Items and configuration information for 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 image, key pair, node specification, external network;
所述集群规模的配置信息是指Kubernetes集群规模的配置信息，其包括：主节点个数和从节点个数；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;
所述集群网络的配置信息是Kubernetes集群网络的配置信息，其包括：业务网络类型、网段地址、子网掩码、网关、需要开通容器服务的虚拟私有云(Virtual PrivateCloud，VPC)、网络插件等；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 (Virtual PrivateCloud, VPC) that needs to open container services, network plug-ins Wait;
所述Kubernetes应用的配置信息包括：Kubernetes版本。The configuration information of the Kubernetes application includes: a Kubernetes version.
进一步地，所述步骤A包括：Further, said step A includes:
确定需要开通容器服务的VPC；Determine the VPC that needs to activate the container service;
确定Kubernetes集群是否为高可用；及determine whether the Kubernetes cluster is highly available; and
确定Kubernetes版本。Determine the Kubernetes version.
步骤B：根据所述配置信息开通相应的容器服务。Step B: Activate the corresponding container service according to the configuration information.
进一步地，所述步骤B包括：Further, the step B includes:
在指定的VPC中创建控制集群。其中，所述控制集群用于部署和管理所述业务集群内的每个应用程序。Create a control cluster in the specified VPC. Wherein, the control cluster is used to deploy and manage each application in the service cluster.
更进一步地，所述控制集群包括至少一组kubernetes控制面的组件，每组kubernetes控制面的组件可以包括，但不限于包括：kube-apiserver、kube-controller-manager、kube-scheduler、Etcd等组件。Furthermore, the control cluster includes at least one set of kubernetes control plane components, and each set of kubernetes control plane components may include, but is not limited to: kube-apiserver, kube-controller-manager, kube-scheduler, Etcd and other components .
其中，所述kubernetes控制面的组件解释如下：Among them, the components of the kubernetes control plane are explained as follows:
kube-apiserver：API服务器，用于暴露Kubernetes API；任何的资源请求/调用操作都是通过kube-apiserver提供的接口进行；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：控制器管理器；kube-controller-manager: controller manager;
kube-scheduler：容器调度器，用于监视新创建没有分配到节点的Pod，为Pod选择一个节点；kube-scheduler: Container scheduler, used to monitor newly created Pods that are not assigned to nodes, and select a node for Pods;
Etcd：键值数据库，用于保存集群数据。Etcd: key-value database for saving cluster data.
更进一步地，所述控制集群还包括至少一组kubernetes服务组件，每组kubernetes服务组件可以包括，但不限于包括：kube-proxy、kube-dns、tiller、addons、flannel等组件。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: kube-proxy, kube-dns, tiller, addons, flannel and other components.
其中，所述kubernetes服务组件解释如下：Wherein, the kubernetes service component is explained as follows:
kube-proxy：向前代理，通过在主机上维护网络规则并执行连接转发来实现Kubernetes服务抽象；kube-proxy: forward proxy, which implements Kubernetes service abstraction by maintaining network rules on the host and performing connection forwarding;
kube-dns：是指集群DNS(Domain Name Server)，是域名服务器，用于为Kubernetes services提供DNS记录；kube-dns: refers to the cluster DNS (Domain Name Server), which is a domain name server and is used to provide DNS records for Kubernetes services;
tiller：是Helm的服务端组件，Helm是Kubernetes的包管理工具；tiller: It is the server component of Helm, and Helm is the package management tool of Kubernetes;
addons：是指addons插件，用于实现集群pod和Services功能；addons: refers to the addons plug-in, which is used to realize the cluster pod and Services functions;
flannel：是kubernetes集群中的网络插件。flannel: is a network plug-in in the kubernetes cluster.
优选地，所述步骤“在指定的VPC中创建控制集群”包括监控步骤，其中，所述监控步骤包括：Preferably, the step "creating a control cluster in a designated VPC" includes a monitoring step, wherein the monitoring step includes:
采集云主机性能指标；及Collect cloud host performance indicators; and
根据采集到的云主机性能指标做界面图形展示。Graphical interface display based on the collected cloud host performance indicators.
其中，在一实施例中，所述云主机性能指标包括：主机的CPU使用率，MEM使用率等。Wherein, in an embodiment, the cloud host performance index includes: the CPU usage rate of the host machine, the MEM usage rate, and the like.
进一步地，所述监控步骤还包括：采集Kubernetes组件和容器的存在性、存活性指标。Further, the monitoring step also 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; It also includes: monitoring the application container on the business cluster.
具体地，在本实施例中，控制集群和业务集群中包括监控agent，通过控制集群和业务集群上运行的监控agent，采集云主机性能指标，并将采集到的云主机性能指标做界面图形展示。其中，监控agent是一种监控程序。Specifically, in this embodiment, the control cluster and the business cluster include a monitoring agent, and through the monitoring agent running on the control cluster and the business cluster, the cloud host performance indicators are collected, and the collected cloud host performance indicators are displayed as interface graphics . Wherein, the monitoring agent is a monitoring program.
进一步地，所述步骤“在指定的VPC中创建控制集群”还包括：日志步骤；具体地，所述日志步骤包括：当所述容器服务模块创建控制集群时生成日志；Further, the step "creating a control cluster in a specified VPC" also includes: a log step; specifically, the log step includes: generating a log when the container service module creates a control cluster;
其中，所述日志包括云主机的日志、管理集群组件日志和pod的日志。Wherein, the logs include cloud host logs, management cluster component logs, and pod logs.
优选地，为了方便用户不用登录到云主机就可以查看自己关注的日志，所述日志步骤还包括：通过监控agent将所有日志统一汇聚到日志云。Preferably, in order to make it convenient for users to view the logs they care about without logging in to the cloud host, the log step further includes: collecting all logs to the log cloud through the monitoring agent.
所述步骤“在指定的VPC中创建控制集群”还包括警报步骤：当控制集群的组件出现异常时，或者业务集群中的组件或者pod出现异常时，发送警报消息给相关人员。优选地，所述警报消息可以通过邮件、电话、短信等形式发送给相关人员。The step "creating a control cluster in the specified VPC" also includes an alarm step: when the components of the control cluster are abnormal, or the components or pods in the business cluster are abnormal, an alarm message is sent to relevant personnel. Preferably, the alarm message can be sent to relevant personnel by mail, telephone, short message and other forms.
进一步地，所述警报步骤包括：当控制集群节点上的所有组件和容器的存活性出现异常时，发送警报消息给相关人员。所述警报步骤还包括：当业务集群上的应用容器的警报出现异常时，发送警报消息给相关人员，例如，当pod出现异常时发送警报消息给相关人员。Further, the alarming step includes: when the survivability of all components and containers on the control cluster node is abnormal, sending an alarm message to relevant personnel. The alarming step further includes: when the alarm of the application container on the business cluster is abnormal, sending an alarm message to relevant personnel, for example, sending an alarm message to relevant personnel when an abnormality occurs in the pod.
步骤C：根据所述配置信息创建相应的业务集群。Step C: Create a corresponding service cluster according to the configuration information.
进一步地，请参阅图2，所述步骤C包括：Further, referring to Fig. 2, the step C includes:
步骤C1：指定业务集群所包含的节点数和业务名称；Step C1: Specify the number of nodes and business names contained in the business cluster;
步骤C2：调用云主机创建接口；Step C2: call the cloud host to create the interface;
步骤C3：创建云主机；Step C3: Create a cloud host;
步骤C4：将所有云主机添加到业务集群中，作为业务容器运行的节点。Step C4: Add all cloud hosts to the business cluster as nodes running business containers.
其中，在执行所述步骤C1的过程中，也可以在后续添加或者删除Kubernetes业务节点。Wherein, during the process of executing the step C1, Kubernetes service nodes may also be added or deleted later.
具体地，所述步骤C4包括：Specifically, the step C4 includes:
在创建完云主机后，将云主机添加到业务集群；After creating the cloud host, add the cloud host to the business cluster;
给云主机安装上Kubernetes业务节点所需的组件；Install the components required for the Kubernetes business node on the cloud host;
将集群节点、网络等信息存储在Etcd中。Store information such as cluster nodes and networks in Etcd.
优选地，所述Kubernetes业务节点所需的组件可以是：flannel、docker、kube-proxy、应用容器等。其中，docker是一个开源的应用容器引擎，用于运行容器。Preferably, the components required by the Kubernetes service node may be: flannel, docker, kube-proxy, application container, and the like. Among them, docker is an open source application container engine for running containers.
优选地，在本实施例中，采用Etcd存储系统存储各节点信息。通过所述Etcd能够快速有效地添加或者删除当前各个Kubernetes节点的信息。Preferably, in this embodiment, the Etcd storage system is used to store information of each node. The information of each current Kubernetes node can be quickly and effectively added or deleted through the Etcd.
进一步地，为了方便在创建core应用时，所述业务容器能调度到VPC中指定的节点上，所述步骤C4之后还包括：Further, for the convenience of creating the core application, the business container can be dispatched to the node specified in the VPC, and after the step C4, it also includes:
步骤C5：给所有节点配置指定的业务标签。例如，app＝core。Step C5: Configure designated service labels for all nodes. For example, app=core.
进一步地，为了隔离应用程序，所述步骤C包括：创建一个namespace(命名空间)资源对象。其中，将一个或者多个应用程序部署到一个业务集群中。Further, in order to isolate the application program, the step C includes: creating a namespace (namespace) resource object. Wherein, one or more application programs are deployed to a business cluster.
步骤D：根据所述配置信息部署相应的应用容器。Step D: Deploy corresponding application containers according to the configuration information.
优选地，为了确保所述应用容器创建成功后，能顺利调度到指定的节点上，所述步骤D包括：给每个应用程序配置好选择节点的配置项。优选地，在本实施例中，所述配置项包括：指定deployment中的spec.nodeSelector字段。Preferably, in order to ensure that the application container can be successfully scheduled to a designated node after being successfully created, the step D includes: configuring configuration items for each application program to select a node. Preferably, in this embodiment, the configuration item includes: specifying a spec.nodeSelector field in the deployment.
其中，deployment是Kubernetes的一种资源对象，用来更好的解决Pod的编排问题；pod代表一个应用；deployment是用来管理Kubernetes无状态应用的；spec.nodeSelector是让pod调度到配置特定标签的主机上。Among them, deployment is a resource object of Kubernetes, which is used to better solve the pod arrangement problem; pod represents an application; deployment is used to manage Kubernetes stateless applications; spec.nodeSelector is to allow pods to be scheduled to configure specific labels on the host.
优选地，一个或者多个应用程序有自己专属的运行环境，该一个或者多个应用程序与其它应用程序隔离；应用程序的资源不会被其它应用程序抢占，两个应用程序之间的异常问题，只可能因为接口调用异常，而不会因为资源抢占导致异常；通过这种隔离方式，可以提升问题定位效率，利于团队之间的协作。Preferably, one or more applications have their own exclusive 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 the abnormal problem between two applications , it may only be caused by interface call exceptions, not by resource preemption; through this isolation method, the efficiency of problem location can be improved, which is conducive to the collaboration between teams.
本发明提出的基于Kubernetes集群的管理方法解决了如何从云主机部署切换到容器化部署的技术问题，不需要用户掌握Kubernetes的专业知识，降低用户学习成本；本发明通过业务集群来管理业务，能让众多的传统用户快速使用基于Kubernetes的容器服务来管理容器应用，方便完成从云主机部署到容器化部署的快速部署；本发明还根据业务模块创建业务集群，从而方便管理业务模块；用户在使用过程中只需要创建自己的业务集群，并可将已容器化的业务部署其中。The Kubernetes cluster-based management method proposed by the present invention solves the technical problem of how to switch from cloud host deployment to containerized deployment, does not require users to master the professional knowledge of Kubernetes, and reduces user learning costs; the present invention manages services through service clusters, which can Let many traditional users quickly use Kubernetes-based container services to manage container applications, and facilitate the rapid deployment from cloud host deployment to containerized deployment; the present invention also creates business clusters according to business modules, thereby facilitating management of business modules; users are using During the process, you only need to create your own business cluster and deploy the containerized business in it.
本发明还提供一种基于Kubernetes集群的管理装置。参照图3所示，为本发明一实施例提供的基于Kubernetes集群的管理装置的内部结构示意图。The present invention also provides a Kubernetes cluster-based management device. Referring to FIG. 3 , it is a schematic diagram of an internal structure of a management device based on a Kubernetes cluster provided by an embodiment of the present invention.
在本实施例中，所述基于Kubernetes集群的管理装置可以是PC(PersonalComputer，个人电脑)，也可以是智能手机、平板电脑、便携计算机等终端设备。该基于Kubernetes集群的管理装置至少包括存储器11、处理器12、网络接口13以及通信总线14。In this embodiment, the management device based on the Kubernetes cluster may be a PC (Personal Computer, personal computer), or may be a terminal device such as a smart phone, a tablet computer, or a portable computer. The Kubernetes cluster-based management device at least includes a memory 11 , a processor 12 , a network interface 13 and a communication bus 14 .
其中，所述存储器11至少包括一种类型的计算机可读存储介质，所述计算机可读存储介质包括闪存、硬盘、多媒体卡、卡型存储器(例如，SD或DX存储器等)、磁性存储器、磁盘、光盘等。所述存储器11在一些实施例中可以是基于Kubernetes集群的管理装置的内部存储单元，例如该基于Kubernetes集群的管理装置的硬盘。所述存储器11在另一些实施例中也可以是基于Kubernetes集群的管理装置的外部存储设备，例如基于Kubernetes集群的管理装置上配备的插接式硬盘，智能存储卡(Smart Media Card,SMC)，安全数字(SecureDigital,SD)卡，闪存卡(Flash Card)等。进一步地，所述存储器11还可以既包括基于Kubernetes集群的管理装置的内部存储单元也包括外部存储设备。所述存储器11不仅可以用于存储安装于基于Kubernetes集群的管理装置的应用软件及各类数据，例如基于Kubernetes集群的管理程序的代码等，还可以用于暂时地存储已经输出或者将要输出的数据。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, magnetic disk , CD, etc. In some embodiments, the storage 11 may be an internal storage unit of the management device based on the Kubernetes cluster, for example, a hard disk of the management device based on the Kubernetes cluster. The memory 11 can also be an external storage device based on the management device of the Kubernetes cluster in other embodiments, such as a plug-in hard disk equipped on the management device based on the Kubernetes cluster, a smart memory card (Smart Media Card, SMC), Secure Digital (SecureDigital, SD) card, flash memory card (Flash Card), etc. Further, the storage 11 may also include both an internal storage unit of the Kubernetes cluster-based management device and an external storage device. The memory 11 can not only be used 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, but also can be used to temporarily store the data that has been output or will be output .
所述处理器12在一些实施例中可以是一中央处理器(Central Processing Unit,CPU)、控制器、微控制器、微处理器或其他数据处理芯片，用于运行所述存储器11中存储的程序代码或处理数据，例如执行基于Kubernetes集群的管理程序等。The processor 12 may be a central processing unit (Central Processing Unit, CPU), a controller, a microcontroller, a microprocessor or other data processing chips in some embodiments, and is used to run the data stored in the memory 11. Program code or data processing, such as executing Kubernetes cluster-based management programs, etc.
所述网络接口13可选的可以包括标准的有线接口、无线接口(如WI-FI接口)，通常用于在该基于Kubernetes集群的管理装置与其他电子设备之间建立通信连接。The network interface 13 may optionally include standard wired interfaces and wireless interfaces (such as WI-FI interfaces), which are generally used to establish communication connections between the Kubernetes cluster-based management device and other electronic devices.
所述通信总线14用于实现这些组件之间的连接通信。The communication bus 14 is used to realize connection and communication between these components.
图3仅示出了具有组件11至14以及基于Kubernetes集群的管理程序的基于Kubernetes集群的管理装置，本领域技术人员可以理解的是，图3示出的结构并不构成对基于Kubernetes集群的管理装置的限定，可以包括比图示更少或者更多的部件，或者组合某些部件，或者不同的部件布置。Fig. 3 only shows the management device based on the Kubernetes cluster with components 11 to 14 and the management program based on the Kubernetes cluster, those skilled in the art can understand that the structure shown in Fig. 3 does not constitute management based on the Kubernetes cluster Device definitions may include fewer or more components than shown, or combinations of certain components, or different arrangements of components.
在图3所示的基于Kubernetes集群的管理装置实施例中，所述存储器11中存储有基于Kubernetes集群的管理程序；所述处理器12执行所述存储器11中存储的基于Kubernetes集群的管理程序时实现如下步骤：In the management device embodiment based on the Kubernetes cluster shown in Figure 3, a management program based on the Kubernetes cluster is stored in the memory 11; when the processor 12 executes the management program based on the Kubernetes cluster stored in the memory 11 Implement the following steps:
步骤A：确定Kubernetes集群所需的配置信息。Step A: Determine the configuration information required for the Kubernetes cluster.
更进一步地，所述步骤A中所述“确定Kubernetes集群所需的配置信息”可以包括，但不限于包括：基础资源的配置信息、集群规模的配置信息、集群网络的配置信息、节点的配置项和Kubernetes应用的配置信息；Furthermore, the "determining the configuration information required by the Kubernetes cluster" in the step A may include, but is not limited to include: configuration information of basic resources, configuration information of cluster scale, configuration information of cluster network, configuration of nodes Items and configuration information for 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 image, key pair, node specification, external network;
所述集群规模的配置信息包括：主节点个数和从节点个数；The configuration information of the cluster scale includes: the number of master nodes and the number of slave nodes;
所述集群网络的配置信息包括：业务网络类型、网段地址、子网掩码、网关、需要开通容器服务的VPC、网络插件等；The configuration information of the cluster network includes: business network type, network segment address, subnet mask, gateway, VPC that needs to open container services, network plug-ins, etc.;
所述Kubernetes应用的配置信息包括：Kubernetes版本。The configuration information of the Kubernetes application includes: a Kubernetes version.
进一步地，所述步骤A包括：Further, said step A includes:
确定需要开通容器服务的VPC(Virtual Private Cloud，虚拟私有云)；Determine the VPC (Virtual Private Cloud, virtual private cloud) that needs to open the container service;
确定Kubernetes集群是否为高可用；及determine whether the Kubernetes cluster is highly available; and
确定Kubernetes版本。Determine the Kubernetes version.
步骤B：根据所述配置信息开通相应的容器服务。Step B: Activate the corresponding container service according to the configuration information.
进一步地，所述步骤B包括：Further, the step B includes:
在指定的VPC中创建控制集群。其中，所述控制集群用于部署和管理所述业务集群内的每个应用程序。Create a control cluster in the specified VPC. Wherein, the control cluster is used to deploy and manage each application in the service cluster.
更进一步地，所述控制集群包括至少一组kubernetes控制面的组件，每组kubernetes控制面的组件可以包括，但不限于包括：kube-apiserver、kube-controller-manager、kube-scheduler、Etcd等组件。Furthermore, the control cluster includes at least one set of kubernetes control plane components, and each set of kubernetes control plane components may include, but is not limited to: kube-apiserver, kube-controller-manager, kube-scheduler, Etcd and other components .
其中，所述kubernetes控制面的组件解释如下：Among them, the components of the kubernetes control plane are explained as follows:
kube-apiserver：API服务器，用于暴露Kubernetes API；任何的资源请求/调用操作都是通过kube-apiserver提供的接口进行；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：控制器管理器；kube-controller-manager: controller manager;
kube-scheduler：容器调度器，用于监视新创建没有分配到节点的Pod，为Pod选择一个节点；kube-scheduler: Container scheduler, used to monitor newly created Pods that are not assigned to nodes, and select a node for Pods;
Etcd：键值数据库，用于保存集群数据。Etcd: key-value database for saving cluster data.
更进一步地，所述控制集群还包括至少一组kubernetes服务组件，每组kubernetes服务组件可以包括，但不限于包括：kube-proxy、kube-dns、tiller、addons、flannel等组件。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: kube-proxy, kube-dns, tiller, addons, flannel and other components.
其中，所述kubernetes服务组件解释如下：Wherein, the kubernetes service component is explained as follows:
kube-proxy：向前代理，通过在主机上维护网络规则并执行连接转发来实现Kubernetes服务抽象；kube-proxy: forward proxy, which implements Kubernetes service abstraction by maintaining network rules on the host and performing connection forwarding;
kube-dns：是指集群DNS(Domain Name Server)，是域名服务器，用于为Kubernetes services提供DNS记录；kube-dns: refers to the cluster DNS (Domain Name Server), which is a domain name server and is used to provide DNS records for Kubernetes services;
tiller：是Helm的服务端组件，Helm是Kubernetes的包管理工具；tiller: It is the server component of Helm, and Helm is the package management tool of Kubernetes;
addons：是指addons插件，用于实现集群pod和Services功能；addons: refers to the addons plug-in, which is used to realize the cluster pod and Services functions;
flannel：是kubernetes集群中的网络插件。flannel: is a network plug-in in the kubernetes cluster.
优选地，所述步骤“在指定的VPC中创建控制集群”包括监控步骤，其中，所述监控步骤包括：Preferably, the step "creating a control cluster in a designated VPC" includes a monitoring step, wherein the monitoring step includes:
采集云主机性能指标；及Collect cloud host performance indicators; and
根据采集到的云主机性能指标做界面图形展示。Graphical interface display based on the collected cloud host performance indicators.
其中，在一实施例中，所述云主机性能指标包括：主机的CPU使用率，MEM使用率等。Wherein, in an embodiment, the cloud host performance index includes: the CPU usage rate of the host machine, the MEM usage rate, and the like.
进一步地，所述监控步骤还包括：采集Kubernetes组件和容器的存在性、存活性指标。Further, the monitoring step also 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; It also includes: monitoring the application container on the business cluster.
具体地，在本实施例中，控制集群和业务集群中包括监控agent，通过控制集群和业务集群上运行的监控agent，采集云主机性能指标，并将采集到的云主机性能指标做界面图形展示。其中，监控agent是一种监控程序。Specifically, in this embodiment, the control cluster and the business cluster include a monitoring agent, and through the monitoring agent running on the control cluster and the business cluster, the cloud host performance indicators are collected, and the collected cloud host performance indicators are displayed as interface graphics . Wherein, the monitoring agent is a monitoring program.
进一步地，所述步骤“在指定的VPC中创建控制集群”还包括：日志步骤；具体地，所述日志步骤包括：当所述容器服务模块创建控制集群时生成日志；Further, the step "creating a control cluster in a specified VPC" also includes: a log step; specifically, the log step includes: generating a log when the container service module creates a control cluster;
其中，所述日志包括云主机的日志、管理集群组件日志和pod的日志。Wherein, the logs include cloud host logs, management cluster component logs, and pod logs.
优选地，为了方便用户不用登录到云主机就可以查看自己关注的日志，所述日志步骤还包括：通过监控agent将所有日志统一汇聚到日志云。Preferably, in order to make it convenient for users to view the logs they care about without logging in to the cloud host, the log step further includes: collecting all logs to the log cloud through the monitoring agent.
所述步骤“在指定的VPC中创建控制集群”还包括警报步骤：当控制集群的组件出现异常时，或者业务集群中的组件或者pod出现异常时，发送警报消息给相关人员。优选地，所述警报消息可以通过邮件、电话、短信等形式发送给相关人员。The step "creating a control cluster in the specified VPC" also includes an alarm step: when the components of the control cluster are abnormal, or the components or pods in the business cluster are abnormal, an alarm message is sent to relevant personnel. Preferably, the alarm message can be sent to relevant personnel by mail, telephone, short message and other forms.
进一步地，所述警报步骤包括：控制集群节点的警报和业务集群的警报；具体地，所述警报步骤包括：当控制集群节点上的所有组件和容器的存活性出现异常时，发送警报消息给相关人员。Further, the alarming step includes: controlling the alarm of the cluster node and the alarm of the business cluster; specifically, the alarming step includes: when the survivability of all components and containers on the controlling cluster node is abnormal, sending an alarm message to Related personnel.
所述警报步骤还包括：当业务集群上的应用容器出现异常时，发送警报消息给相关人员，例如，当pod出现异常时发送警报消息给相关人员。The alarming step further includes: when the application container on the business cluster is abnormal, sending an alarm message to relevant personnel, for example, sending an alarm message to relevant personnel when the pod is abnormal.
步骤C：根据所述配置信息创建相应的业务集群。Step C: Create a corresponding service cluster according to the configuration information.
进一步地，所述步骤C包括：Further, the step C includes:
步骤C1：指定业务集群所包含的节点数和业务名称；Step C1: Specify the number of nodes and business names contained in the business cluster;
步骤C2：调用云主机创建接口；Step C2: call the cloud host to create the interface;
步骤C3：创建云主机；Step C3: Create a cloud host;
步骤C4：将所有云主机添加到业务集群中，作为业务容器运行的节点。Step C4: Add all cloud hosts to the business cluster as nodes running business containers.
其中，在执行所述步骤C1的过程中，也可以在后续添加或者删除Kubernetes业务节点。Wherein, during the process of executing the step C1, Kubernetes service nodes may also be added or deleted later.
具体地，所述步骤C4包括：Specifically, the step C4 includes:
在创建完云主机后，将云主机添加到业务集群；After creating the cloud host, add the cloud host to the business cluster;
给云主机安装上Kubernetes业务节点所需的组件；Install the components required for the Kubernetes business node on the cloud host;
将集群节点、网络等信息存储在Etcd中。Store information such as cluster nodes and networks in Etcd.
优选地，所述Kubernetes业务节点所需的组件可以是：flannel、docker、kube-proxy、应用容器等。其中，docker是一个开源的应用容器引擎，用于运行容器。Preferably, the components required by the Kubernetes service node may be: flannel, docker, kube-proxy, application container, and the like. Among them, docker is an open source application container engine for running containers.
进一步地，为了方便在创建core应用时，所述业务容器能调度到VPC中指定的节点上，所述步骤C4之后还包括：Further, for the convenience of creating the core application, the business container can be dispatched to the node specified in the VPC, and after the step C4, it also includes:
步骤C5：给所有节点配置指定的业务标签。例如，app＝core。Step C5: Configure designated service labels for all nodes. For example, app=core.
进一步地，为了隔离应用程序，所述步骤C包括：创建一个namespace(命名空间)资源对象。其中，将一个或者多个应用程序部署到一个业务集群中。Further, in order to isolate the application program, the step C includes: creating a namespace (namespace) resource object. Wherein, one or more application programs are deployed to a business cluster.
步骤D：根据所述配置信息部署相应的应用容器。Step D: Deploy corresponding application containers according to the configuration information.
优选地，为了确保所述应用容器创建成功后，能顺利调度到指定的节点上，所述步骤D包括：给每个应用程序配置好选择节点的配置项。优选地，在本实施例中，所述配置项包括：指定deployment中的spec.nodeSelector字段。Preferably, in order to ensure that the application container can be successfully scheduled to a designated node after being successfully created, the step D includes: configuring configuration items for each application program to select a node. Preferably, in this embodiment, the configuration item includes: specifying a spec.nodeSelector field in the deployment.
其中，deployment是Kubernetes的一种资源对象，用来更好的解决Pod的编排问题；pod代表一个应用；deployment是用来管理Kubernetes无状态应用的；spec.nodeSelector是让pod调度到配置特定标签的主机上。Among them, deployment is a resource object of Kubernetes, which is used to better solve the pod arrangement problem; pod represents an application; deployment is used to manage Kubernetes stateless applications; spec.nodeSelector is to allow pods to be scheduled to configure specific labels on the host.
优选地，一个或者多个应用程序有自己专属的运行环境，该一个或者多个应用程序与其它应用程序隔离；应用程序的资源不会被其它应用程序抢占，两个应用程序之间的异常问题，只可能因为接口调用异常，而不会因为资源抢占导致异常；通过这种隔离方式，可以提升问题定位效率，利于团队之间的协作。Preferably, one or more applications have their own exclusive 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 the abnormal problem between two applications , it may only be caused by interface call exceptions, not by resource preemption; through this isolation method, the efficiency of problem location can be improved, which is conducive to the collaboration between teams.
例如，参照图4所示，为本发明基于Kubernetes集群的管理装置一实施例中的基于Kubernetes集群的管理程序的程序模块示意图。在该实施例中，所述基于Kubernetes集群的管理程序可以被分割为配置模块10、容器服务模块20、创建模块30、部署模块40、监控模块50、警报模块60以及日志模块70，示例性地：For example, referring to FIG. 4 , it is a schematic diagram of a program module of a management program based on a Kubernetes cluster in an embodiment of a management device based on a Kubernetes cluster of the present invention. 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 :
所述配置模块10用于确定Kubernetes集群所需的配置信息。所述配置模块10还用于确定需要开通容器服务的VPC、确定Kubernetes集群是否为高可用、及确定Kubernetes版本。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 open the container service, determine whether the Kubernetes cluster is highly available, and determine the Kubernetes version.
所述容器服务模块20用于根据所述配置信息开通相应的容器服务。The container service module 20 is configured to open a corresponding container service according to the configuration information.
所述创建模块30用于根据所述配置信息创建相应的业务集群。The creation module 30 is used to create a corresponding service cluster according to the configuration information.
所述部署模块40用于根据所述配置信息部署相应的应用容器。The deployment module 40 is configured to deploy corresponding application containers according to the configuration information.
所述监控模块50用于采集云主机性能指标，及用于根据采集到的云主机性能指标做界面图形展示。The monitoring module 50 is used for collecting cloud host performance indicators, and for displaying interface graphics according to the collected cloud host performance indicators.
所述监控模块50采用cAdvisor，cAdvisor是一个用于收集、聚合处理和输出容器运行指标的守护进程，通过cAdvisor能获取Kubernetes集群中Docker各种性能数据。The monitoring module 50 adopts cAdvisor, and cAdvisor is a daemon process for collecting, aggregating, processing and outputting container operation indicators, and various performance data of Docker in the Kubernetes cluster can be obtained through cAdvisor.
所述警报模块60用于当控制集群的组件出现异常时，或者业务集群中的组件或者pod出现异常时，发送警报消息给相关人员。The alarm module 60 is configured to send an alarm message to relevant personnel when a component of the control cluster is abnormal, or a component or pod in the business cluster is abnormal.
所述日志模块70用于当所述容器服务模块创建控制集群时生成日志。The log module 70 is used to generate a log when the container service module creates a control cluster.
所述创建模块30还用于指定业务集群所包含的节点数和业务名称；还用于在指定业务集群所包含的节点数和业务名称后调用云主机创建接口；及用于在调用云主机创建接口后创建云主机；并用于在创建云主机后将所有云主机添加到业务集群中，作为业务容器运行的节点。The creation module 30 is also used to specify the number of nodes and business names that the business cluster contains; it is also used to call the cloud host to create an interface after the number of nodes and business names that the specified business cluster contains; and to create an interface when calling the cloud host. Create a cloud host after the interface; and add all cloud hosts to the business cluster after creating the cloud host, as a node running the business container.
进一步地，为了方便在创建core应用时，所述业务容器能调度到VPC中指定的节点上，所述创建模块30还用于给所有节点配置指定的业务标签。Further, in order to facilitate that the service container can be dispatched to specified nodes in the VPC when creating the core application, the creation module 30 is also configured to configure specified service tags for all nodes.
优选地，为了确保所述应用容器创建成功后，能顺利调度到指定的节点上，所述部署模块40还用于给每个应用程序配置好选择节点的配置项。优选地，在本实施例中，所述配置项包括：指定deployment中的spec.nodeSelector字段。Preferably, in order to ensure that the application container can be smoothly dispatched to a designated node after it is successfully created, the deployment module 40 is further configured to configure configuration items of selected nodes for each application. Preferably, in this embodiment, the configuration item includes: specifying a spec.nodeSelector field in the deployment.
优选地，本实施例中，采用Etcd存储系统存储各节点信息。通过所述Etcd能够快速有效地添加或者删除当前各个Kubernetes节点的信息。Preferably, in this embodiment, the Etcd storage system is used to store information of each node. The information of each current Kubernetes node can be quickly and effectively added or deleted through the Etcd.
上述配置模块10、容器服务模块20、创建模块30、部署模块40、监控模块50、警报模块60以及日志模块70等程序模块被执行时所实现的功能或操作步骤与上述实施例大体相同，在此不再赘述。The above-mentioned configuration module 10, container service module 20, creation module 30, deployment module 40, monitoring module 50, alarm module 60, log module 70 and other program modules are executed. This will not be repeated here.
此外，本发明实施例还提出一种计算机可读存储介质，所述计算机可读存储介质上存储有基于Kubernetes集群的管理程序，所述基于Kubernetes集群的管理程序可被一个或多个处理器执行，以实现如下操作：In addition, the embodiment of the present invention also proposes a computer-readable storage medium, the computer-readable storage medium 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 do the following:
步骤A：确定Kubernetes集群所需的配置信息；Step A: Determine the configuration information required by the Kubernetes cluster;
步骤B：根据所述配置信息开通相应的容器服务；Step B: activate the corresponding container service according to the configuration information;
步骤C：根据所述配置信息创建相应的业务集群；Step C: Create a corresponding business cluster according to the configuration information;
步骤D：根据所述配置信息部署相应的应用容器。Step D: Deploy corresponding application containers according to the configuration information.
其中，所述步骤A包括：Wherein, the step A includes:
确定需要开通容器服务的VPC；Determine the VPC that needs to activate the container service;
确定Kubernetes集群是否为高可用；及determine whether the Kubernetes cluster is highly available; and
确定Kubernetes版本。Determine the Kubernetes version.
所述步骤B包括：在指定的VPC中创建控制集群。The step B includes: creating a control cluster in a designated VPC.
优选地，所述步骤“在指定的VPC中创建控制集群”包括监控步骤，其中所述监控步骤包括：Preferably, the step "creating a control cluster in a specified VPC" includes a monitoring step, wherein the monitoring step includes:
采集云主机性能指标；及Collect cloud host performance indicators; and
根据采集到的云主机性能指标做界面图形展示。Graphical interface display based on the collected cloud host performance indicators.
进一步地，所述监控步骤还包括：采集Kubernetes组件和容器的存在性、存活性指标。Further, the monitoring step also includes: collecting the existence and survivability indicators of Kubernetes components and containers.
进一步地，所述步骤“在指定的VPC中创建控制集群”还包括：日志步骤，其中，所述日志步骤包括：当所述容器服务模块创建控制集群时生成日志；Further, the step of "creating a control cluster in a specified VPC" further includes: a log step, wherein the log step includes: generating a log when the container service module creates a control cluster;
所述步骤“在指定的VPC中创建控制集群”还包括警报步骤：当控制集群的组件出现异常时，或者业务集群中的组件或者pod出现异常时，发送警报消息给相关人员。The step "creating a control cluster in the specified VPC" also includes an alarm step: when the components of the control cluster are abnormal, or the components or pods in the business cluster are abnormal, an alarm message is sent to relevant personnel.
优选地，所述步骤C包括：Preferably, said step C includes:
步骤C1：指定业务集群所包含的节点数和业务名称；Step C1: Specify the number of nodes and business names contained in the business cluster;
步骤C2：调用云主机创建接口；Step C2: call the cloud host to create the interface;
步骤C3：创建云主机；及Step C3: Create a cloud host; and
步骤C4：将所有云主机添加到业务集群中，作为业务容器运行的节点。Step C4: Add all cloud hosts to the business cluster as nodes running business containers.
进一步地，所述步骤C4之后还包括：Further, after the step C4, it also includes:
步骤C5：给所有节点配置指定的业务标签。Step C5: Configure designated service labels for all nodes.
进一步地，所述步骤D包括：给每个应用程序配置好选择节点的配置项。Further, the step D includes: configuring the configuration item of the selected node for each application program.
本发明计算机可读存储介质具体实施方式与上述基于Kubernetes集群的管理装置和方法各实施例基本相同，在此不作累述。The specific implementation manners of the computer-readable storage medium of the present invention are basically the same as the above-mentioned embodiments of the Kubernetes cluster-based management device and method, and will not be repeated here.
本发明提出的基于Kubernetes集群的管理方法、装置及计算机可读存储介质，通过在配置集群所需的配置信息后开通容器服务，创建业务集群，并部署应用容器，在指定的VPC中创建控制集群；本发明解决了如何从云主机部署切换到容器化部署的技术问题，不需要用户掌握Kubernetes的专业知识，降低用户学习成本；本发明通过业务集群来管理业务，能让众多的传统用户快速使用基于Kubernetes的容器服务来管理容器应用，方便完成从云主机部署到容器化部署的快速部署；本发明还根据业务模块创建业务集群，从而方便管理业务模块；用户在使用过程中只需要创建自己的业务集群，并可将已容器化的业务部署其中。The management method, device and computer-readable storage medium based on the Kubernetes cluster proposed by the present invention create a business cluster by opening the container service after configuring the configuration information required by the cluster, deploying application containers, and creating a control cluster in a designated VPC ; The present invention solves the technical problem of how to switch from cloud host deployment to containerized deployment, does not require users to master Kubernetes expertise, and reduces user learning costs; the present invention manages services through business clusters, allowing many traditional users to quickly use Based on the container service of Kubernetes to manage container applications, it is convenient to complete the rapid deployment from cloud host deployment to containerized deployment; the invention also creates business clusters according to business modules, so as to facilitate the management of business modules; users only need to create their own during use Business clusters, where containerized services can be deployed.
需要说明的是，上述本发明实施例序号仅仅为了描述，不代表实施例的优劣。并且本文中的术语“包括”、或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、装置、物品或者方法不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、装置、物品或者方法所固有的要素。在没有更多限制的情况下，由语句“包括一……”限定的要素，并不排除在包括该要素的过程、装置、物品或者方法中还存在另外的相同要素。It should be noted that the serial numbers of the above embodiments of the present invention are only for description, and do not represent the advantages and disadvantages of the embodiments. And herein the term "comprising", or any other variation thereof, is intended to cover a non-exclusive inclusion such that a process, apparatus, article, or method comprising a set of elements includes not only those elements, but also items not expressly listed other elements, or also include elements inherent in such a process, apparatus, article, or method. Without further limitations, an element defined by the phrase "comprising a ..." does not preclude the presence of additional identical elements in the process, device, article or method comprising the element.
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在如上所述的一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。Through the description of the above embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus a necessary general-purpose hardware platform, and of course also by hardware, but in many cases the former is better implementation. Based on such an understanding, the technical solution of the present invention can be embodied in the form of a software product in essence or in other words, the part that contributes to the prior art, 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 enable a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in various embodiments of the present invention.
以上仅为本发明的优选实施例，并非因此限制本发明的专利范围，凡是利用本发明说明书及附图内容所作的等效结构或等效流程变换，或直接或间接运用在其他相关的技术领域，均同理包括在本发明的专利保护范围内。The above are only preferred embodiments of the present invention, and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made by using the description of the present invention and the contents of the accompanying drawings, or directly or indirectly used in other related technical fields , are all included in the scope of patent protection of the present invention in the same way.
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910704915.3ACN110531987A (en) | 2019-07-30 | 2019-07-30 | Management method, device and computer readable storage medium based on Kubernetes cluster |
| PCT/CN2019/118007WO2021017301A1 (en) | 2019-07-30 | 2019-11-13 | Management method and apparatus based on kubernetes cluster, and computer-readable storage medium |
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910704915.3ACN110531987A (en) | 2019-07-30 | 2019-07-30 | Management method, device and computer readable storage medium based on Kubernetes cluster |
| Publication Number | Publication Date |
|---|---|
| CN110531987Atrue CN110531987A (en) | 2019-12-03 |
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910704915.3APendingCN110531987A (en) | 2019-07-30 | 2019-07-30 | Management method, device and computer readable storage medium based on Kubernetes cluster |
| Country | Link |
|---|---|
| CN (1) | CN110531987A (en) |
| WO (1) | WO2021017301A1 (en) |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111327681A (en)* | 2020-01-21 | 2020-06-23 | 北京工业大学 | A construction method of cloud computing data platform based on Kubernetes |
| CN111367950A (en)* | 2020-02-28 | 2020-07-03 | 上海欣巴自动化科技股份有限公司 | Kubernetes-based distributed AGV (automatic guided vehicle) scheduling system and scheduling method |
| CN111427625A (en)* | 2020-03-23 | 2020-07-17 | 中国—东盟信息港股份有限公司 | Method for constructing Kubernetes container cloud external load balancer based on dynamic routing |
| CN111787063A (en)* | 2020-06-02 | 2020-10-16 | 深圳前海移联科技有限公司 | Channel route management method for business service |
| CN111782370A (en)* | 2020-06-30 | 2020-10-16 | 平安科技（深圳）有限公司 | Kubernetes multi-cluster management system, method, terminal and storage medium |
| CN111859428A (en)* | 2020-07-22 | 2020-10-30 | 成都安恒信息技术有限公司 | Containerization-based secret key storage method and system |
| CN111897541A (en)* | 2020-08-03 | 2020-11-06 | 上海嗨酷强供应链信息技术有限公司 | A software interaction platform and method for automatically deploying resources in a cloud environment |
| CN111984270A (en)* | 2020-08-20 | 2020-11-24 | 第四范式（北京）技术有限公司 | Application deployment method and system |
| CN112015753A (en)* | 2020-08-31 | 2020-12-01 | 南京易捷思达软件科技有限公司 | Monitoring system and method suitable for containerized deployment of open-source cloud platform |
| CN112187925A (en)* | 2020-09-28 | 2021-01-05 | 江苏银承网络科技股份有限公司 | Offline cluster management method and device for big data platform |
| CN112328456A (en)* | 2021-01-04 | 2021-02-05 | 北京电信易通信息技术股份有限公司 | Cluster resource monitoring system based on service discovery |
| CN112527449A (en)* | 2020-11-19 | 2021-03-19 | 北京浪潮数据技术有限公司 | Cluster node label creating method and system, electronic device and storage medium |
| CN112565475A (en)* | 2020-12-01 | 2021-03-26 | 成都精灵云科技有限公司 | IP address allocation method for adding new node to container cluster service layer |
| CN112671602A (en)* | 2020-12-14 | 2021-04-16 | 北京金山云网络技术有限公司 | Data processing method, device, system, equipment and storage medium of edge node |
| US11086700B2 (en) | 2018-08-24 | 2021-08-10 | Vmware, Inc. | Template driven approach to deploy a multi-segmented application in an SDDC |
| CN113419819A (en)* | 2021-06-25 | 2021-09-21 | 重庆紫光华山智安科技有限公司 | Container management method, device, equipment and medium |
| WO2021196080A1 (en) | 2020-04-01 | 2021-10-07 | Vmware Information Technology (China) Co., Ltd. | Auto deploying network elements for heterogeneous compute elements |
| CN113568684A (en)* | 2021-09-23 | 2021-10-29 | 中国电子科技集团公司第十五研究所 | Application hosting method, device and equipment and big data system |
| WO2021258719A1 (en)* | 2020-06-23 | 2021-12-30 | 海尔数字科技（上海）有限公司 | Billing method and system for container platform |
| CN113872997A (en)* | 2020-06-30 | 2021-12-31 | 华为技术有限公司 | Container group POD reconstruction method and related equipment based on container cluster service |
| CN113934711A (en)* | 2021-12-16 | 2022-01-14 | 天津南大通用数据技术股份有限公司 | Method for automatically deploying gbase8s cluster |
| US11277309B2 (en) | 2018-06-15 | 2022-03-15 | Vmware, Inc. | Hierarchical API for SDDC |
| CN114218039A (en)* | 2021-11-26 | 2022-03-22 | 新浪网技术(中国)有限公司 | A method and system for automatically generating kubernetes resource monitoring and data display graphs |
| CN114443214A (en)* | 2021-12-23 | 2022-05-06 | 天翼云科技有限公司 | Cloud-side kubernets management method and system |
| US11606254B2 (en) | 2021-06-11 | 2023-03-14 | Vmware, Inc. | Automatic configuring of VLAN and overlay logical switches for container secondary interfaces |
| US11748170B2 (en) | 2018-06-15 | 2023-09-05 | Vmware, Inc. | Policy constraint framework for an SDDC |
| US11803408B2 (en) | 2020-07-29 | 2023-10-31 | Vmware, Inc. | Distributed network plugin agents for container networking |
| US11831511B1 (en) | 2023-01-17 | 2023-11-28 | Vmware, Inc. | Enforcing network policies in heterogeneous systems |
| US11848910B1 (en) | 2022-11-11 | 2023-12-19 | Vmware, Inc. | Assigning stateful pods fixed IP addresses depending on unique pod identity |
| US11863352B2 (en) | 2020-07-30 | 2024-01-02 | Vmware, Inc. | Hierarchical networking for nested container clusters |
| US11902245B2 (en) | 2022-01-14 | 2024-02-13 | VMware LLC | Per-namespace IP address management method for container networks |
| CN117632017A (en)* | 2023-11-28 | 2024-03-01 | 中电云计算技术有限公司 | Cross-cluster shared storage method, device, equipment and medium under cloud native architecture |
| US12101244B1 (en) | 2023-06-12 | 2024-09-24 | VMware LLC | Layer 7 network security for container workloads |
| US12177124B2 (en) | 2022-10-04 | 2024-12-24 | VMware LLC | Using CRDs to create externally routable addresses and route records for pods |
| US12184450B2 (en) | 2022-03-18 | 2024-12-31 | VMware LLC | Mapping VLAN of container network to logical network in hypervisor to support flexible IPAM and routing container traffic |
| US12199833B2 (en) | 2022-11-29 | 2025-01-14 | VMware LLC | Network controller as a service (NCaaS) to define network policies for third-party container clusters |
| US12267212B2 (en) | 2022-11-29 | 2025-04-01 | VMware LLC | Implementing defined service policies in a third-party container cluster |
| WO2025098070A1 (en)* | 2023-11-08 | 2025-05-15 | 中国移动通信有限公司研究院 | Information processing method and apparatus, and device and readable storage medium |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US12299489B2 (en) | 2021-06-03 | 2025-05-13 | Red Hat, Inc. | Automatic dependency configuration for managed services |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105376303A (en)* | 2015-10-23 | 2016-03-02 | 深圳前海达闼云端智能科技有限公司 | Docker implementation system and communication method thereof |
| CN108549580A (en)* | 2018-03-30 | 2018-09-18 | 平安科技（深圳）有限公司 | Methods and terminal device of the automatic deployment Kubernetes from node |
| CN108809722A (en)* | 2018-06-13 | 2018-11-13 | 郑州云海信息技术有限公司 | A kind of method, apparatus and storage medium of deployment Kubernetes clusters |
| CN109150987A (en)* | 2018-07-27 | 2019-01-04 | 北京友普信息技术有限公司 | The two-layer container cluster elasticity expansion method of Intrusion Detection based on host layer and container floor |
| CN109800055A (en)* | 2018-12-27 | 2019-05-24 | 北京航天智造科技发展有限公司 | Container dispatches method of combination and system |
| CN109981351A (en)* | 2019-03-06 | 2019-07-05 | 浪潮通用软件有限公司 | A kind of private clound dispositions method |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10705880B2 (en)* | 2017-09-22 | 2020-07-07 | Vmware, Inc. | Cluster updating using temporary update-monitor pod |
| CN109491674A (en)* | 2018-11-07 | 2019-03-19 | 李斌 | A kind of method and system of the automatic deployment service in Kubernetes cluster |
| CN109885316B (en)* | 2019-02-18 | 2023-05-09 | 国家计算机网络与信息安全管理中心 | Hdfs-hbase deployment method and device based on kubernetes |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105376303A (en)* | 2015-10-23 | 2016-03-02 | 深圳前海达闼云端智能科技有限公司 | Docker implementation system and communication method thereof |
| CN108549580A (en)* | 2018-03-30 | 2018-09-18 | 平安科技（深圳）有限公司 | Methods and terminal device of the automatic deployment Kubernetes from node |
| CN108809722A (en)* | 2018-06-13 | 2018-11-13 | 郑州云海信息技术有限公司 | A kind of method, apparatus and storage medium of deployment Kubernetes clusters |
| CN109150987A (en)* | 2018-07-27 | 2019-01-04 | 北京友普信息技术有限公司 | The two-layer container cluster elasticity expansion method of Intrusion Detection based on host layer and container floor |
| CN109800055A (en)* | 2018-12-27 | 2019-05-24 | 北京航天智造科技发展有限公司 | Container dispatches method of combination and system |
| CN109981351A (en)* | 2019-03-06 | 2019-07-05 | 浪潮通用软件有限公司 | A kind of private clound dispositions method |
| Title |
|---|
| 石瑞生: "《网络空间安全专业规划教材 大数据安全与隐私保护》", 31 May 2019, 北京：北京邮电大学出版社, pages: 104 - 107* |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11689425B2 (en) | 2018-06-15 | 2023-06-27 | Vmware, Inc. | Hierarchical API for a SDDC |
| US12261746B2 (en) | 2018-06-15 | 2025-03-25 | VMware LLC | Hierarchical API for a SDDC |
| US12182630B2 (en) | 2018-06-15 | 2024-12-31 | VMware LLC | Policy constraint framework for an SDDC |
| US11277309B2 (en) | 2018-06-15 | 2022-03-15 | Vmware, Inc. | Hierarchical API for SDDC |
| US11748170B2 (en) | 2018-06-15 | 2023-09-05 | Vmware, Inc. | Policy constraint framework for an SDDC |
| US12197971B2 (en) | 2018-08-24 | 2025-01-14 | VMware LLC | Template driven approach to deploy a multi-segmented application in 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 (en)* | 2020-01-21 | 2020-06-23 | 北京工业大学 | A construction method of cloud computing data platform based on Kubernetes |
| CN111367950A (en)* | 2020-02-28 | 2020-07-03 | 上海欣巴自动化科技股份有限公司 | Kubernetes-based distributed AGV (automatic guided vehicle) scheduling system and scheduling method |
| CN111367950B (en)* | 2020-02-28 | 2023-08-08 | 上海欣巴自动化科技股份有限公司 | Distributed AGV scheduling system and scheduling method based on Kubernetes |
| CN111427625A (en)* | 2020-03-23 | 2020-07-17 | 中国—东盟信息港股份有限公司 | Method for constructing Kubernetes container cloud external load balancer based on dynamic routing |
| CN111427625B (en)* | 2020-03-23 | 2023-03-24 | 中国—东盟信息港股份有限公司 | Method for constructing Kubernetes container cloud external load balancer based on dynamic routing |
| US11689497B2 (en) | 2020-04-01 | 2023-06-27 | Vmware, Inc. | Auto deploying network for virtual private cloud with heterogenous workloads |
| US11436057B2 (en) | 2020-04-01 | 2022-09-06 | Vmware, Inc. | Administrative policy custom resource definitions |
| US11792159B2 (en) | 2020-04-01 | 2023-10-17 | Vmware, Inc. | Endpoint group containing heterogeneous workloads |
| US11671400B2 (en) | 2020-04-01 | 2023-06-06 | Vmware, Inc. | Defining and using service rules that reference endpoint group identifiers |
| WO2021196080A1 (en) | 2020-04-01 | 2021-10-07 | Vmware Information Technology (China) Co., Ltd. | Auto deploying network elements for heterogeneous compute elements |
| US12058102B2 (en) | 2020-04-01 | 2024-08-06 | VMware LLC | Virtual load-balanced service object |
| US11570146B2 (en) | 2020-04-01 | 2023-01-31 | Vmware, Inc. | Deploying and configuring different virtual networks for different workloads |
| US12120088B2 (en) | 2020-04-01 | 2024-10-15 | VMware LLC | Defining services for virtual interfaces of workloads |
| US11500688B2 (en) | 2020-04-01 | 2022-11-15 | Vmware, Inc. | Virtual network custom resource definition |
| CN111787063B (en)* | 2020-06-02 | 2023-05-16 | 深圳前海移联科技有限公司 | Channel route management method for business service |
| CN111787063A (en)* | 2020-06-02 | 2020-10-16 | 深圳前海移联科技有限公司 | Channel route management method for business service |
| WO2021258719A1 (en)* | 2020-06-23 | 2021-12-30 | 海尔数字科技（上海）有限公司 | Billing method and system for container platform |
| CN111782370B (en)* | 2020-06-30 | 2022-12-06 | 平安科技（深圳）有限公司 | Kubernetes multi-cluster management system, method, terminal and storage medium |
| CN113872997B (en)* | 2020-06-30 | 2022-08-26 | 华为技术有限公司 | Container group POD reconstruction method based on container cluster service and related equipment |
| CN111782370A (en)* | 2020-06-30 | 2020-10-16 | 平安科技（深圳）有限公司 | Kubernetes multi-cluster management system, method, terminal and storage medium |
| CN113872997A (en)* | 2020-06-30 | 2021-12-31 | 华为技术有限公司 | Container group POD reconstruction method and related equipment based on container cluster service |
| CN111859428B (en)* | 2020-07-22 | 2022-07-19 | 成都安恒信息技术有限公司 | Containerization-based secret key storage method and system |
| CN111859428A (en)* | 2020-07-22 | 2020-10-30 | 成都安恒信息技术有限公司 | Containerization-based secret key storage method and system |
| 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 |
| CN111897541A (en)* | 2020-08-03 | 2020-11-06 | 上海嗨酷强供应链信息技术有限公司 | A software interaction platform and method for automatically deploying resources in a cloud environment |
| CN111984270A (en)* | 2020-08-20 | 2020-11-24 | 第四范式（北京）技术有限公司 | Application deployment method and system |
| CN112015753A (en)* | 2020-08-31 | 2020-12-01 | 南京易捷思达软件科技有限公司 | Monitoring system and method suitable for containerized deployment of open-source cloud platform |
| CN112015753B (en)* | 2020-08-31 | 2023-10-31 | 北京易捷思达科技发展有限公司 | Monitoring system and method suitable for containerized deployment of open source cloud platform |
| CN112187925A (en)* | 2020-09-28 | 2021-01-05 | 江苏银承网络科技股份有限公司 | Offline cluster management method and device for big data platform |
| CN112527449A (en)* | 2020-11-19 | 2021-03-19 | 北京浪潮数据技术有限公司 | Cluster node label creating method and system, electronic device and storage medium |
| CN112565475A (en)* | 2020-12-01 | 2021-03-26 | 成都精灵云科技有限公司 | IP address allocation method for adding new node to container cluster service layer |
| CN112671602A (en)* | 2020-12-14 | 2021-04-16 | 北京金山云网络技术有限公司 | Data processing method, device, system, equipment and storage medium of edge node |
| CN112671602B (en)* | 2020-12-14 | 2023-07-04 | 北京金山云网络技术有限公司 | Data processing method, device, system, equipment and storage medium of edge node |
| CN112328456A (en)* | 2021-01-04 | 2021-02-05 | 北京电信易通信息技术股份有限公司 | Cluster resource monitoring system based on service discovery |
| US11606254B2 (en) | 2021-06-11 | 2023-03-14 | Vmware, Inc. | Automatic configuring of VLAN and overlay logical switches for container secondary interfaces |
| CN113419819A (en)* | 2021-06-25 | 2021-09-21 | 重庆紫光华山智安科技有限公司 | Container management method, device, equipment and medium |
| CN113419819B (en)* | 2021-06-25 | 2023-09-08 | 重庆紫光华山智安科技有限公司 | Container management method, device, equipment and medium |
| CN113568684A (en)* | 2021-09-23 | 2021-10-29 | 中国电子科技集团公司第十五研究所 | Application hosting method, device and equipment and big data system |
| CN114218039A (en)* | 2021-11-26 | 2022-03-22 | 新浪网技术(中国)有限公司 | A method and system for automatically generating kubernetes resource monitoring and data display graphs |
| CN113934711A (en)* | 2021-12-16 | 2022-01-14 | 天津南大通用数据技术股份有限公司 | Method for automatically deploying gbase8s cluster |
| CN113934711B (en)* | 2021-12-16 | 2022-03-15 | 天津南大通用数据技术股份有限公司 | Method for automatically deploying gbase8s cluster |
| CN114443214B (en)* | 2021-12-23 | 2025-05-27 | 天翼云科技有限公司 | A cloud-edge Kubernetes management method and system |
| CN114443214A (en)* | 2021-12-23 | 2022-05-06 | 天翼云科技有限公司 | Cloud-side kubernets management method and system |
| US11902245B2 (en) | 2022-01-14 | 2024-02-13 | VMware LLC | Per-namespace IP address management method for container networks |
| US12231398B2 (en) | 2022-01-14 | 2025-02-18 | VMware LLC | Per-namespace IP address management method for container networks |
| US12301382B2 (en) | 2022-03-18 | 2025-05-13 | VMware LLC | Mapping VLAN of container network to logical network in hypervisor to support flexible IPAM and routing container traffic |
| US12184450B2 (en) | 2022-03-18 | 2024-12-31 | VMware LLC | Mapping VLAN of container network to logical network in hypervisor to support flexible IPAM and routing container traffic |
| US12177124B2 (en) | 2022-10-04 | 2024-12-24 | VMware LLC | Using CRDs to create externally routable addresses and route records for pods |
| US11848910B1 (en) | 2022-11-11 | 2023-12-19 | Vmware, Inc. | Assigning stateful pods fixed IP addresses depending on unique pod identity |
| US12199833B2 (en) | 2022-11-29 | 2025-01-14 | VMware LLC | Network controller as a service (NCaaS) to define network policies for third-party container clusters |
| US12267212B2 (en) | 2022-11-29 | 2025-04-01 | VMware LLC | Implementing defined service policies in a third-party container cluster |
| US11831511B1 (en) | 2023-01-17 | 2023-11-28 | Vmware, Inc. | Enforcing network policies in heterogeneous systems |
| US12101244B1 (en) | 2023-06-12 | 2024-09-24 | VMware LLC | Layer 7 network security for container workloads |
| WO2025098070A1 (en)* | 2023-11-08 | 2025-05-15 | 中国移动通信有限公司研究院 | Information processing method and apparatus, and device and readable storage medium |
| CN117632017A (en)* | 2023-11-28 | 2024-03-01 | 中电云计算技术有限公司 | Cross-cluster shared storage method, device, equipment and medium under cloud native architecture |
| Publication number | Publication date |
|---|---|
| WO2021017301A1 (en) | 2021-02-04 |
| Publication | Publication Date | Title |
|---|---|---|
| CN110531987A (en) | Management method, device and computer readable storage medium based on Kubernetes cluster | |
| CN110535831B (en) | Kubernetes and network domain-based cluster security management method and device and storage medium | |
| US9038082B2 (en) | Resource abstraction via enabler and metadata | |
| CN106331150B (en) | For dispatching the method and apparatus of Cloud Server | |
| US10498857B2 (en) | System interaction monitoring and component scaling | |
| CN110908658A (en) | A "micro-service + micro-application" system, data processing method and device | |
| CN112925647A (en) | Cloud edge coordination system, and control method and device of cluster resources | |
| US11416294B1 (en) | Task processing for management of data center resources | |
| WO2019057055A1 (en) | Task processing method and apparatus, electronic device, and storage medium | |
| CN109245988A (en) | Monitor mail automatic sending method, system, computer equipment and storage medium | |
| CN109450693B (en) | Hybrid cloud monitoring system and monitoring method using same | |
| CN104160376A (en) | Offline provisioning of virtual machines | |
| CN113867884B (en) | Method and system for computer network and storage medium | |
| CN101853152A (en) | A method and system for generating a graphical user interface | |
| CN111625419A (en) | Log acquisition method, system, equipment and computer readable storage medium | |
| CN111294250B (en) | Pressure testing method, device and system | |
| CN110377489A (en) | The method and apparatus of log information processing | |
| CN116828035A (en) | Data integration system based on cloud computing | |
| CN112068953A (en) | Cloud resource fine management traceability system and method | |
| CN102904739B (en) | Method and Common Information Model CIM server that a kind of realization event forwards | |
| CN110472124A (en) | Data managing method, device and the storage medium of customer service system | |
| CN113923122B (en) | Deriving network device and host connections | |
| CN115390982A (en) | Method and device for realizing SAAS application arrangement engine, electronic equipment and storage medium | |
| CN107404410B (en) | Method and device for constructing virtual network function platform in cloud environment | |
| CN110333930A (en) | Digital platform system |
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication | Application publication date:20191203 |