CN112214330A - Method and device for deploying master nodes in cluster and computer-readable storage medium - Google Patents
Method and device for deploying master nodes in cluster and computer-readable storage medium Download PDFInfo
- Publication number
- CN112214330A CN112214330A CN202011217893.7A CN202011217893A CN112214330A CN 112214330 A CN112214330 A CN 112214330A CN 202011217893 A CN202011217893 A CN 202011217893A CN 112214330 A CN112214330 A CN 112214330A
- Authority
- CN
- China
- Prior art keywords
- resource object
- cluster
- predefined resource
- container cloud
- predefined
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
Images
Classifications
-
- 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
-
- 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/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- 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/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/4557—Distribution of virtual machine instances; Migration and load balancing
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application provides a method and a device for deploying a master node in a cluster and a computer-readable storage medium, wherein the method comprises the following steps: receiving a cluster creating request which comprises configuration information of a target Kubernetes cluster to be created; responding to a cluster creation request to create a corresponding namespace in a preset Kubernets cluster, and creating a predefined resource object based on configuration information, wherein the predefined resource object indicates a resource object required by a main node in the target Kubernets cluster; submitting the predefined resource object to a preset Kubernetes cluster through an APIServer in the preset Kubernetes cluster so as to enable an Operator control in the preset Kubernetes cluster to deploy the resource object in a name space and synchronize the running state of the predefined resource object to the APIServer; the running state of the predefined resource object is obtained through the APIServer, and the running state of the predefined resource object is determined to be running, the completion of the deployment of the main node corresponding to the target Kubernetes cluster is determined, and the scheme ensures that the state of each resource object can reach the expected state after the main node is deployed.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for deploying a master node in a cluster, and a computer-readable storage medium.
Background
The container cloud (kubernets) is an open-source container operation platform, can realize the functions of combining a plurality of containers into a service, dynamically distributing a host computer for container operation and the like, and provides great convenience for users to use the containers. Generally, a kubernets cluster (or a container cloud cluster) includes two types of nodes, namely a master node and a slave node, where the master node is responsible for managing and scheduling all resources in the kubernets cluster, and therefore, to create the kubernets cluster, the master node needs to be built first.
However, in the prior art, the deployment mode of the main node in the kubernets cluster cannot guarantee the running state of each component in the main node after the main node is deployed.
Disclosure of Invention
The purpose of this application is to solve at least one of the above technical defects, and the technical solution provided by this application embodiment is as follows:
in a first aspect, an embodiment of the present application provides a method for deploying a master node in a cluster, including:
receiving a cluster creating request, wherein the cluster creating request comprises configuration information of a target container cloud cluster to be created;
creating a namespace corresponding to the target container cloud cluster in the preset container cloud cluster in response to the cluster creation request, and creating a predefined resource object based on the configuration information, wherein the predefined resource object indicates a resource object required by a main node in the target container cloud cluster;
submitting the predefined resource object to a preset container cloud cluster through an application program interface service in the preset container cloud cluster so as to enable an application program controller control in the preset container cloud cluster to deploy the resource object in a naming space and synchronize the running state of the predefined resource object to the application program interface service;
and acquiring the running state of the predefined resource object through the application program interface service, and determining that the deployment of the main node corresponding to the target container cloud cluster is finished when the running state of the predefined resource object is running.
In a second aspect, an embodiment of the present application provides a method for deploying a master node in a cluster, including:
when a newly added event of a predefined resource object is monitored through an application program interface service in a preset container cloud cluster, starting a corresponding work coroutine for the predefined resource object, wherein the predefined resource object indicates a resource object required by a master node in a target container cloud cluster to be created;
deploying a resource object in a namespace corresponding to a target container cloud cluster in a preset container cloud cluster through a work coroutine, wherein the namespace is created after a cluster deployment control receives a cluster creation request;
and synchronizing the running state of the predefined resource object to the application program interface service so that the cluster deployment control acquires the running state of the predefined resource object through the application program interface service, and determining that the deployment of the main node corresponding to the target container cloud cluster is finished when the running state of the predefined resource object is running.
In a third aspect, an embodiment of the present application provides a device for deploying a master node in a cluster, including:
the system comprises a cluster creation request receiving module, a cluster creation request sending module and a cluster creation module, wherein the cluster creation request receiving module is used for receiving a cluster creation request which comprises configuration information of a target container cloud cluster to be created;
the system comprises a namespace and predefined resource object creating module, a resource allocation module and a resource allocation module, wherein the namespace and predefined resource object creating module is used for responding to a cluster creating request to create a namespace corresponding to a target container cloud cluster in a preset container cloud cluster and creating a predefined resource object based on configuration information, and the predefined resource object indicates resource objects required by main nodes in the target container cloud cluster;
the system comprises a predefined resource object submitting module, a resource object managing module and a resource object managing module, wherein the predefined resource object submitting module is used for submitting a predefined resource object to a preset container cloud cluster through an application program interface service in the preset container cloud cluster so as to enable an application program controller control in the preset container cloud cluster to deploy a resource object in a name space and synchronize the running state of the predefined resource object to the application program interface service;
and the predefined resource object running state monitoring module is used for acquiring the running state of the predefined resource object through the application program interface service, and determining that the deployment of the main node corresponding to the target container cloud cluster is finished when the running state of the predefined resource object is running.
In an optional embodiment of the present application, a definition file of a predefined resource object is pre-installed in a preset container cloud cluster, and an application controller control is pre-deployed in the preset container cloud cluster.
In an optional embodiment of the present application, the namespace and predefined resource object creation module is specifically configured to:
acquiring a predefined resource object template based on the definition file;
and generating the predefined resource object based on the configuration information and the predefined resource object template.
In a fourth aspect, an embodiment of the present application provides a device for deploying a master node in a cluster, including:
the working coroutine starting module is used for starting a corresponding working coroutine for a predefined resource object when a newly increased event of the predefined resource object is monitored through an application program interface service in a preset container cloud cluster, and the predefined resource object indicates a resource object required by a master node in a target container cloud cluster to be created;
the resource object deployment module is used for deploying resource objects in a naming space corresponding to a target container cloud cluster in a preset container cloud cluster through a work coroutine, and the naming space is created after a cluster deployment control receives a cluster creation request;
and the predefined resource object running state synchronization module is used for synchronizing the running state of the predefined resource object to the application program interface service so that the cluster deployment control acquires the running state of the predefined resource object through the application program interface service, and the running state of the predefined resource object is the running state, and the completion of the deployment of the main node corresponding to the target container cloud cluster is determined.
In an optional embodiment of the present application, the apparatus further comprises an operation status update module, configured to:
after deploying the resource object in the namespace corresponding to the target container cloud cluster in the preset container cloud cluster through the work coroutine, acquiring the actual state of the resource object;
and if the actual state of the resource object is the same as the expected state corresponding to the resource object, updating the running state of the predefined resource object to be running.
In an optional embodiment of the present application, the predefined resource object further indicates a desired state of the resource object.
In a fifth aspect, an embodiment of the present application provides an electronic device, including a memory and a processor;
the memory has a computer program stored therein;
a processor configured to execute a computer program to implement the method provided in the first aspect embodiment or the second aspect embodiment.
In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and the computer program, when executed by a processor, implements the method provided in the first aspect embodiment or the second aspect embodiment.
In a seventh aspect, the present application provides a computer program product or a computer program, where the computer program product or the computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device implements the method provided in the first aspect embodiment or the second aspect embodiment when executed.
The beneficial effect that technical scheme that this application provided brought is:
the method comprises the steps of creating a predefined resource object corresponding to a resource object required by a main node, deploying the resource object indicated by the predefined resource object through a preset application program controller (Operator) control, synchronizing the running state of the predefined resource object to an application program interface service (APIServer) in the deployment process for detection of a cluster deployment control, and determining that the main node is deployed when the running state of the predefined resource object is known to be running.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the description of the embodiments of the present application will be briefly described below.
Fig. 1 is a flow chart illustrating a pre-deployment process in an embodiment of the present application;
fig. 2 is a schematic flowchart of a method for deploying a master node in a cluster according to the present application;
FIG. 3 is a schematic flowchart illustrating actions performed by a cluster deployment control in an embodiment of the present application;
fig. 4 is a schematic flowchart of a method for deploying a master node in a cluster according to an embodiment of the present application;
fig. 5 is a schematic flowchart illustrating an action performed by an application controller (Operator) control in an embodiment of the present application;
FIG. 6 is a schematic flow chart of an overall scheme of an embodiment of the present application;
fig. 7 is a block diagram of a configuration apparatus for a master node in a cluster according to an embodiment of the present disclosure;
fig. 8 is a block diagram of a configuration apparatus for a master node in a cluster according to an embodiment of the present disclosure;
fig. 9 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
Reference will now be made in detail to embodiments of the present application, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are exemplary only for the purpose of explaining the present application and are not to be construed as limiting the present invention.
As used herein, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. It will be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may also be present. Further, "connected" or "coupled" as used herein may include wirelessly connected or wirelessly coupled. As used herein, the term "and/or" includes all or any element and all combinations of one or more of the associated listed items.
To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
The terms referred to in this application will first be introduced and explained:
application program interface service (APIServer): an HTTP (Resource Representational State Transfer) interface for the modification, deletion, check, monitoring and the like of various Resource objects of Kubernetes is provided, and the HTTP interface is a data bus and a data center of the whole system. The function of the APIServer: (1) providing a Rest API (Application Programming Interface) Interface (including authentication authorization, data verification and cluster state change) of cluster management; (2) a hub providing data interaction and communication between other modules (which query or modify data via the APIServer); (3) is an entry for resource quota control; (4) has a complete cluster security mechanism.
Application controller (Operator): the Kubernetes API is used for expanding Kubernetes API and is used for creating, configuring and managing complex stateful applications such as databases, caches and monitoring systems. The Operator is built on top of kubernets' resource and controller concept, but at the same time contains application specific domain knowledge.
Logical host (pod): a pod is a set of closely related containers that run together on the same worker node, and in the same Linux namespace. Each pod is like an independent logical machine, has its own IP (Internet Protocol), hostname, process, etc., and runs an independent application. All containers of one pod run on the same logical machine, and containers in other pods, even if running on the same working node, appear on different nodes. I.e., a pod contains multiple containers that always run on the same work node, a pod can never span multiple work nodes.
In the prior art, a host node deployment method in a Kubernetes cluster includes the following steps:
(1) the components required by the master node are manually installed on the host computer in a binary form by using yum installation (yum installation is one of three ways of linux installation software) or compiling, and the components are operated as a system-level daemon process. However, the manual deployment mode is very complicated, the error rate is high, and if an error occurs, the error is difficult to trace and repair.
(2) The method includes the steps that a kubbeadm tool (a tool for constructing a Kubernetes cluster) is adopted for deployment, components required by a main node are containerized, each component is deployed in a container mode, kubbelets (which can be understood as node agents running on the nodes) and dockers (which are open source application container engines are required to be installed on each node in advance, developers can pack applications of the kubbeadlet and rely on a portable container to be issued to popular Linux machines, virtualization can be achieved) to instantiate the container, and the pod on the main node is a static pod and can only run in a self-hosting pod mode without being managed by the Kubernetes. However, the static pod deployed by the kubeadm tool runs in a self-hosting manner, the health state of the main node component cannot be guaranteed, the kubeadm tool also shields a lot of deployment details, and if problems are encountered in the deployment process, errors are difficult to be checked.
(3) Writing a deployment script template in advance, generating a configuration script according to configuration parameters of a user, starting the deployment script on a node, and starting a component of a main node in a binary system mode. However, this approach has two disadvantages, one is that because the kubernets version updates very quickly, each update requires rewriting the details in the deployment script, which introduces complexity into version management. The second disadvantage is that after the main node components are deployed, the subsequent operating states of the components cannot be guaranteed.
In view of the foregoing problems, embodiments of the present application provide a method for deploying a master node in a cluster, and a specific implementation of the method will be described in detail below.
Before executing the deployment method of the master node in the cluster provided in the embodiment of the present application, a preset kubernets cluster needs to be created in advance, a definition file of a predefined resource object is submitted through an apicerver of the preset kubernets cluster, and the submitted definition file of the predefined resource object is installed in the preset kubernets cluster. Meanwhile, an Operator control needs to be deployed in a preset kubernets cluster, and particularly, the Operator control is deployed in the preset Operator control as a container. After the cluster creation and control deployment work is completed, a cluster deployment control corresponding to the preset kubernets cluster needs to be started, and the cluster deployment control can be deployed inside or outside the preset kubernets cluster.
As can be seen from the above description, the above process may be understood as a pre-deployment process of the solution provided in the present application, and an overall flow of the pre-deployment process may be as shown in fig. 1, including:
(1) a preset kubernets cluster is created.
(2) Installing a definition file of a predefined resource object in a preset Kubernets cluster, and deploying an Operator control in the preset Kubernets cluster.
(3) And starting a cluster deployment control.
Fig. 2 is a schematic flowchart of a method for deploying a master node in a cluster according to the present application, where an execution subject of the method may be a pre-started cluster deployment control, and as shown in fig. 2, the method may include:
step S201, receiving a cluster creating request, wherein the cluster creating request comprises configuration information of a target Kubernetes cluster to be created.
The configuration information may include a name of the target kubernets cluster, a corresponding subnet Identification (ID), a corresponding kubernets version number, and the like.
Specifically, the cluster deployment control receives a cluster creation request sent by a user, where the cluster creation request includes configuration information of a target Kubernetes cluster. Since the corresponding master node needs to be deployed in the process of creating the target kubernets cluster, when the cluster creation request is received, it is equivalent to that the master node deployment request of the target kubernets cluster is also received, and then, the master node needs to be deployed in response to the master node deployment request, so as to implement creation of the target kubernets cluster.
Step S202, a namespace corresponding to the target Kubernetes cluster is created in the preset Kubernetes cluster in response to the cluster creation request, and a predefined resource object is created based on the configuration information, wherein the predefined resource object indicates a resource object required by the main node in the target Kubernetes cluster.
The name space is a deployment space of a main node in the target Kubernets cluster, and the name space can be named by adopting the name of the target Kubernets cluster.
Wherein the predefined resource object indicates a resource object required by the master node in the target kubernets cluster, wherein the resource object required by the master node can be understood as a component required by the master node, for example, an api server, a Scheduler, a Controller Manager, and the like.
Specifically, when the cluster deployment control receives a cluster creation request sent by a user, in response to the cluster creation request, the cluster deployment control first creates a namespace corresponding to a target kubernets cluster in a preset kubernets cluster, and the namespace may be named by a cluster name of the target kubernets cluster. Then, the cluster deployment control creates a predefined resource object according to the configuration information and by combining with a pre-installed definition file of the predefined resource object, wherein the predefined resource object indicates a resource object required by a main node in the target Kubernets cluster, namely, components required by the main node.
Step S203, submitting the predefined resource object to a preset Kubernetes cluster through an APIServer in the preset Kubernetes cluster, so that an Operator control in the preset Kubernetes cluster deploys the resource object in a name space, and synchronizing the running state of the predefined resource object to the APIServer.
Specifically, the cluster deployment control submits the created predefined resource object to a preset Kubernetes cluster through an APIServer, because an Operator control in the preset Kubernetes cluster always monitors related events (including addition, modification, deletion and the like) of the predefined resource object in the APIServer, when the APIServer receives the submitted predefined resource object, the Operator control monitors the addition event of the predefined resource object. Next, the Operator control deploys the resource object required by the master node in the target Kubernetes cluster indicated by the predefined resource object to a corresponding namespace, and synchronizes the running state of the predefined resource object to the APIServer at certain intervals in the deployment process.
It should be noted that, in the scheme of this embodiment, a predefined resource object corresponding to each resource object required by the master node is created, and an Operator control which is pre-deployed and corresponds to the predefined resource object is used to deploy each resource object, and the deployment mode of the master node is closer to the operation mode of the native kubernets, so that the complexity of master node deployment is lower, and the accuracy is higher.
Step S204, acquiring the running state of the predefined resource object through the APIServer, and determining that the deployment of the main node corresponding to the target Kubernetes cluster is finished when the running state of the predefined resource object is running.
Specifically, since the Operator control synchronizes the running state of the predefined resource object to the apicerver at a certain interval, the cluster deployment control may obtain the running state of the predefined resource object from the apicerver to determine the deployment condition of the master node. Specifically, the cluster deployment control acquires the running state of the predefined resource object from the APIServer at a certain time interval, and determines that the deployment of the master node is finished when the running state of the predefined resource object is known to be running. The operation state of the predefined resource object is determined by the operation state of the corresponding resource object, and the actual state of the operation state of all the corresponding resource objects reaches the expected state, so that the operation state of the predefined resource object is the running state. Wherein the predefined resource objects further indicate the desired state of the corresponding respective resource object.
According to the scheme provided by the application, the predefined resource object corresponding to the resource object required by the main node is created, the resource object indicated by the predefined resource object is deployed through the preset Operator control, the running state of the predefined resource object is synchronized to the APIserver for the cluster deployment control to detect in the deployment process, the main node deployment is determined to be finished when the running state of the predefined resource object is known to be running, and the mode ensures that the state of each resource object can reach the expected state after the main node deployment.
In an optional embodiment of the present application, a definition file of a predefined resource object is preset in a kubernets cluster, and an Operator control is preset in the kubernets cluster.
Specifically, because the declarative API and the Controller mechanism are the basis of the kubernets design concept, the embodiment of the application creates a preset kubernets cluster in advance, installs a predefined resource object for the preset kubernets cluster, and deploys a corresponding Operator control. In particular, the definition file of a predefined resource object contains all the selectable attributes that create the predefined resource object type. The Operator control defines a Controller corresponding to each resource object indicated by the predefined resource object to ensure the running state of each resource object in the predefined resource object, and the Controller continuously synchronizes the expected state of each resource object from the API Server and tunes between the expected state and the actual state of each resource object, thereby realizing the final consistency of the two. Each component of the Kubernetes main node has fault migration capability and self-repairability.
In an optional embodiment of the present application, creating the predefined resource object based on the configuration information comprises:
acquiring a predefined resource object template based on the definition file;
and generating the predefined resource object based on the configuration information and the predefined resource object template.
The predefined resource object template may be additionally defined based on the definition file, and specifically, since the definition file of the predefined resource object includes all selectable attributes for creating the predefined resource object type, the corresponding attribute may be selected according to the requirement to determine the corresponding predefined resource template.
Specifically, after the cluster deployment control acquires the cluster creation request, first, configuration information included in the cluster creation request is acquired, a corresponding template is acquired from a preset Kubernetes, and then, a predefined resource object is generated based on the configuration information and the predefined resource object template.
As can be seen from the above description, in the solution provided in the present application, the flow of the actions performed by the cluster deployment control may be as shown in fig. 3, and includes:
(1) and receiving a cluster creation request sent by a user.
(2) A namespace is created in a preset Kubernets cluster and a predefined resource object is created based on configuration information in the cluster creation request.
(3) And acquiring the running state of the predefined resource object through the APIServer.
(4) It is determined whether a predefined resource object is running.
(5) And defining the running state of the resource object as running, and determining that the deployment of the main node corresponding to the target Kubernetes cluster is finished.
Fig. 4 is a schematic flowchart of a method for deploying a master node in a cluster according to an embodiment of the present application, where an execution subject of the method may be an Operator control, and as shown in fig. 4, the method may include:
step S401, when the APIServer in the preset Kubernets cluster monitors a new event of a predefined resource object, a corresponding work coroutine is started for the predefined resource object, and the predefined resource object indicates a resource object required by a master node in a target Kubernets cluster required to be created.
Wherein the predefined resource object indicates a resource object required by the master node in the target kubernets cluster, wherein the resource object required by the master node can be understood as a component required by the master node, such as APIServer, Scheduler, Controller Manager, and the like.
Specifically, the cluster deployment control submits the created predefined resource object to a preset Kubernetes cluster through an APIServer, because an Operator control in the preset Kubernetes cluster always monitors related events (including addition, modification, deletion and the like) of the predefined resource object in the APIServer, when the APIServer receives the submitted predefined resource object, the Operator control monitors the addition event of the predefined resource object.
Step S402, deploying resource objects in a namespace corresponding to a target Kubernets cluster in a preset Kubernets cluster through a work coroutine, wherein the namespace is created after a cluster deployment control receives a cluster creation request.
The name space is a deployment space of a main node in the target Kubernets cluster, and the name space can be named by adopting the name of the target Kubernets cluster. When the cluster deployment control receives a cluster creation request sent by a user, in response to the cluster creation request, the cluster deployment control creates a namespace corresponding to a target Kubernetes cluster in a preset Kubernetes cluster, and the namespace can be named by a cluster name of the target Kubernetes cluster. Then, the cluster deployment control creates a predefined resource object according to the configuration information and by combining with a pre-installed definition file of the predefined resource object, wherein the predefined resource object indicates a resource object required by a main node in the target Kubernets cluster, namely, components required by the main node.
Specifically, the Operator control deploys the resource object required by the master node in the target Kubernetes cluster indicated by the predefined resource object to the corresponding namespace, and synchronizes the running state of the predefined resource object to the APIServer at certain intervals in the deployment process. Specifically, the Operator control starts a work coroutine corresponding to the predefined resource object, and deploys the resource object in a namespace corresponding to a target Kubernets cluster in a preset Kubernets cluster through the work coroutine.
Step S403, synchronizing the running state of the predefined resource object to the APIServer, so that the cluster deployment control obtains the running state of the predefined resource object through the APIServer, and determining that the deployment of the master node corresponding to the target Kubernetes cluster is completed when the running state of the predefined resource object is running.
Specifically, since the Operator control synchronizes the running state of the predefined resource object to the apicerver at a certain interval, the cluster deployment control may obtain the running state of the predefined resource object from the apicerver to determine the deployment condition of the master node. Specifically, the cluster deployment control acquires the running state of the predefined resource object from the APIServer at a certain time interval, and determines that the deployment of the master node is finished when the running state of the predefined resource object is known to be running. The operation state of the predefined resource object is determined by the operation state of the corresponding resource object, and the actual state of the operation state of all the corresponding resource objects reaches the expected state, so that the operation state of the predefined resource object is the running state. Wherein the predefined resource objects further indicate the desired state of the corresponding respective resource object.
According to the scheme provided by the application, the predefined resource object corresponding to the resource object required by the main node is created, the resource object indicated by the predefined resource object is deployed through the preset Operator control, the running state of the predefined resource object is synchronized to the APIserver for the cluster deployment control to detect in the deployment process, the main node deployment is determined to be finished when the running state of the predefined resource object is known to be running, and the mode ensures that the state of each resource object can reach the expected state after the main node deployment.
In an optional embodiment of the present application, after deploying, by a work protocol, a resource object in a namespace corresponding to a target kubernets cluster in a preset kubernets cluster, the method further includes:
acquiring the actual state of the resource object;
and if the actual state of the resource object is the same as the expected state corresponding to the resource object, updating the running state of the predefined resource object to be running.
Wherein the predefined resource object also indicates a desired state of the resource object.
Specifically, for each resource object corresponding to the predefined resource object, when the Operator control deploys the resource object through the work coroutine, it needs to determine whether the actual state of each resource object is the same as the corresponding expected state, and if so, the running state of the predefined resource object is updated to be running and synchronized to the APIserver.
As can be seen from the above description, in the solution provided in the present application, the flow of actions performed by the Operator control may be as shown in fig. 5, including:
(1) and starting a corresponding work coroutine for the predefined resource object when a newly added event of the predefined resource object is monitored.
(2) And deploying each resource object corresponding to the predefined resource object in the name space through the work coordination process, and checking the actual state of each resource object.
(3) It is determined whether the actual state of each resource object is the same as the corresponding desired state.
(4) And if the actual state of each resource object is the same as the corresponding expected state, updating the running state of the predefined resource object to be running.
The overall scheme flow of the embodiment of the present application is further described with reference to fig. 6, and as shown in fig. 6, the scheme may include:
(1.0) the cluster deployment control receives a cluster creation request sent by a user.
(1.1) the cluster deployment control creates a namespace corresponding to the target Kubernetes cluster in a preset Kubernetes cluster.
(1.2) the cluster deployment control creates a predefined resource object and submits the predefined resource object to the Kubernetes cluster through the APIserver.
(1.3) the cluster deployment control acquires the running state of the predefined resource object through the APIserver.
(2.1) the Operator control listens through the APIserver.
And (2.2) when a new event of the predefined resource object is monitored, the Operator control starts a work coroutine (or a browser) corresponding to the predefined resource object.
And (2.3) the predefined resource object deploys the resource objects APIServer, Scheduler and Controller Manager corresponding to the predefined resource object in the name space through a work cooperation program.
(2.4) the Operator control synchronizes the running state of the predefined resource object to the APIserver.
It should be noted that, the present application relates to Cloud technology, and Cloud technology (Cloud technology) refers to a hosting technology for unifying serial resources such as hardware, software, and network in a wide area network or a local area network to implement calculation, storage, processing, and sharing of data.
Cloud technology (Cloud technology) is based on a general term of network technology, information technology, integration technology, management platform technology, application technology and the like applied in a Cloud computing business model, can form a resource pool, is used as required, and is flexible and convenient. Cloud computing technology will become an important support. Background services of the technical network system require a large amount of computing and storage resources, such as video websites, picture-like websites and more web portals. With the high development and application of the internet industry, each article may have its own identification mark and needs to be transmitted to a background system for logic processing, data in different levels are processed separately, and various industrial data need strong system background support and can only be realized through cloud computing.
The server may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as cloud service, a cloud database, cloud computing, a cloud function, cloud storage, network service, cloud communication, middleware service, domain name service, security service, CDN, big data and artificial intelligence platform. The terminal may be, but is not limited to, a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart speaker, a smart watch, and the like. The terminal and the server may be directly or indirectly connected through wired or wireless communication, and the application is not limited herein.
Fig. 7 is a block diagram of a configuration apparatus of a master node in a cluster according to an embodiment of the present disclosure, and as shown in fig. 7, the apparatus 700 may include: a cluster creation request receiving module 701, a namespace and predefined resource object creating module 702, a predefined resource object submitting module 703, and a predefined resource object running state monitoring module 704, wherein:
the cluster creation request receiving module 701 is configured to receive a cluster creation request, where the cluster creation request includes configuration information of a target kubernets cluster to be created;
the namespace and predefined resource object creating module 702 is configured to create, in response to the cluster creation request, a namespace corresponding to the target Kubernetes cluster in the preset Kubernetes cluster, and create a predefined resource object based on the configuration information, where the predefined resource object indicates a resource object required by a master node in the target Kubernetes cluster;
the pre-defined resource object submitting module 703 is configured to submit a pre-defined resource object to a preset Kubernetes cluster through an APIServer in the preset Kubernetes cluster, so that an Operator control in the preset Kubernetes cluster deploys the resource object in a namespace, and synchronizes an operating state of the pre-defined resource object to the APIServer;
the predefined resource object running state monitoring module 704 is configured to obtain a running state of the predefined resource object through the APIServer, and determine that the deployment of the master node corresponding to the target kubernet cluster is completed when the running state of the predefined resource object is running.
According to the scheme provided by the application, the predefined resource object corresponding to the resource object required by the main node is created, the resource object indicated by the predefined resource object is deployed through the preset Operator control, the running state of the predefined resource object is synchronized to the APIserver for the cluster deployment control to detect in the deployment process, the main node deployment is determined to be finished when the running state of the predefined resource object is known to be running, and the mode ensures that the state of each resource object can reach the expected state after the main node deployment.
In an optional embodiment of the present application, a definition file of a predefined resource object is preset in a kubernets cluster, and an Operator control is preset in the kubernets cluster.
In an optional embodiment of the present application, the namespace and predefined resource object creation module is specifically configured to:
acquiring a predefined resource object template based on the definition file;
and generating the predefined resource object based on the configuration information and the predefined resource object template.
Fig. 8 is a block diagram of a configuration apparatus for a master node in a cluster according to an embodiment of the present disclosure, and as shown in fig. 8, the apparatus 800 may include: a work coroutine starting module 801, a predefined resource object deployment module 802 and a predefined resource object running state synchronization module 803, wherein:
the working protocol starting module 801 is configured to start a corresponding working protocol for a predefined resource object when an APIServer in a preset kubernet cluster monitors a new event of the predefined resource object, where the predefined resource object indicates a resource object required by a master node in a target kubernet cluster to be created;
the pre-defined resource object deployment module 802 is configured to deploy a resource object in a namespace corresponding to a target kubernet cluster in a preset kubernet cluster through a work coroutine, where the namespace is created after a cluster deployment control receives a cluster creation request;
the predefined resource object running state synchronization module 803 is configured to synchronize the running state of the predefined resource object to the APIServer, so that the cluster deployment control obtains the running state of the predefined resource object through the APIServer, and when the running state of the predefined resource object is running, it is determined that the deployment of the master node corresponding to the target Kubernetes cluster is completed.
According to the scheme provided by the application, the predefined resource object corresponding to the resource object required by the main node is created, the resource object indicated by the predefined resource object is deployed through the preset Operator control, the running state of the predefined resource object is synchronized to the APIserver for the cluster deployment control to detect in the deployment process, the main node deployment is determined to be finished when the running state of the predefined resource object is known to be running, and the mode ensures that the state of each resource object can reach the expected state after the main node deployment.
In an optional embodiment of the present application, the apparatus further comprises an operation status update module, configured to:
after a resource object is deployed in a namespace corresponding to a target Kubernet cluster in a preset Kubernet cluster through a work coroutine, acquiring the actual state of the resource object;
and if the actual state of the resource object is the same as the expected state corresponding to the resource object, updating the running state of the predefined resource object to be running.
In an optional embodiment of the present application, the predefined resource object further indicates a desired state of the resource object.
Based on the same principle, an embodiment of the present application further provides an electronic device, where the electronic device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, the method provided in any optional embodiment of the present application is implemented, and specifically, the following situations are implemented:
receiving a cluster creating request which comprises configuration information of a target Kubernetes cluster to be created; responding to a cluster creating request to create a namespace corresponding to a target Kubernetes cluster in a preset Kubernetes cluster, and creating a predefined resource object based on configuration information, wherein the predefined resource object indicates a resource object required by a main node in the target Kubernetes cluster; submitting the predefined resource object to a preset Kubernetes cluster through an APIServer in the preset Kubernetes cluster so as to enable an Operator control in the preset Kubernetes cluster to deploy the resource object in a name space and synchronize the running state of the predefined resource object to the APIServer; and acquiring the running state of the predefined resource object through the APIServer, and determining that the deployment of the main node corresponding to the target Kubernetes cluster is finished when the running state of the predefined resource object is running.
Or when an APIServer in a preset Kubernets cluster monitors a newly added event of a predefined resource object, starting a corresponding work coroutine for the predefined resource object, wherein the predefined resource object indicates a resource object required by a main node in a target Kubernets cluster required to be established; deploying a resource object in a namespace corresponding to a target Kubernet cluster in a preset Kubernet cluster through a work coroutine, wherein the namespace is created after a cluster deployment control receives a cluster creation request; and synchronizing the running state of the predefined resource object to the APIServer so that the cluster deployment control acquires the running state of the predefined resource object through the APIServer, and determining that the deployment of the main node corresponding to the target Kubernetes cluster is finished when the running state of the predefined resource object is running.
The embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the method shown in any embodiment of the present application.
It is understood that the medium may store a computer program corresponding to an interactive method in video playing.
Fig. 9 is a schematic structural diagram of an electronic device to which the embodiment of the present application is applied, and as shown in fig. 9, the electronic device 900 shown in fig. 9 includes: a processor 901 and a memory 903. Wherein the processor 901 is coupled to the memory 903, such as via a bus 902. Further, the electronic device 900 may also include a transceiver 904, and the electronic device 900 may interact with other electronic devices through the transceiver 904. It should be noted that the transceiver 904 is not limited to one in practical applications, and the structure of the electronic device 900 is not limited to the embodiment of the present application.
In this embodiment, the processor 901 may be used to implement the function of the deployment apparatus of the master node in the cluster shown in fig. 7 or fig. 8.
The processor 901 may be a CPU, general purpose processor, DSP, ASIC, FPGA or other programmable logic device, transistor logic device, hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor 901 may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs, and microprocessors, among others.
The memory 903 may be, but is not limited to, a ROM or other type of static storage device that can store static information and instructions, a RAM or other type of dynamic storage device that can store information and instructions, an EEPROM, a CD-ROM or other optical disk storage, optical disk storage (including compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.
The memory 903 is used for storing application program codes for executing the scheme of the application, and the execution is controlled by the processor 901. The processor 901 is configured to execute application program codes stored in the memory 903 to implement the actions of the deployment apparatus of the master node in the cluster provided by the embodiment shown in fig. 7 or fig. 8.
Embodiments of the present application provide a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device realizes the following when executed:
receiving a cluster creating request which comprises configuration information of a target Kubernetes cluster to be created; responding to a cluster creating request to create a namespace corresponding to a target Kubernetes cluster in a preset Kubernetes cluster, and creating a predefined resource object based on configuration information, wherein the predefined resource object indicates a resource object required by a main node in the target Kubernetes cluster; submitting the predefined resource object to a preset Kubernetes cluster through an APIServer in the preset Kubernetes cluster so as to enable an Operator control in the preset Kubernetes cluster to deploy the resource object in a name space and synchronize the running state of the predefined resource object to the APIServer; and acquiring the running state of the predefined resource object through the APIServer, and determining that the deployment of the main node corresponding to the target Kubernetes cluster is finished when the running state of the predefined resource object is running.
Or when an APIServer in a preset Kubernets cluster monitors a newly added event of a predefined resource object, starting a corresponding work coroutine for the predefined resource object, wherein the predefined resource object indicates a resource object required by a main node in a target Kubernets cluster required to be established; deploying a resource object in a namespace corresponding to a target Kubernet cluster in a preset Kubernet cluster through a work coroutine, wherein the namespace is created after a cluster deployment control receives a cluster creation request; and synchronizing the running state of the predefined resource object to the APIServer so that the cluster deployment control acquires the running state of the predefined resource object through the APIServer, and determining that the deployment of the main node corresponding to the target Kubernetes cluster is finished when the running state of the predefined resource object is running.
It should be understood that, although the steps in the flowcharts of the figures are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and may be performed in other orders unless explicitly stated herein. Moreover, at least a portion of the steps in the flow chart of the figure may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed alternately or alternately with other steps or at least a portion of the sub-steps or stages of other steps.
The foregoing is only a partial embodiment of the present application, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present application, and these modifications and decorations should also be regarded as the protection scope of the present application.
Claims (10)
1. A method for deploying a master node in a cluster is characterized by comprising the following steps:
receiving a cluster creating request, wherein the cluster creating request comprises configuration information of a target container cloud cluster to be created;
creating a namespace corresponding to the target cluster in a preset container cloud cluster in response to the cluster creation request, and creating a predefined resource object based on the configuration information, wherein the predefined resource object indicates a resource object required by a master node in the target container cloud cluster;
submitting the predefined resource object to the preset container cloud cluster through an application program interface service in the preset container cloud cluster so that an application program controller control in the preset container cloud cluster deploys the resource object in the namespace and synchronizes the running state of the predefined resource object to the application program interface service;
and acquiring the running state of the predefined resource object through the application program interface service, and determining that the deployment of the main node corresponding to the target container cloud cluster is finished when the running state of the predefined resource object is running.
2. The method of claim 1, wherein the preset container cloud cluster is pre-installed with a definition file of the predefined resource object, and the preset container cloud cluster is pre-deployed with the application controller control.
3. The method of claim 2, wherein creating a predefined resource object based on the configuration information comprises:
acquiring the predefined resource object template based on the definition file;
generating the predefined resource object based on the configuration information and the predefined resource object template.
4. A method for deploying a master node in a cluster is characterized by comprising the following steps:
when a newly added event of a predefined resource object is monitored through an application program interface service in a preset container cloud cluster, starting a corresponding work coroutine for the predefined resource object, wherein the predefined resource object indicates a resource object required by a master node in a target container cloud cluster to be created;
deploying the resource object in a namespace corresponding to the target container cloud cluster in the preset container cloud cluster through the working coroutine, wherein the namespace is created after the cluster deployment control receives a cluster creation request;
and synchronizing the running state of the predefined resource object to the application program interface service so that the cluster deployment control acquires the running state of the predefined resource object through the application program interface service, and the running state of the predefined resource object is determined to be finished by the deployment of the main node corresponding to the target container cloud cluster when the predefined resource object is running.
5. The method of claim 4, further comprising, after deploying the resource object in the namespace corresponding to the target one of the preset container cloud clusters through the work coroutine:
acquiring the actual state of the resource object;
and if the actual state of the resource object is the same as the expected state corresponding to the resource object, updating the running state of the predefined resource object to be running.
6. The method of claim 5, wherein the predefined resource object further indicates the desired state of the resource object.
7. An apparatus for deploying a master node in a cluster, comprising:
the system comprises a cluster creation request receiving module, a cluster creation request sending module and a cluster creation module, wherein the cluster creation request receiving module is used for receiving a cluster creation request which comprises configuration information of a target container cloud cluster to be created;
a namespace and predefined resource object creation module, configured to create, in response to the cluster creation request, a namespace corresponding to the target container cloud cluster in a preset container cloud cluster, and create a predefined resource object based on the configuration information, where the predefined resource object indicates a resource object required by a master node in the target container cloud cluster;
a predefined resource object submitting module, configured to submit the predefined resource object to the preset container cloud cluster through an application program interface service in the preset container cloud cluster, so that an application program controller control in the preset container cloud cluster deploys the resource object in the namespace, and synchronizes an operating state of the predefined resource object to the application program interface service;
and the predefined resource object running state monitoring module is used for acquiring the running state of the predefined resource object through the application program interface service, and determining that the deployment of the main node corresponding to the target container cloud cluster is finished when the running state of the predefined resource object is running.
8. An apparatus for deploying a master node in a cluster, comprising:
the working co-project starting module is used for starting a corresponding working co-project for a predefined resource object when a newly added event of the predefined resource object is monitored through an application program interface service in a preset container cloud cluster, wherein the predefined resource object indicates a resource object required by a master node in a target container cloud cluster to be created;
a predefined resource object deployment module, configured to deploy, through the work coroutine, the resource object in a namespace corresponding to the target container cloud cluster in the preset container cloud cluster, where the namespace is created after the cluster deployment control receives the cluster creation request;
and the predefined resource object running state synchronization module is used for synchronizing the running state of the predefined resource object to the application program interface service so that the cluster deployment control acquires the running state of the predefined resource object through the application program interface service, and the running state of the predefined resource object is the running state, and the completion of the deployment of the main node corresponding to the target container cloud cluster is determined.
9. An electronic device comprising a memory and a processor;
the memory has stored therein a computer program;
the processor for executing the computer program to implement the method of any one of claims 1 to 6.
10. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011217893.7A CN112214330A (en) | 2020-11-04 | 2020-11-04 | Method and device for deploying master nodes in cluster and computer-readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011217893.7A CN112214330A (en) | 2020-11-04 | 2020-11-04 | Method and device for deploying master nodes in cluster and computer-readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112214330A true CN112214330A (en) | 2021-01-12 |
Family
ID=74058224
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011217893.7A Pending CN112214330A (en) | 2020-11-04 | 2020-11-04 | Method and device for deploying master nodes in cluster and computer-readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112214330A (en) |
Cited By (24)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112783646A (en) * | 2021-01-13 | 2021-05-11 | 中国工商银行股份有限公司 | Stateful application containerization deployment method and device |
| CN112817691A (en) * | 2021-01-27 | 2021-05-18 | 北京迈格威科技有限公司 | Resource allocation method, device, equipment and medium |
| CN113031874A (en) * | 2021-03-26 | 2021-06-25 | 网易（杭州）网络有限公司 | Cache processing method, device, equipment and storage medium based on Kubernetes cluster |
| CN113220420A (en) * | 2021-05-18 | 2021-08-06 | 北京百度网讯科技有限公司 | Service monitoring method, device, equipment, storage medium and computer program product |
| CN113238763A (en) * | 2021-05-17 | 2021-08-10 | 京东数字科技控股股份有限公司 | Application deployment method, device, storage medium and program product |
| CN113448686A (en) * | 2021-06-22 | 2021-09-28 | 深信服科技股份有限公司 | Resource deployment method and device, electronic equipment and storage medium |
| CN113535328A (en) * | 2021-07-22 | 2021-10-22 | 华云数据控股集团有限公司 | Application instance control method, device, equipment and storage medium |
| CN113553139A (en) * | 2021-07-28 | 2021-10-26 | 瑞幸咖啡信息技术(厦门)有限公司 | Hybrid multi-cloud management method, system, device and medium in container cloud environment |
| CN113572831A (en) * | 2021-07-21 | 2021-10-29 | 重庆星环人工智能科技研究院有限公司 | Communication method between Kubernetes clusters, computer equipment and medium |
| CN113626286A (en) * | 2021-08-04 | 2021-11-09 | 北京汇钧科技有限公司 | Multi-cluster instance processing method and device, electronic equipment and storage medium |
| CN113726855A (en) * | 2021-07-30 | 2021-11-30 | 北京奇艺世纪科技有限公司 | Service aggregation method, device, electronic equipment and computer-readable storage medium |
| CN113934711A (en) * | 2021-12-16 | 2022-01-14 | 天津南大通用数据技术股份有限公司 | Method for automatically deploying gbase8s cluster |
| CN114201240A (en) * | 2022-02-21 | 2022-03-18 | 联信弘方(北京)科技股份有限公司 | Method and device for configuring helm chart |
| CN114615340A (en) * | 2022-03-08 | 2022-06-10 | 北京字节跳动网络技术有限公司 | Request processing method and device, computer equipment and storage device |
| CN114650170A (en) * | 2022-02-24 | 2022-06-21 | 京东科技信息技术有限公司 | Cross-cluster resource management method, device, equipment and storage medium |
| CN114780170A (en) * | 2022-04-11 | 2022-07-22 | 远景智能国际私人投资有限公司 | Container resource configuration method, device, equipment and storage medium |
| CN115189995A (en) * | 2022-09-07 | 2022-10-14 | 江苏博云科技股份有限公司 | Multi-cluster network federal communication establishing method, equipment and storage medium in Kubernets environment |
| US20220357938A1 (en) * | 2021-05-04 | 2022-11-10 | Red Hat, Inc. | Automatically configuring and deploying a software operator in a distributed computing environment from a package |
| CN115361283A (en) * | 2022-10-20 | 2022-11-18 | 深圳依时货拉拉科技有限公司 | K8S-based cloud host management method and device and computer equipment |
| CN115361285A (en) * | 2022-07-05 | 2022-11-18 | 海南车智易通信息技术有限公司 | Method, device, equipment and medium for realizing off-line business mixed deployment |
| CN115686802A (en) * | 2023-01-03 | 2023-02-03 | 海马云（天津）信息技术有限公司 | Cloud computing cluster scheduling system |
| US20230133312A1 (en) * | 2021-11-04 | 2023-05-04 | Red Hat, Inc. | Enhancing Operator Installation and Upgrade Management and Verification |
| CN116501446A (en) * | 2023-06-09 | 2023-07-28 | 摩尔线程智能科技(北京)有限责任公司 | Kubernetes cluster deployment method and system and electronic equipment |
| CN116501446B (en) * | 2023-06-09 | 2024-06-07 | 摩尔线程智能科技(北京)有限责任公司 | Kubernetes cluster deployment method and system and electronic equipment |
-
2020
- 2020-11-04 CN CN202011217893.7A patent/CN112214330A/en active Pending
Cited By (38)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112783646A (en) * | 2021-01-13 | 2021-05-11 | 中国工商银行股份有限公司 | Stateful application containerization deployment method and device |
| CN112817691A (en) * | 2021-01-27 | 2021-05-18 | 北京迈格威科技有限公司 | Resource allocation method, device, equipment and medium |
| CN112817691B (en) * | 2021-01-27 | 2024-02-02 | 北京迈格威科技有限公司 | Resource allocation method, device, equipment and medium |
| CN113031874A (en) * | 2021-03-26 | 2021-06-25 | 网易（杭州）网络有限公司 | Cache processing method, device, equipment and storage medium based on Kubernetes cluster |
| CN113031874B (en) * | 2021-03-26 | 2022-05-13 | 网易（杭州）网络有限公司 | Cache processing method, device, equipment and storage medium based on Kubernetes cluster |
| US20220357938A1 (en) * | 2021-05-04 | 2022-11-10 | Red Hat, Inc. | Automatically configuring and deploying a software operator in a distributed computing environment from a package |
| US11900089B2 (en) * | 2021-05-04 | 2024-02-13 | Red Hat, Inc. | Automatically configuring and deploying a software operator in a distributed computing environment from a package |
| CN113238763A (en) * | 2021-05-17 | 2021-08-10 | 京东数字科技控股股份有限公司 | Application deployment method, device, storage medium and program product |
| CN113220420A (en) * | 2021-05-18 | 2021-08-06 | 北京百度网讯科技有限公司 | Service monitoring method, device, equipment, storage medium and computer program product |
| CN113448686B (en) * | 2021-06-22 | 2024-05-24 | 深信服科技股份有限公司 | Resource deployment method and device, electronic equipment and storage medium |
| CN113448686A (en) * | 2021-06-22 | 2021-09-28 | 深信服科技股份有限公司 | Resource deployment method and device, electronic equipment and storage medium |
| CN113572831B (en) * | 2021-07-21 | 2024-03-15 | 重庆星环人工智能科技研究院有限公司 | Communication method, computer equipment and medium between Kubernetes clusters |
| CN113572831A (en) * | 2021-07-21 | 2021-10-29 | 重庆星环人工智能科技研究院有限公司 | Communication method between Kubernetes clusters, computer equipment and medium |
| CN113535328B (en) * | 2021-07-22 | 2024-03-19 | 华云数据控股集团有限公司 | Application instance control method, device, equipment and storage medium |
| CN113535328A (en) * | 2021-07-22 | 2021-10-22 | 华云数据控股集团有限公司 | Application instance control method, device, equipment and storage medium |
| CN113553139A (en) * | 2021-07-28 | 2021-10-26 | 瑞幸咖啡信息技术(厦门)有限公司 | Hybrid multi-cloud management method, system, device and medium in container cloud environment |
| CN113726855B (en) * | 2021-07-30 | 2023-02-07 | 北京奇艺世纪科技有限公司 | Service aggregation method, device, electronic equipment and computer-readable storage medium |
| CN113726855A (en) * | 2021-07-30 | 2021-11-30 | 北京奇艺世纪科技有限公司 | Service aggregation method, device, electronic equipment and computer-readable storage medium |
| CN113626286A (en) * | 2021-08-04 | 2021-11-09 | 北京汇钧科技有限公司 | Multi-cluster instance processing method and device, electronic equipment and storage medium |
| US11989542B2 (en) * | 2021-11-04 | 2024-05-21 | Red Hat, Inc. | Enhancing operator installation and upgrade management and verification |
| US20230133312A1 (en) * | 2021-11-04 | 2023-05-04 | Red Hat, Inc. | Enhancing Operator Installation and Upgrade Management and Verification |
| CN113934711B (en) * | 2021-12-16 | 2022-03-15 | 天津南大通用数据技术股份有限公司 | Method for automatically deploying gbase8s cluster |
| CN113934711A (en) * | 2021-12-16 | 2022-01-14 | 天津南大通用数据技术股份有限公司 | Method for automatically deploying gbase8s cluster |
| CN114201240A (en) * | 2022-02-21 | 2022-03-18 | 联信弘方(北京)科技股份有限公司 | Method and device for configuring helm chart |
| CN114650170B (en) * | 2022-02-24 | 2024-02-02 | 京东科技信息技术有限公司 | Cross-cluster resource management method, device, equipment and storage medium |
| CN114650170A (en) * | 2022-02-24 | 2022-06-21 | 京东科技信息技术有限公司 | Cross-cluster resource management method, device, equipment and storage medium |
| CN114615340B (en) * | 2022-03-08 | 2023-10-20 | 抖音视界有限公司 | Request processing method and device, computer equipment and storage device |
| CN114615340A (en) * | 2022-03-08 | 2022-06-10 | 北京字节跳动网络技术有限公司 | Request processing method and device, computer equipment and storage device |
| CN114780170B (en) * | 2022-04-11 | 2023-07-21 | 远景智能国际私人投资有限公司 | Container resource configuration method, device, equipment and storage medium |
| CN114780170A (en) * | 2022-04-11 | 2022-07-22 | 远景智能国际私人投资有限公司 | Container resource configuration method, device, equipment and storage medium |
| CN115361285A (en) * | 2022-07-05 | 2022-11-18 | 海南车智易通信息技术有限公司 | Method, device, equipment and medium for realizing off-line business mixed deployment |
| CN115361285B (en) * | 2022-07-05 | 2024-02-23 | 海南车智易通信息技术有限公司 | Method, device, equipment and medium for realizing off-line service mixed deployment |
| CN115189995A (en) * | 2022-09-07 | 2022-10-14 | 江苏博云科技股份有限公司 | Multi-cluster network federal communication establishing method, equipment and storage medium in Kubernets environment |
| CN115361283A (en) * | 2022-10-20 | 2022-11-18 | 深圳依时货拉拉科技有限公司 | K8S-based cloud host management method and device and computer equipment |
| CN115686802B (en) * | 2023-01-03 | 2023-03-21 | 海马云（天津）信息技术有限公司 | Cloud computing cluster scheduling system |
| CN115686802A (en) * | 2023-01-03 | 2023-02-03 | 海马云（天津）信息技术有限公司 | Cloud computing cluster scheduling system |
| CN116501446A (en) * | 2023-06-09 | 2023-07-28 | 摩尔线程智能科技(北京)有限责任公司 | Kubernetes cluster deployment method and system and electronic equipment |
| CN116501446B (en) * | 2023-06-09 | 2024-06-07 | 摩尔线程智能科技(北京)有限责任公司 | Kubernetes cluster deployment method and system and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112214330A (en) | Method and device for deploying master nodes in cluster and computer-readable storage medium | |
| CN108809722B (en) | Method, device and storage medium for deploying Kubernetes cluster | |
| CN108829409B (en) | Distributed system rapid deployment method and system | |
| CN107766050B (en) | Heterogeneous application deployment method and device | |
| CN110752947B (en) | K8s cluster deployment method and device, and deployment platform | |
| US20210263714A1 (en) | System and method for autowiring of a microservice architecture | |
| US9003406B1 (en) | Environment-driven application deployment in a virtual infrastructure | |
| CN110413288B (en) | Application deployment method, device, server and storage medium | |
| CN111324571B (en) | Container cluster management method, device and system | |
| US9015712B1 (en) | Environment template-driven environment provisioning in a virtual infrastructure | |
| EP2893443B1 (en) | Re-configuration in cloud computing environments | |
| CN111930521A (en) | Method and device for deploying application, electronic equipment and readable storage medium | |
| CN112585919A (en) | Method for managing application configuration state by using cloud-based application management technology | |
| CN104536899A (en) | Software deploying and maintaining method based on intelligent cluster | |
| EP3149603B1 (en) | Customized configuration of cloud-based applications prior to deployment | |
| CN112364897B (en) | Distributed training method and device, storage medium and electronic equipment | |
| CN111800468A (en) | Cloud-based multi-cluster management method, device, medium and electronic equipment | |
| CN115220874B (en) | Kubernetes cluster deployment method, device, equipment and storage medium | |
| EP3230865B1 (en) | Recovery execution system using programatic generation of actionable workflows | |
| CN110890987A (en) | Method, device, equipment and system for automatically creating cluster | |
| CN111831567A (en) | Application test environment configuration method, device, system and medium | |
| CN113419818B (en) | Basic component deployment method, device, server and storage medium | |
| CN117112122A (en) | Cluster deployment method and device | |
| Gupta et al. | Deploying hadoop architecture using ansible and terraform | |
| CN112379934B (en) | Deployment method and device of cloud computing platform and storage medium |
Legal Events
| 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 |