WO2019184164A1 - Procédé de déploiement automatique de nœud travailleur de kubernetes, dispositif, appareil terminal et support de stockage lisible - Google Patents

Procédé de déploiement automatique de nœud travailleur de kubernetes, dispositif, appareil terminal et support de stockage lisible Download PDF

Info

Publication number
WO2019184164A1
WO2019184164A1 PCT/CN2018/097564 CN2018097564W WO2019184164A1 WO 2019184164 A1 WO2019184164 A1 WO 2019184164A1 CN 2018097564 W CN2018097564 W CN 2018097564W WO 2019184164 A1 WO2019184164 A1 WO 2019184164A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
deployed
kubernetes
identifier
slave
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.)
Ceased
Application number
PCT/CN2018/097564
Other languages
English (en)
Chinese (zh)
Inventor
刘俊杰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ping An Technology Shenzhen Co Ltd
Original Assignee
Ping An Technology Shenzhen Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ping An Technology Shenzhen Co Ltd filed Critical Ping An Technology Shenzhen Co Ltd
Publication of WO2019184164A1 publication Critical patent/WO2019184164A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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

Definitions

  • the present application belongs to the field of data processing technologies, and in particular, to a method, an apparatus, a terminal device, and a computer readable storage medium for automatically deploying a Kubernetes slave node.
  • Docker provides container technology that has become a research hotspot by dividing the resources managed by a single operating system into isolated groups and improving resource utilization.
  • This container technology allows several containers to run on the same host or virtual machine, each of which is a separate virtual environment or application.
  • Kubernetes as an open source container operation platform, can realize the functions of combining several containers into one service and dynamically allocating the host running the container, which provides great convenience for users to use the container.
  • the master node In the Kubernetes cluster, there are two types of nodes: the master node and the slave node.
  • the master node is responsible for the management and scheduling of resources in the Kubernetes cluster, while the slave node is responsible for hosting the container and is the host of the container.
  • the slave node In the prior art, if a new slave node is to be deployed in a Kubernetes cluster, a large number of components need to be manually installed on the corresponding host or virtual machine, and a large number of configurations are required. Therefore, the existing method of deploying the Kubernetes slave node mainly relies on manual operations, and the deployment process is cumbersome, and configuration errors are likely to occur during the deployment process, and the error rate is high.
  • the embodiment of the present application provides a method, an apparatus, a terminal device, and a computer readable storage medium for automatically deploying a Kubernetes slave node, so as to solve the problem that the Kubernetes slave node deployment is cumbersome and has a high error rate in the prior art. .
  • a first aspect of the embodiments of the present application provides a method for automatically deploying a Kubernetes slave node, including:
  • the request information includes a primary node identifier and a node parameter, where the node parameter is used to indicate a physical node or a virtual machine node;
  • the control server is invoked to find a node to be deployed corresponding to the node identifier to be deployed, and the node to be deployed is deployed as a Kubernetes slave node of the Kubernetes cluster.
  • a second aspect of an embodiment of the present application provides an apparatus for automatically deploying a Kubernetes slave node, which may include means for implementing the steps of the method of automatically deploying a Kubernetes slave node as described above.
  • a third aspect of the embodiments of the present application provides a terminal device, including a memory and a processor, where the computer stores computer readable instructions executable on the processor, the processor executing the computer
  • the steps of the above method of automatically deploying the Kubernetes slave node are implemented when the instruction is read.
  • a fourth aspect of embodiments of the present application provides a computer readable storage medium storing computer readable instructions that, when executed by a processor, implement the above-described auto-deployment Kubernetes slave node The steps of the method.
  • the embodiment of the present application obtains the request information of the user, and the request information includes a primary node identifier and a node parameter, where the node parameter is used to indicate a physical node or a virtual machine node, and the primary node of the Kubernetes is found by the primary node identifier, thereby determining the primary node of the Kubernetes.
  • the Kubernetes cluster and finds the node identifier to be deployed corresponding to the node parameter in the database, and finally calls the control server, and the control server searches for the node to be deployed corresponding to the node identifier to be deployed, and deploys the node to be deployed as a Kubernetes cluster.
  • the Kubernetes slave node after obtaining the request information of the user, implements the automatic deployment of the Kubernetes slave node, reduces the possibility of error in the deployment process, saves manpower, and improves the deployment efficiency.
  • FIG. 1 is a flowchart of an implementation of a method for automatically deploying a Kubernetes slave node in the first embodiment of the present application
  • FIG. 2 is a flowchart of an implementation of a method for automatically deploying a Kubernetes slave node in Embodiment 2 of the present application;
  • FIG. 3 is a flowchart of an implementation of a method for automatically deploying a Kubernetes slave node in Embodiment 3 of the present application;
  • FIG. 4 is a flowchart of an implementation of a method for automatically deploying a Kubernetes slave node in Embodiment 4 of the present application;
  • FIG. 5 is a flowchart of an implementation of a method for automatically deploying a Kubernetes slave node in Embodiment 5 of the present application;
  • FIG. 6 is an implementation structural diagram of a method for automatically deploying a Kubernetes slave node in Embodiment 6 of the present application;
  • FIG. 7 is a flowchart of an implementation of a method for automatically deploying a Kubernetes slave node in Embodiment 7 of the present application;
  • Embodiment 8 is a structural block diagram of an apparatus for automatically searching for logistics information in Embodiment 8 of the present application;
  • FIG. 9 is a schematic diagram of a terminal device in Embodiment 9 of the present application.
  • FIG. 1 is a flowchart of an implementation of a method for automatically deploying a Kubernetes slave node according to an embodiment of the present application. As shown in Figure 1, the method includes the following steps:
  • S101 Acquire user request information, where the request information includes a primary node identifier and a node parameter, where the node parameter is used to indicate a physical node or a virtual machine node.
  • the automatic deployment of the new Kubernetes slave node is implemented on the basis of the existing Kubernetes cluster.
  • Kubernetes is an open source platform for automated container operations. It can implement the functions of container deployment, scheduling, and inter-cluster expansion.
  • the physical machine nodes or virtual machines configured with Kubernetes environment are called Kubernetes nodes.
  • Kubernetes Cluster (Kubernetes Cluster) is composed of multiple Kubernetes nodes, which can realize the deployment and management of containers.
  • the Kubernetes Master which is responsible for scheduling and managing Kubernetes services, such as allocating a container of a service to a slave node of the Kubernetes cluster.
  • the Kubernetes master node contains four subcomponents, namely the database (Etcd) component and the interface service (Kube).
  • the ApiServer) component, the Kube Scheduler component and the Kube Controller Manager component in the embodiment of the present application, mainly relate to an interface service component of the Kubernetes master node, and the interface service component is configured to receive and process the request for the Kubernetes cluster.
  • the Kubernetes cluster also includes a Kubernetes Node (Kubernetes Node) for actually running the container allocated by the Kubernetes master node.
  • the nodes to be joined to the Kubernetes cluster are determined from the plurality of nodes of the slave node resource pool, wherein the slave node resource pool refers to a runnable physical node or virtual Machine collection.
  • the slave node resource pool refers to a runnable physical node or virtual Machine collection.
  • the cloud host virtual machine is a virtual host similar to the independent host on the cluster host, but it should be known that the slave node
  • the resource pool can also be used to store other physical nodes, such as physical servers, for use in the embodiments of the present application.
  • the user's request information is first obtained, wherein the request information includes the primary node identifier and the node parameter.
  • the master node identifier is an Internet Protocol Address (IP) provided by the interface service component of the Kubernetes master node, and the corresponding Kubernetes master node can be automatically found through the master node identifier, thereby finding the corresponding Kubernetes cluster.
  • IP Internet Protocol Address
  • the node parameter is related to the physical node or the virtual machine node, and is used to find a specific physical node or virtual machine node to be added to the Kubernetes cluster.
  • the physical node or the virtual machine node has the node identifier, and the node parameter and the node identifier.
  • the node parameters can be used to indicate the node identification, thereby indicating the physical node or the virtual machine node.
  • the front end page based on the Kubernetes cluster and the slave node resource pool is provided to the user, and the request information sent by the user through the front end page is received.
  • the Kubernetes cluster Since the Kubernetes cluster is established, you can obtain the cluster information of the Kubernetes cluster, such as the name of the Kubernetes cluster and the existing Kubernetes slave node name, and obtain the feature information of multiple cloud host virtual machines in the node resource pool, such as multiple clouds.
  • the name of the host virtual machine, etc., through the user interface provided by the Kubernetes cluster, the cluster information and feature information are integrated into the front-end page for display.
  • the request information corresponding to the user's selection result is automatically generated, and the request information is sent.
  • the Kubernetes cluster replaces the user query node and manually sends the request information, which improves the convenience of request information generation. It is worth mentioning that in order to improve the security of the request information, the request information is based on the Secure Sockets Layer-based hypertext transfer protocol (Hyper Text Transfer Protocol over Secure Socket Layer (HTTPS) format is sent.
  • HTTPS Secure Sockets Layer-based hypertext transfer protocol
  • the cluster information of the Kubernetes cluster and the feature information of the plurality of cloud host virtual machines related to the user equipment are provided to the user.
  • the front-end page including the cluster information and the feature information related to the user equipment is provided to the user according to the authority of the user equipment. For example, there may be multiple Kubernetes clusters. After determining the Kubernetes cluster to which the user equipment belongs, only the cluster information and feature information related to the Kubernetes cluster are provided to the user, which improves the security of the Kubernetes slave node process.
  • S102 Search for a Kubernetes cluster corresponding to the primary node identifier, and obtain a node identifier to be deployed corresponding to the node parameter from a database.
  • the request information is parsed to obtain the primary node identifier and the node parameter therein.
  • the corresponding Kubernetes primary node is found according to the primary node identifier, thereby determining the Kubernetes cluster corresponding to the Kubernetes primary node, and searching for the to-be-deployed node identifier corresponding to the node parameter from the database.
  • a Kubernetes Manager may be set to manage the Kubernetes cluster, and the operations of step S101 and step S102 are performed.
  • the management program parses the request information, and acquires the primary node identifier and the node parameter in the request information. Since the hypervisor may manage multiple Kubernetes clusters at the same time, after obtaining the primary node identifier, the Kubernetes cluster corresponding to the primary node identifier is determined, and the data interface provided by the database is called, and the node parameters are searched from multiple node identifiers in the database. Corresponding node ID to be deployed. It is worth mentioning that if there are multiple Kubernetes clusters, the database is shared by multiple Kubernetes clusters.
  • S103 Call a control server to find a node to be deployed corresponding to the node identifier to be deployed, and deploy the node to be deployed as a Kubernetes slave node of the Kubernetes cluster.
  • the hypervisor After obtaining the node identifier to be deployed, the hypervisor calls the control server, specifically calling the control server to add the node's add interface.
  • the control server is a standalone server and is not controlled by the Kubernetes cluster, and is mainly set in the control slave node.
  • a plurality of cloud host virtual machines in the node resource pool have corresponding node identifiers. Therefore, after obtaining the node identifiers to be deployed, the control server searches for the cloud host virtual machines corresponding to the node identifiers to be deployed in the slave node resource pool.
  • the node to be deployed and the nodes to be deployed are controlled and deployed as Kubernetes slaves of the Kubernetes cluster.
  • FIG. 6 shows an implementation architecture diagram of a method for automatically deploying a Kubernetes slave node.
  • the architecture diagram has a hypervisor configured to manage a Kubernetes cluster and a slave node resource pool to store multiple cloud host virtual machines.
  • the premise reflects the entire process of automatically deploying Kubernetes from a node.
  • the management program receives the request information of the user, and parses the primary node identifier and the node parameter in the request information, finds the corresponding Kubernetes cluster according to the primary node identifier, and finds the corresponding node identifier to be deployed from the database according to the node parameter.
  • the hypervisor invokes the control server, and the control server determines the cloud host virtual machine identified from the node to be deployed from the plurality of cloud host virtual machines of the node resource pool, and deploys the cloud host virtual machine as a Kubernetes Nodes are added to the Kubernetes cluster.
  • the embodiment shown in FIG. 1 shows that, in the embodiment of the present application, by acquiring the request information of the user, the request information includes the primary node identifier and the node parameter, and firstly, the object added by the Kubernetes slave node, that is, the identifier corresponding to the master node identifier is determined.
  • the Kubernetes cluster obtains the node identifier to be deployed corresponding to the node parameter from the database, and finally finds the node to be deployed corresponding to the node identifier to be deployed through the control server, and deploys the node to be deployed as the Kubernetes slave node of the Kubernetes cluster. Reduced manual operations and improved deployment efficiency of Kubernetes slave nodes by building automated deployments.
  • FIG. 2 is a flowchart of an implementation method of automatically deploying a Kubernetes slave node according to Embodiment 2 of the present application.
  • the embodiment refines the process after S102 to obtain S201 ⁇ S203, which are as follows:
  • S201 Acquire multiple available node identifiers of multiple available nodes in the node resource pool, and compare the to-be-deployed node identifier with the multiple available node identifiers.
  • the node stored in the node resource pool is a cloud host virtual machine
  • the slave node resource pool may also store other nodes such as physical nodes. It is used in the embodiment of the present application. Since the node parameter is included in the request information, and the request information is automatically generated according to the user selecting a cloud host virtual machine, the user can specify a cloud host virtual machine to select by writing a code, but in the present application In an embodiment, the user selects a cloud host virtual machine displayed on the front-end page by clicking on the front-end page of the Kubernetes cluster and the slave node resource pool, thereby completing the selection, and the background is completed.
  • the corresponding request information is automatically generated.
  • the state of the cloud host virtual machine cannot be known.
  • the front-end page is not updated in real time according to the status of the Kubernetes cluster and the slave node resource pool, and the request information is generated when the request information is generated.
  • the cloud host VM to which the node ID of the node to be deployed corresponds to the node parameter may have joined the Kubernetes cluster or other Kubernetes cluster corresponding to the master node identifier.
  • the plurality of available node identifiers of the plurality of available nodes in the node resource pool are obtained, and the node identifier to be deployed is compared with the plurality of available node identifiers.
  • the plurality of available nodes refers to a plurality of cloud host virtual machines in the slave resource pool that are not joined to the Kubernetes cluster and are in a running state.
  • the plurality of available node identities of the slave node resource pool are updated, and the plurality of available node identities are stored in the database.
  • the status of the node in the slave node resource pool is updated, and then multiple available nodes and corresponding multiple available node identifiers are updated.
  • the update may be real-time update, and the time interval may be updated.
  • multiple available node identifiers are stored in the database, and the deposit mode may be to newly create a state data table dedicated to storing the available node identifiers in the database.
  • multiple available node identifiers are obtained from the database, which reduces the operation complexity and improves the accuracy of the node selection to be deployed.
  • the node identifier to be deployed is compared with the plurality of available node identifiers. If the node identifier to be deployed is successfully matched with the one of the plurality of available node identifiers, the node identifier corresponding to the node to be deployed is proved to be corresponding. If the cloud host virtual machine is available, the node corresponding to the successfully available node identifier (the cloud host virtual machine) is used as the node to be deployed.
  • the error prompt may include a cloud host virtual machine corresponding to the node identifier to be deployed, so that the user can view the cloud host virtual machine.
  • multiple available node identifiers of multiple available nodes in the node resource pool are obtained, and the node identifier to be deployed is compared with multiple available node identifiers. And determining the validity of the node identifier to be deployed. If the node identifier to be deployed is successfully matched with the one of the plurality of available node identifiers, the node identifier to be deployed is valid, and the node corresponding to the successfully available node identifier is compared as the node to be deployed.
  • the node ID of the node to be deployed fails to be compared with the number of available node identifiers, the node ID of the node to be deployed is invalid, and an error message is sent to the user.
  • the validity of the node ID to be deployed is verified before the node to be deployed is determined. Waste, after the validity verification is passed, the node corresponding to the node ID to be deployed is guaranteed to be available.
  • FIG. 3 is a flowchart of an implementation of a method for automatically deploying a Kubernetes slave node according to Embodiment 3 of the present application.
  • the S103 is refined to obtain S301 ⁇ S302, which are as follows:
  • S301 Automatically send a deployment instruction corresponding to the request information to the control server.
  • the agent client On the node to be deployed (the cloud host VM) corresponding to the node ID to be deployed, the agent client (Agent) is pre-installed to operate the node to be deployed. Since the node to be deployed needs to be deployed as a Kubernetes slave node of the Kubernetes cluster, the management program of the Kubernetes cluster parses the content of the request information after receiving the request information from the user, and calls the control interface of the control server to the control. The server sends a deployment instruction corresponding to the request information, and preferably, the deployment instruction is sent in an HTTPS format.
  • S302 Establish a socket connection between the control server and the proxy client, so that after receiving the deployment instruction, the control server causes the proxy client to deploy the proxy according to the deployment instruction.
  • the node is deployed as the Kubernetes slave node of the Kubernetes cluster.
  • the control server establishes a socket connection with the proxy client, and the socket substantially provides the endpoint of the communication, so before the communication is implemented, the two parties first create an endpoint, that is, the control server.
  • Socket and proxy client sockets The establishment process of a socket connection is mainly divided into three steps, namely, controlling server monitoring, proxy client request, and connection confirmation.
  • the control server socket is in a waiting state, monitoring the connection request in the network in real time, and not looking for a specific proxy client socket; in the proxy client request process, the node to be deployed is installed.
  • the proxy client socket first obtains information about the control server socket, including controlling the address and port number of the server socket, and then sending a connection request to the control server socket; during the connection confirmation process, the control server set The connection successfully listens to the connection request of the proxy client socket, and in response to the connection request, sends information about the control server socket to the proxy client socket, and finally the proxy client socket control server After the socket information is related, the establishment of the socket connection is completed.
  • the proxy client After the control server establishes a socket connection with the proxy client, the proxy client is controlled based on the received deployment instruction, so that the proxy client performs the deployment operation on the node to be deployed according to the deployment instruction, and the node to be deployed is added.
  • the deployment instruction corresponding to the request information is automatically sent to the control server, and the control server establishes a socket connection with the proxy client, so that the control server receives the connection.
  • the control agent client deploys the node to be deployed as the Kubernetes slave node of the Kubernetes cluster according to the deployment instruction, and performs the deployment operation through the pre-installed proxy client, thereby further improving the automation degree of deploying the Kubernetes slave node, and controlling through A socket connection established between the server and the proxy client improves the stability of the deployment operation.
  • FIG. 4 is a flowchart of an implementation of a method for automatically searching for logistics information according to Embodiment 4 of the present application.
  • the process before S302 is refined to obtain S401 ⁇ S403, which are as follows:
  • S401 Extract parameters other than the authentication signature value from the deployment instruction, and calculate a calculated signature value of the parameter by using a parameter signature algorithm.
  • the control server performs an authentication operation.
  • the hypervisor extracts the parameters in the deployment instruction and sorts them, and calculates the authentication signature value through the parameter signature algorithm based on the sorted parameters and the customized string token.
  • the parameter signature algorithm is combined with a hash message authentication code (Hash-based)
  • the message authentication code (HMAC) and the Secure Hash Algorithm (SHA) algorithm are the HAMC-SHA1 signature authentication algorithm.
  • the calculated authentication signature value is the signature summary based on the sorted parameters and the token.
  • the control server extracts parameters other than the authentication signature value, sorts the parameters, and calculates the calculation based on the sorted parameters and the same string token through the HAMC-SHA1 signature authentication algorithm. Signature value.
  • control server compares the calculated signature value with the authentication signature value. If the calculated signature value is equal to the authentication signature value, the control server authenticates and continues to perform the socket connection between the control server and the proxy client. operating.
  • the authentication fails, and the control server does not have the authority to execute the deployment instruction, and then the subsequent operations are stopped.
  • the embodiment of the present application performs authentication before establishing a socket connection, thereby improving the security of the connection.
  • FIG. 5 is a flowchart of an implementation method for automatically deploying a Kubernetes slave node according to Embodiment 5 of the present application.
  • S103 is refined to obtain S501 ⁇ S503, which are as follows:
  • S501 Obtain a binary file related to the Kubernetes cluster from a file server.
  • S502 Acquire a slave service file in the binary file, and obtain a node address of the node to be deployed.
  • the binary file obtained from the file server includes a master node service file related to the Kubernetes master node and a slave node service file related to the Kubernetes slave node, wherein the master node service file includes an interface service component file and a scheduling component file, and the like.
  • the slave service files include Kubectl files, Kubelet files, and Kube-Proxy files. Therefore, in the embodiment of the present application, the slave node server file is obtained from the binary file, and the node address of the node to be deployed is obtained for deployment.
  • the master node identifier and the slave node identifier are respectively set for the master node service file and the slave node service file.
  • the slave node identifier is set to the slave node server and stored in the file server, when the node to be deployed is deployed later, the slave node service file is directly obtained from the file server according to the slave node identifier, and the master node is not acquired.
  • the service file and the binary file of the slave service file save the extraction of the binary file and improve the deployment efficiency.
  • S503 Automatically configure the slave node service based on the slave node service file and the node address.
  • the node to be deployed is cleaned.
  • the original configuration of the node to be deployed is cleared.
  • a certificate related to the Kubernetes cluster is generated, which mainly includes a certification authority (CA) certificate, a kubernetes certificate, an admin certificate, and a proxy certificate.
  • CA certification authority
  • a key file corresponding to the above certificate is also generated. Subsequent distribution of the key file, the specific distribution process will be described later.
  • the flannel service is configured and started based on the slave service file.
  • the flannel is the network planning service for Kubernetes, so that the docker containers created by the different Kubernetes slave nodes in the Kubernetes cluster have the full Kubernetes cluster.
  • the only virtual IP address on the other hand, the flannel is essentially the overlay network, that is, the transmission control protocol (Transmission) Control Protocol, TCP) Packets are encapsulated in another network packet for routing and communication.
  • TCP Transmission Control Protocol
  • Kubectl is a console tool for Kubernetes cluster management, which can provide users with a large number of commands for users to view Kubernetes cluster.
  • Kubelet is a container management tool on the Kubernetes slave node, which is used to process the task that the Kubernetes master node delivers to the Kubernetes slave node.
  • Kubelet registers the Kubernetes slave node information on the interface service component of the Kubernetes master node, and periodically reports to the Kubernetes master.
  • the node sends the resource usage of the Kubernetes slave node, while monitoring the container and node resources inside the Kubernetes slave node.
  • Kube-Proxy is the entry component of the Kubernetes service and is used to manage access to the Kubernetes service. Based on the node service file and the node address of the node to be deployed, the Kubectl service, the Kubelet service, and the Kube-Proxy service are sequentially deployed and started. It is worth mentioning that the CA certificate and the admin certificate corresponding key file are distributed to the Kubectl service. The CA certificate corresponding key file is distributed to the Kubelet service, and the CA certificate and the proxy certificate corresponding key file are distributed to the Kube-Proxy service. Finally, when the Kube-Proxy service is successfully deployed and started, the node to be deployed is successfully deployed as Kubernetes. From the node.
  • FIG. 7 is a flowchart showing an implementation of deploying a node to be deployed after setting a retry and recording mechanism.
  • Each of x, y, and z is an integer greater than zero.
  • the state of the node to be deployed is checked, and the binary is obtained.
  • Files, clean up the nodes to be deployed, generate certificate related files, configure and start the flannel service, install and start the container, configure and start the Kubectl service, configure and start the Kubelet service, and configure and start the Kube-Proxy service.
  • Mechanism and set the threshold of the number of times, when a link is successful, the next step.
  • the threshold of the number of inspections is y, y is greater than x, and the number of times the node to be deployed is not ready does not reach the check.
  • the link to check the status of the node to be deployed is re-entered. After all the links are passed, the deployment of the node to be deployed is completed.
  • the above method improves the fault tolerance of the node to be deployed through the retry and record mechanism, and facilitates the developer to locate the problem by recording the failed link. It is worth mentioning that the flowchart shown in FIG. 7 is only an example. In the actual application scenario, the threshold of the number of times and the waiting time of each link can be freely set according to actual conditions.
  • FIG. 8 is a structural block diagram of an apparatus for automatically deploying a Kubernetes slave node according to an embodiment of the present application.
  • the device is provided. include:
  • the obtaining unit 81 is configured to acquire request information of the user, where the request information includes a primary node identifier and a node parameter, where the node parameter is used to indicate a physical node or a virtual machine node;
  • the searching unit 82 is configured to search for a Kubernetes cluster corresponding to the primary node identifier, and obtain, from the database, a node identifier to be deployed corresponding to the node parameter;
  • the deployment unit 83 is configured to invoke a control server to find a node to be deployed corresponding to the node identifier to be deployed, and deploy the node to be deployed as a Kubernetes slave node of the Kubernetes cluster.
  • the searching unit 82 further includes:
  • An identifier obtaining unit configured to acquire a plurality of available node identifiers of the plurality of available nodes in the node resource pool, and compare the node identifier to be deployed with the plurality of available node identifiers;
  • a node determining unit configured to use, as the node to be deployed, a node corresponding to the successfully available node identifier, if the comparison between the node identifier to be deployed and the identifier of the multiple available node identifiers is successful;
  • an output unit configured to output an error prompt to the user if the comparison between the node identifier to be deployed and the multiple available node identifiers fails.
  • the deployment unit 83 includes:
  • An instruction sending unit configured to automatically send a deployment instruction corresponding to the request information to the control server
  • connection establishing unit configured to establish a socket connection between the control server and the proxy client, so that after receiving the deployment instruction, the control server causes the proxy client to perform the The node to be deployed is deployed as the Kubernetes slave node of the Kubernetes cluster.
  • connection establishing unit further includes:
  • a calculating unit configured to extract a parameter other than the authentication signature value from the deployment instruction, and calculate a calculated signature value of the parameter by using a parameter signature algorithm
  • An execution unit configured to perform an operation of establishing a socket connection between the control server and the proxy client if the authentication signature value is equal to the calculated signature value
  • Stopping the execution unit if the verification signature value is not equal to the calculated signature value, stopping performing the subsequent operation.
  • the deployment unit 83 includes:
  • a file obtaining unit configured to acquire a binary file related to the Kubernetes cluster from a file server
  • An address obtaining unit configured to acquire a slave node service file in the binary file, and obtain a node address of the node to be deployed;
  • a service configuration unit configured to automatically configure a slave node service based on the slave node service file and the node address.
  • FIG. 9 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • the terminal device 9 of this embodiment includes a processor 90 and a memory 91 in which computer readable instructions 92 executable on the processor 90 are stored, for example, a Kubernetes slave node is deployed. program of.
  • the processor 90 when executing the computer readable instructions 92, implements the functions of the various units of the apparatus embodiments described above, such as the functions of units 81 through 83 of FIG.
  • the computer readable instructions 92 may be partitioned into one or more modules/units that are stored in the memory 91 and executed by the processor 90, To complete this application.
  • the one or more modules/units may be a series of computer readable instruction segments capable of performing a particular function, the instruction segments being used to describe the execution of the computer readable instructions 92 in the terminal device 9.
  • the computer readable instructions 92 can be partitioned into an acquisition unit, a lookup unit, and a deployment unit, each unit having a specific function as described above.
  • the terminal device may include, but is not limited to, a processor 90 and a memory 91. It will be understood by those skilled in the art that FIG. 9 is only an example of the terminal device 9, does not constitute a limitation of the terminal device 9, may include more or less components than those illustrated, or combine some components, or different components.
  • the terminal device may further include an input/output device, a network access device, a bus, and the like.
  • the so-called processor 90 can be a central processing unit (Central Processing Unit, CPU), can also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), Application Specific Integrated Circuit (ASIC), off-the-shelf programmable gate array (Field-Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory 91 may be an internal storage unit of the terminal device 9, such as a hard disk or a memory of the terminal device 9.
  • the memory 91 may also be an external storage device of the terminal device 9, for example, a plug-in hard disk equipped on the terminal device 9, a smart memory card (SMC), and a secure digital (SD). Card, flash card, etc. Further, the memory 91 may also include both an internal storage unit of the terminal device 9 and an external storage device.
  • the memory 91 is configured to store the computer readable instructions and other programs and data required by the terminal device.
  • the memory 91 can also be used to temporarily store data that has been output or is about to be output.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • a computer readable storage medium A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer And Data Communications (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

La présente invention s'applique au domaine technique du traitement de données et concerne un procédé de déploiement automatique d'un nœud travailleur de Kubernetes, un appareil terminal et un support de stockage lisible par ordinateur. Le procédé consiste à : acquérir des informations de demande d'un utilisateur, les informations de demande comprenant un identifiant de nœud maître et un paramètre de nœud, et le paramètre de nœud indiquant un nœud physique ou un nœud de machine virtuelle ; rechercher une grappe de Kubernetes correspondant à l'identifiant de nœud maître, et acquérir, auprès d'une base de données, un identifiant d'un nœud à déployer correspondant au paramètre de nœud ; et appeler un serveur de commande, de façon à rechercher le nœud à déployer correspondant à l'identifiant du nœud à déployer, et déployer le nœud sous la forme d'un nœud travailleur de Kubernetes de la grappe de Kubernetes. La présente solution réalise un déploiement automatique de nœuds travailleurs de Kubernetes, réduit la possibilité d'erreur pendant un processus de déploiement, et améliore significativement l'efficacité de déploiement.
PCT/CN2018/097564 2018-03-30 2018-07-27 Procédé de déploiement automatique de nœud travailleur de kubernetes, dispositif, appareil terminal et support de stockage lisible Ceased WO2019184164A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810277483.8A CN108549580B (zh) 2018-03-30 2018-03-30 自动部署Kubernetes从节点的方法及终端设备
CN201810277483.8 2018-03-30

Publications (1)

Publication Number Publication Date
WO2019184164A1 true WO2019184164A1 (fr) 2019-10-03

Family

ID=63517533

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/097564 Ceased WO2019184164A1 (fr) 2018-03-30 2018-07-27 Procédé de déploiement automatique de nœud travailleur de kubernetes, dispositif, appareil terminal et support de stockage lisible

Country Status (2)

Country Link
CN (1) CN108549580B (fr)
WO (1) WO2019184164A1 (fr)

Cited By (35)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111193783A (zh) * 2019-12-19 2020-05-22 新浪网技术(中国)有限公司 一种服务访问的处理方法及装置
CN111651275A (zh) * 2020-06-04 2020-09-11 山东汇贸电子口岸有限公司 一种MySQL集群自动化部署系统及方法
CN111782766A (zh) * 2020-06-30 2020-10-16 福建健康之路信息技术有限公司 一种通过关键字检索Kubernetes集群中所有资源的方法和系统
CN111930466A (zh) * 2020-05-28 2020-11-13 武汉达梦数据库有限公司 一种基于Kubernetes的数据同步环境部署方法和装置
CN112099911A (zh) * 2020-08-28 2020-12-18 中国—东盟信息港股份有限公司 一种基于Kubernetes构建动态资源准入控制器的方法
CN112148429A (zh) * 2020-09-22 2020-12-29 江苏银承网络科技股份有限公司 用于管理容器编排引擎集群的信息处理方法及装置
CN113110917A (zh) * 2021-04-28 2021-07-13 北京链道科技有限公司 基于Kubernetes的数据发现和安全访问方法
CN113190239A (zh) * 2021-05-20 2021-07-30 洛阳轴承研究所有限公司 一种工业应用快速部署的方法
CN113360160A (zh) * 2020-03-05 2021-09-07 北京沃东天骏信息技术有限公司 部署应用的方法、装置、电子设备和存储介质
CN113377346A (zh) * 2021-06-10 2021-09-10 北京滴普科技有限公司 集成环境搭建方法、装置、电子设备及存储介质
CN113778331A (zh) * 2021-08-12 2021-12-10 联想凌拓科技有限公司 一种数据处理方法、主节点及存储介质
CN113849159A (zh) * 2021-09-18 2021-12-28 浪潮电子信息产业股份有限公司 源代码跨架构的同步构建方法、装置、设备及存储介质
CN113886146A (zh) * 2021-10-22 2022-01-04 郑州云海信息技术有限公司 一种异常处理方法、装置、设备及计算机可读存储介质
CN113965582A (zh) * 2020-07-20 2022-01-21 中移(苏州)软件技术有限公司 一种模式转换方法和系统，及存储介质
CN114006815A (zh) * 2020-07-13 2022-02-01 中移(苏州)软件技术有限公司 云平台节点的自动化部署方法、装置、节点及存储介质
CN114124903A (zh) * 2021-11-15 2022-03-01 新华三大数据技术有限公司 一种虚ip地址管理方法及装置
CN114116909A (zh) * 2021-12-01 2022-03-01 敏博科技(武汉)有限公司 一种分布式云原生数据库管理方法和系统
CN114138754A (zh) * 2021-12-09 2022-03-04 安超云软件有限公司 基于Kubernetes平台的软件部署方法及装置
CN114138590A (zh) * 2020-09-03 2022-03-04 中国移动通信集团湖南有限公司 Kubernetes集群的运维处理方法、装置及电子设备
CN114697985A (zh) * 2020-12-28 2022-07-01 中国联合网络通信集团有限公司 无线运维系统注册方法、装置、电子设备及存储介质
CN114760292A (zh) * 2020-12-25 2022-07-15 广东飞企互联科技股份有限公司 一种面向服务发现与注册的方法及装置
CN114884880A (zh) * 2022-04-06 2022-08-09 阿里巴巴（中国）有限公司 数据传输方法以及系统
CN115525416A (zh) * 2021-06-24 2022-12-27 中移(苏州)软件技术有限公司 管理方法、相关设备和存储介质
US20230060053A1 (en) * 2021-08-20 2023-02-23 Beijing Baidu Netcom Science Technology Co., Ltd. Method and apparatus of deploying a cluster, and storage medium
CN115981675A (zh) * 2022-12-06 2023-04-18 浪潮云信息技术股份公司 一种快速部署Kubernetes集群的方法及系统
CN116016545A (zh) * 2022-12-26 2023-04-25 上海浦东发展银行股份有限公司 Redis集群高可用的部署方法、装置、设备及存储介质
CN116009897A (zh) * 2022-12-28 2023-04-25 广东亿迅科技有限公司 一种多架构harbor-operator的集成与部署方法、系统、设备及存储介质
CN116233274A (zh) * 2023-02-09 2023-06-06 京东科技信息技术有限公司 一种信息处理方法及装置、存储介质
CN116244271A (zh) * 2022-12-29 2023-06-09 金篆信科有限责任公司 分布式数据库的部署方法、装置、电子设备及可读介质
CN117857343A (zh) * 2023-12-14 2024-04-09 天翼云科技有限公司 一种自动化更新Kubernetes调度器的方法
US12026561B2 (en) 2020-08-27 2024-07-02 Cisco Technology, Inc. Dynamic authentication and authorization of a containerized process
CN118573558A (zh) * 2024-06-14 2024-08-30 中国科学院空天信息创新研究院 云边系统的部署装置及方法
WO2025013032A1 (fr) * 2023-07-12 2025-01-16 Jio Platforms Limited Procédé et système d'automatisation d'un déploiement d'orchestration de conteneurs
EP4521250A1 (fr) * 2023-08-29 2025-03-12 Beijing Volcano Engine Technology Co., Ltd. Procédé et appareil de gestion de grappe, dispositif électronique et support de stockage
CN120162200A (zh) * 2025-05-20 2025-06-17 深圳市飞泉云数据服务有限公司 集群服务器调度方法、装置、设备及介质

Families Citing this family (35)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109445904B (zh) * 2018-09-30 2020-08-04 咪咕文化科技有限公司 一种信息处理方法、装置和计算机存储介质
CN109462508B (zh) * 2018-11-30 2021-06-01 北京百度网讯科技有限公司 节点部署方法、装置和存储介质
CN111865630B (zh) * 2019-04-26 2023-03-24 北京达佳互联信息技术有限公司 拓扑信息获取方法、装置、终端及存储介质
CN110196843B (zh) * 2019-05-17 2023-08-08 腾讯科技（深圳）有限公司 一种基于容器集群的文件分发方法及容器集群
CN110321207B (zh) * 2019-06-25 2026-02-10 深圳前海微众银行股份有限公司 任务调度方法、装置、设备及计算机可读存储介质
WO2021003729A1 (fr) * 2019-07-11 2021-01-14 深圳市大疆创新科技有限公司 Procédé de configuration, dispositif physique, serveur et support de stockage lisible par ordinateur
CN110531987A (zh) * 2019-07-30 2019-12-03 平安科技（深圳）有限公司 基于Kubernetes集群的管理方法、装置及计算机可读存储介质
CN110798375B (zh) * 2019-09-29 2021-10-01 烽火通信科技股份有限公司 一种增强容器集群高可用性的监控方法、系统及终端设备
CN110912827B (zh) * 2019-11-22 2021-08-13 北京金山云网络技术有限公司 一种路由更新方法和用户集群
CN112968919B (zh) * 2019-12-12 2023-05-30 上海欣诺通信技术股份有限公司 一种数据处理方法、装置、设备和存储介质
CN111259072B (zh) * 2020-01-08 2023-11-14 广州虎牙科技有限公司 数据同步方法、装置、电子设备和计算机可读存储介质
CN113918273B (zh) * 2020-07-10 2023-07-18 华为技术有限公司 一种容器组的创建方法和装置
CN112162857A (zh) * 2020-09-24 2021-01-01 珠海格力电器股份有限公司 一种集群服务器节点管理系统
CN112241314B (zh) * 2020-10-29 2022-08-09 浪潮通用软件有限公司 多Kubernetes集群管理方法、装置和可读介质
CN114443059A (zh) * 2020-10-30 2022-05-06 中国联合网络通信集团有限公司 Kubernetes集群的部署方法、装置及设备
CN112199167A (zh) * 2020-11-05 2021-01-08 成都精灵云科技有限公司 基于战场环境的多机快速一键部署的高可用方法
CN114579250B (zh) * 2020-12-02 2024-08-06 腾讯科技（深圳）有限公司 一种构建虚拟集群的方法、装置及存储介质
CN114650293B (zh) * 2020-12-17 2024-02-23 中移(苏州)软件技术有限公司 一种流量分流的方法、装置、终端和计算机存储介质
CN112286560B (zh) * 2020-12-30 2021-04-23 博智安全科技股份有限公司 一种分布式存储集群自动部署升级的方法及系统
CN112667355B (zh) * 2020-12-31 2025-01-21 联想未来通信科技(重庆)有限公司 一种信息处理方法及装置
CN112637037B (zh) * 2021-03-10 2021-06-18 北京瑞莱智慧科技有限公司 跨地域容器通讯系统、方法、存储介质及计算机设备
CN113127150B (zh) * 2021-03-18 2023-10-17 同盾控股有限公司 云原生系统的快速部署方法、装置、电子设备和存储介质
CN113138717B (zh) * 2021-04-09 2022-11-11 锐捷网络股份有限公司 节点部署方法、设备及存储介质
CN113064600B (zh) * 2021-04-20 2022-12-02 支付宝(杭州)信息技术有限公司 部署应用的方法和装置
CN114024841B (zh) * 2021-08-04 2023-09-19 统信软件技术有限公司 一种服务器集群部署方法、装置、计算设备及存储介质
CN114124703B (zh) * 2021-11-26 2024-01-23 浪潮卓数大数据产业发展有限公司 一种基于Kubernetes的多环境服务配置方法、设备及介质
CN116208607A (zh) * 2021-11-30 2023-06-02 龙芯中科(合肥)技术有限公司 节点管理方法、装置及电子设备
CN116340416A (zh) * 2021-12-22 2023-06-27 中兴通讯股份有限公司 数据库部署方法、数据库处理方法、相关设备及存储介质
CN116418660A (zh) * 2021-12-31 2023-07-11 航天信息股份有限公司 一种组网部署方法、装置、电子设备和存储介质
CN114546429B (zh) * 2022-02-24 2025-11-25 浙江大华技术股份有限公司 一种大数据集群的组建方法、装置、介质和电子设备
CN114936898B (zh) * 2022-05-16 2023-04-18 广州高专资讯科技有限公司 一种基于现货供应的管理系统、方法、设备及存储介质
CN114911494A (zh) * 2022-06-06 2022-08-16 北京百度网讯科技有限公司 用于分布式系统的应用部署方法、装置、电子设备和介质
CN115396437B (zh) * 2022-08-24 2023-06-13 中电金信软件有限公司 一种集群搭建方法、装置、电子设备及存储介质
CN116185984A (zh) * 2022-12-08 2023-05-30 金篆信科有限责任公司 分布式数据库部署方法、装置、电子设备及可读存储介质
CN115904627A (zh) * 2022-12-14 2023-04-04 平安银行股份有限公司 Kubernetes集群部署方法及其系统、计算机设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105393220A (zh) * 2013-05-15 2016-03-09 思杰系统有限公司 用于在集群系统中部署点状虚拟服务器的系统和方法
CN106850621A (zh) * 2017-02-07 2017-06-13 南京云创大数据科技股份有限公司 一种基于容器云技术快速搭建Hadoop集群的方法
US20170346683A1 (en) * 2016-05-24 2017-11-30 Futurewei Technologies, Inc. Automated Generation of Deployment Workflows for Cloud Platforms Based on Logical Stacks
CN107426034A (zh) * 2017-08-18 2017-12-01 国网山东省电力公司信息通信公司 一种基于云平台的大规模容器调度系统及方法

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107645396B (zh) * 2016-07-21 2020-11-13 北京金山云网络技术有限公司 一种集群扩容方法及装置
CN106506233A (zh) * 2016-12-01 2017-03-15 郑州云海信息技术有限公司 一种自动部署Hadoop集群及伸缩工作节点的方法
CN107766157A (zh) * 2017-11-02 2018-03-06 山东浪潮云服务信息科技有限公司 基于国产cpu和os的分布式容器集群框架实现方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105393220A (zh) * 2013-05-15 2016-03-09 思杰系统有限公司 用于在集群系统中部署点状虚拟服务器的系统和方法
US20170346683A1 (en) * 2016-05-24 2017-11-30 Futurewei Technologies, Inc. Automated Generation of Deployment Workflows for Cloud Platforms Based on Logical Stacks
CN106850621A (zh) * 2017-02-07 2017-06-13 南京云创大数据科技股份有限公司 一种基于容器云技术快速搭建Hadoop集群的方法
CN107426034A (zh) * 2017-08-18 2017-12-01 国网山东省电力公司信息通信公司 一种基于云平台的大规模容器调度系统及方法

Cited By (45)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111193783A (zh) * 2019-12-19 2020-05-22 新浪网技术(中国)有限公司 一种服务访问的处理方法及装置
CN113360160A (zh) * 2020-03-05 2021-09-07 北京沃东天骏信息技术有限公司 部署应用的方法、装置、电子设备和存储介质
CN111930466A (zh) * 2020-05-28 2020-11-13 武汉达梦数据库有限公司 一种基于Kubernetes的数据同步环境部署方法和装置
CN111651275A (zh) * 2020-06-04 2020-09-11 山东汇贸电子口岸有限公司 一种MySQL集群自动化部署系统及方法
CN111782766A (zh) * 2020-06-30 2020-10-16 福建健康之路信息技术有限公司 一种通过关键字检索Kubernetes集群中所有资源的方法和系统
CN114006815B (zh) * 2020-07-13 2024-01-26 中移(苏州)软件技术有限公司 云平台节点的自动化部署方法、装置、节点及存储介质
CN114006815A (zh) * 2020-07-13 2022-02-01 中移(苏州)软件技术有限公司 云平台节点的自动化部署方法、装置、节点及存储介质
CN113965582B (zh) * 2020-07-20 2024-04-09 中移(苏州)软件技术有限公司 一种模式转换方法和系统，及存储介质
CN113965582A (zh) * 2020-07-20 2022-01-21 中移(苏州)软件技术有限公司 一种模式转换方法和系统，及存储介质
US12026561B2 (en) 2020-08-27 2024-07-02 Cisco Technology, Inc. Dynamic authentication and authorization of a containerized process
CN112099911A (zh) * 2020-08-28 2020-12-18 中国—东盟信息港股份有限公司 一种基于Kubernetes构建动态资源准入控制器的方法
CN112099911B (zh) * 2020-08-28 2024-02-13 中国—东盟信息港股份有限公司 一种基于Kubernetes构建动态资源准入控制器的方法
CN114138590A (zh) * 2020-09-03 2022-03-04 中国移动通信集团湖南有限公司 Kubernetes集群的运维处理方法、装置及电子设备
CN112148429A (zh) * 2020-09-22 2020-12-29 江苏银承网络科技股份有限公司 用于管理容器编排引擎集群的信息处理方法及装置
CN112148429B (zh) * 2020-09-22 2024-05-28 江苏银承网络科技股份有限公司 用于管理容器编排引擎集群的信息处理方法及装置
CN114760292B (zh) * 2020-12-25 2023-07-21 广东飞企互联科技股份有限公司 一种面向服务发现与注册的方法及装置
CN114760292A (zh) * 2020-12-25 2022-07-15 广东飞企互联科技股份有限公司 一种面向服务发现与注册的方法及装置
CN114697985A (zh) * 2020-12-28 2022-07-01 中国联合网络通信集团有限公司 无线运维系统注册方法、装置、电子设备及存储介质
CN113110917B (zh) * 2021-04-28 2024-03-15 北京链道科技有限公司 基于Kubernetes的数据发现和安全访问方法
CN113110917A (zh) * 2021-04-28 2021-07-13 北京链道科技有限公司 基于Kubernetes的数据发现和安全访问方法
CN113190239B (zh) * 2021-05-20 2024-05-24 洛阳轴承研究所有限公司 一种工业应用快速部署的方法
CN113190239A (zh) * 2021-05-20 2021-07-30 洛阳轴承研究所有限公司 一种工业应用快速部署的方法
CN113377346A (zh) * 2021-06-10 2021-09-10 北京滴普科技有限公司 集成环境搭建方法、装置、电子设备及存储介质
CN115525416A (zh) * 2021-06-24 2022-12-27 中移(苏州)软件技术有限公司 管理方法、相关设备和存储介质
CN113778331A (zh) * 2021-08-12 2021-12-10 联想凌拓科技有限公司 一种数据处理方法、主节点及存储介质
CN113778331B (zh) * 2021-08-12 2024-06-07 联想凌拓科技有限公司 一种数据处理方法、主节点及存储介质
US20230060053A1 (en) * 2021-08-20 2023-02-23 Beijing Baidu Netcom Science Technology Co., Ltd. Method and apparatus of deploying a cluster, and storage medium
CN113849159A (zh) * 2021-09-18 2021-12-28 浪潮电子信息产业股份有限公司 源代码跨架构的同步构建方法、装置、设备及存储介质
CN113886146A (zh) * 2021-10-22 2022-01-04 郑州云海信息技术有限公司 一种异常处理方法、装置、设备及计算机可读存储介质
CN114124903A (zh) * 2021-11-15 2022-03-01 新华三大数据技术有限公司 一种虚ip地址管理方法及装置
CN114116909A (zh) * 2021-12-01 2022-03-01 敏博科技(武汉)有限公司 一种分布式云原生数据库管理方法和系统
CN114138754A (zh) * 2021-12-09 2022-03-04 安超云软件有限公司 基于Kubernetes平台的软件部署方法及装置
CN114884880A (zh) * 2022-04-06 2022-08-09 阿里巴巴（中国）有限公司 数据传输方法以及系统
CN114884880B (zh) * 2022-04-06 2024-03-08 阿里巴巴（中国）有限公司 数据传输方法以及系统
WO2023193671A1 (fr) * 2022-04-06 2023-10-12 阿里巴巴（中国）有限公司 Procédé et système de transmission de données
CN115981675A (zh) * 2022-12-06 2023-04-18 浪潮云信息技术股份公司 一种快速部署Kubernetes集群的方法及系统
CN116016545A (zh) * 2022-12-26 2023-04-25 上海浦东发展银行股份有限公司 Redis集群高可用的部署方法、装置、设备及存储介质
CN116009897A (zh) * 2022-12-28 2023-04-25 广东亿迅科技有限公司 一种多架构harbor-operator的集成与部署方法、系统、设备及存储介质
CN116244271A (zh) * 2022-12-29 2023-06-09 金篆信科有限责任公司 分布式数据库的部署方法、装置、电子设备及可读介质
CN116233274A (zh) * 2023-02-09 2023-06-06 京东科技信息技术有限公司 一种信息处理方法及装置、存储介质
WO2025013032A1 (fr) * 2023-07-12 2025-01-16 Jio Platforms Limited Procédé et système d'automatisation d'un déploiement d'orchestration de conteneurs
EP4521250A1 (fr) * 2023-08-29 2025-03-12 Beijing Volcano Engine Technology Co., Ltd. Procédé et appareil de gestion de grappe, dispositif électronique et support de stockage
CN117857343A (zh) * 2023-12-14 2024-04-09 天翼云科技有限公司 一种自动化更新Kubernetes调度器的方法
CN118573558A (zh) * 2024-06-14 2024-08-30 中国科学院空天信息创新研究院 云边系统的部署装置及方法
CN120162200A (zh) * 2025-05-20 2025-06-17 深圳市飞泉云数据服务有限公司 集群服务器调度方法、装置、设备及介质

Also Published As

Publication number Publication date
CN108549580B (zh) 2023-04-14
CN108549580A (zh) 2018-09-18

Similar Documents

Publication Publication Date Title
WO2019184164A1 (fr) Procédé de déploiement automatique de nœud travailleur de kubernetes, dispositif, appareil terminal et support de stockage lisible
WO2019184116A1 (fr) Procédé et dispositif de construction automatique de nœud principal de kubernetes, dispositif terminal et support de stockage lisible par ordinateur
US10735329B2 (en) Container communication method and system for parallel applications
US10700947B2 (en) Life cycle management method and device for network service
CN104734931B (zh) 一种虚拟网络功能间链路建立方法及装置
CN106375101B (zh) 一种生命周期管理方法及装置
US10353728B2 (en) Method, system and device for managing virtual machine software in cloud environment
CN113315754B (zh) 容器出访防火墙智能联动方法及装置、设备、介质
US11444785B2 (en) Establishment of trusted communication with container-based services
CN106134141A (zh) 一种更新网络服务描述器nsd的方法及装置
CN113923023A (zh) 权限配置和数据处理的方法、装置、电子设备及介质
CN111245634A (zh) 一种虚拟化管理方法及装置
CN115604120B (zh) 一种多云集群资源共享方法、装置、设备及存储介质
WO2017185992A1 (fr) Procédé et appareil permettant de transmettre un message de requête
CN110855488B (zh) 一种虚拟机接入方法及装置
CN110890987A (zh) 自动创建集群的方法、装置、设备和系统
CN105162667B (zh) 虚拟机配置方法和装置
CN106126283A (zh) 一种产品部署的方法、装置及系统
CN111338926A (zh) 补丁的测试方法、装置及电子设备
CN104484221A (zh) CloudStack接管vCenter已有集群的方法
JP7581390B2 (ja) プロバイダネットワークサービス拡張
US12517767B2 (en) Managing events for services of a cloud platform in a hybrid cloud environment
WO2022063121A1 (fr) Procédé et dispositif d'intercommunication de réseau basés sur un réseau privé, et groupe d'ordinateurs
CN113297158A (zh) 一种云安全产品管理方法、装置、设备及存储介质
CN120915798B (zh) 服务器信息采集、更新方法与装置、系统、介质、产品及设备

Legal Events

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

Ref document number: 18911681

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 18911681

Country of ref document: EP

Kind code of ref document: A1