CN111324417B - Component control method and device of Kubernetes cluster, electronic equipment and medium - Google Patents
Component control method and device of Kubernetes cluster, electronic equipment and medium Download PDFInfo
- Publication number
- CN111324417B CN111324417B CN202010062862.2A CN202010062862A CN111324417B CN 111324417 B CN111324417 B CN 111324417B CN 202010062862 A CN202010062862 A CN 202010062862A CN 111324417 B CN111324417 B CN 111324417B
- Authority
- CN
- China
- Prior art keywords
- component object
- component
- cluster
- deployed
- updated
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 87
- 230000008859 change Effects 0.000 claims description 22
- 230000015654 memory Effects 0.000 claims description 19
- 238000012217 deletion Methods 0.000 claims description 9
- 230000037430 deletion Effects 0.000 claims description 9
- 230000004048 modification Effects 0.000 claims description 9
- 238000012986 modification Methods 0.000 claims description 9
- 238000012544 monitoring process Methods 0.000 claims description 5
- 230000008901 benefit Effects 0.000 description 12
- 238000010586 diagram Methods 0.000 description 12
- 230000003993 interaction Effects 0.000 description 11
- 230000006870 function Effects 0.000 description 10
- 230000008439 repair process Effects 0.000 description 7
- 238000012545 processing Methods 0.000 description 6
- 238000004891 communication Methods 0.000 description 4
- 238000004590 computer program Methods 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 230000011664 signaling Effects 0.000 description 4
- 230000000007 visual effect Effects 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 239000004973 liquid crystal related substance Substances 0.000 description 2
- 230000001413 cellular effect Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000008602 contraction Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 239000002071 nanotube Substances 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000001151 other effect Effects 0.000 description 1
- 230000001953 sensory effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
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/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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- 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/45562—Creating, deleting, cloning virtual machine instances
-
- 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/45595—Network integration; Enabling network access in virtual machine instances
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the application discloses a method, a device, electronic equipment and a medium for controlling components of a Kubernetes cluster, and relates to the technical field of cloud computing. The specific implementation scheme is as follows: determining deployed component object information on a cluster, and reporting the component object information to a cloud platform to instruct the cloud platform to determine whether a component object to be updated exists in the deployed component object according to the component object information; and if the component object to be updated issued by the cloud platform is received, updating the component object to be updated. By the technical scheme of the embodiment of the application, the complexity of the Kubernetes cluster component management can be reduced.
Description
Technical Field
The present disclosure relates to computer technologies, and in particular, to a method, an apparatus, an electronic device, and a medium for controlling components of Kubernetes clusters.
Background
Kubernetes is an open-source container application cluster management service, provides a series of complete functions such as deployment operation, resource scheduling, service discovery, dynamic expansion and contraction and the like for containerized applications on the basis of a Docker technology, and improves the convenience of large-scale container clusters. In general, a user may implement a cluster event reporting function by installing a component in a Kubernetes cluster to extend a cluster function, such as an Exporter component of a hundred degree cloud CNAP product. Where a component is a collection of dependency Kubernetes Resource, typically including Deployment, service, serviceAccount, configMap, clusterRole and ClusterRoleBinding, etc.
However, when the cloud platform nanotubes have a large number of Kubernetes clusters, and various components are installed in the clusters, maintenance, such as repair, of the components becomes difficult, and the cloud platform is required to traverse all the clusters to locate and repair the components, which is a complicated process.
Disclosure of Invention
The embodiment of the application provides a method, a device, electronic equipment and a medium for controlling components of a Kubernetes cluster, so as to reduce the complexity of the management of the components of the Kubernetes cluster.
In a first aspect, an embodiment of the present application discloses a method for controlling a component of a Kubernetes cluster, which is performed by the Kubernetes cluster, where the method includes:
determining deployed component object information on a cluster, and reporting the component object information to a cloud platform to instruct the cloud platform to determine whether a component object to be updated exists in the deployed component object according to the component object information;
and if the component object to be updated issued by the cloud platform is received, updating the component object to be updated.
One embodiment of the above application has the following advantages or benefits: and the Kubernetes cluster actively reports the information of the deployed component object on the cluster to the cloud platform, so that the cloud platform determines whether the deployed component object has the component object to be updated according to the component object information, and issues the component object to be updated to the Kubernetes cluster when determining that the component object to be updated exists, and then the Kubernetes cluster updates the object to be updated if receiving the component object to be updated issued by the cloud platform, so as to realize the restoration of the deployed component in the cluster. Compared with the existing method for repairing the deployed components of the clusters, the method for repairing the deployed components of the clusters by adopting the interaction between the active mode of the Kubernetes clusters and the cloud platform reduces the complexity of repairing the components of the Kubernetes clusters.
Optionally, the method further comprises:
and if a component object creation request issued by the cloud platform is received, storing the component object information to be created in the component object creation request, and deploying resources for the component object to be created.
The above alternatives have the following advantages or benefits: the cloud platform encapsulates the resources into the form of the component objects, and issues a component object creation request to the Kubernetes cluster, so that the Kubernetes cluster automatically deploys the resources included in the component objects to be created according to the component object creation request issued by the cloud platform, and the resource deployment efficiency is improved.
Optionally, the method further comprises:
if any resource change event is monitored, determining a component object to which the resource belongs; wherein the change event is a delete event or a modify event;
consistency comparison is carried out on the original resources of the determined component objects and the resources of the component objects deployed in the cluster;
if not, restoring the resource.
The above alternatives have the following advantages or benefits: the Kubernetes cluster can automatically monitor deletion or modification of any deployed resource on the cluster and restore the resource, thereby ensuring that the deployed components in the cluster can realize expected functions.
In a second aspect, an embodiment of the present application discloses a method for controlling a component of a Kubernetes cluster, which is executed by a cloud platform, where the method includes:
receiving deployed component object information on a cluster reported by the cluster;
determining whether a component object to be updated exists in the deployed component object according to the component object information;
and if so, issuing the component object to be updated to the cluster.
One embodiment of the above application has the following advantages or benefits: the method comprises the steps that the information of the deployed component object on the cluster is actively reported to a cloud platform through a Kubernetes cluster, the cloud platform determines whether the deployed component object has a component object to be updated according to the component object information, and when the fact that the component object to be updated exists is determined, the component object to be updated is issued to the Kubernetes cluster, so that the Kubernetes cluster updates the object to be updated when receiving the component object to be updated issued by the cloud platform, and further repair of the deployed component in the cluster is achieved. Compared with the existing method for repairing the deployed components of the clusters, the method for repairing the deployed components of the clusters by adopting the interaction between the active mode of the Kubernetes clusters and the cloud platform reduces the complexity of repairing the components of the Kubernetes clusters.
Optionally, the component object information includes a name and a hash value of the component object.
Optionally, determining whether the component object to be updated exists in the deployed component object according to the component object information includes:
positioning a locally stored association component template according to the name of the component object, and determining a hash value of the association component template;
and determining whether a component object to be updated exists in the deployed component object according to a comparison result of the hash value of the associated component template and the hash value of the component object.
The above alternatives have the following advantages or benefits: the cloud platform can quickly determine whether the deployed component object in the Kubernetes cluster has a component to be updated or not by comparing the hash value of the locally stored associated component template with the hash value of the component object reported by the Kubernetes cluster, and an optional mode is provided for the cloud platform to determine whether the deployed component object in the Kubernetes cluster has the component to be updated or not.
In a third aspect, an embodiment of the present application discloses a device for controlling a component of a Kubernetes cluster, configured in the Kubernetes cluster, where the device includes:
The object information reporting module is used for determining the deployed component object information on the cluster and reporting the component object information to the cloud platform so as to instruct the cloud platform to determine whether a component object to be updated exists in the deployed component object according to the component object information;
and the object updating module is used for updating the component object to be updated if the component object to be updated issued by the cloud platform is received.
In a fourth aspect, an embodiment of the present application discloses a device for controlling a component of a Kubernetes cluster, configured in a cloud platform, where the device includes:
the object information receiving module is used for receiving the deployed component object information on the cluster reported by the cluster;
the to-be-updated object determining module is used for determining whether the to-be-updated component object exists in the deployed component object according to the component object information;
and the object to be updated issuing module is used for issuing the component object to be updated to the cluster if the object to be updated exists.
In a fifth aspect, embodiments of the present application further disclose an electronic device, including:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform a method of controlling components of a Kubernetes cluster as described in any of the embodiments of the present application.
In a sixth aspect, embodiments of the present application also disclose a non-transitory computer readable storage medium storing computer instructions for causing the computer to perform a method of controlling components of a Kubernetes cluster according to any embodiment of the present application.
One embodiment of the above application has the following advantages or benefits: and the Kubernetes cluster actively reports the information of the deployed component object on the cluster to the cloud platform, so that the cloud platform determines whether the deployed component object has the component object to be updated according to the component object information, and issues the component object to be updated to the Kubernetes cluster when determining that the component object to be updated exists, and then the Kubernetes cluster updates the object to be updated if receiving the component object to be updated issued by the cloud platform, so as to realize the restoration of the deployed component in the cluster. Compared with the existing method for repairing the deployed components of the clusters, the method for repairing the deployed components of the clusters by adopting the interaction between the active mode of the Kubernetes clusters and the cloud platform reduces the complexity of repairing the components of the Kubernetes clusters.
Other effects of the above alternative will be described below in connection with specific embodiments.
Drawings
The drawings are for better understanding of the present solution and do not constitute a limitation of the present application. Wherein:
fig. 1 is a flowchart of a method for controlling components of a Kubernetes cluster according to a first embodiment of the present application;
fig. 2A is a flowchart of a method for controlling components of a Kubernetes cluster according to a second embodiment of the present application;
fig. 2B is a signaling diagram of component control of a Kubernetes cluster according to a second embodiment of the present application;
fig. 3 is a flowchart of a method for controlling components of a Kubernetes cluster according to a third embodiment of the present application;
fig. 4A is a block diagram of a component control of a Kubernetes cluster according to a fourth embodiment of the present application;
fig. 4B is a signaling diagram of component control of a Kubernetes cluster according to a fourth embodiment of the present application;
fig. 5 is a schematic structural diagram of a component control device of a Kubernetes cluster according to a fifth embodiment of the present application;
fig. 6 is a schematic structural diagram of a component control device of a Kubernetes cluster according to a sixth embodiment of the present application;
fig. 7 is a block diagram of an electronic device used to implement a method of component control of Kubernetes clusters of an embodiment of the present application.
Detailed Description
Exemplary embodiments of the present application are described below in conjunction with the accompanying drawings, which include various details of the embodiments of the present application to facilitate understanding, and should be considered as merely exemplary. Accordingly, one of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present application. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
First embodiment
Fig. 1 is a flowchart of a method for controlling components of a Kubernetes cluster according to a first embodiment of the present application, where the present embodiment may be applicable to a case of how to manage components of a Kubernetes cluster. The whole set of the component control method of the Kubernetes cluster can be cooperatively executed by the cloud platform and the Kubernetes cluster. The solution of the present embodiment may be performed by Kubernetes clusters, and further by component controllers in Kubernetes clusters that are dedicated to managing components. The method can be executed by a component control device of the Kubernetes cluster, and the device can be realized in a software and/or hardware mode and can be integrated on the Kubernetes cluster, in particular can be integrated on a component controller in the Kubernetes cluster. As shown in fig. 1, the method for controlling components of the Kubernetes cluster provided in this embodiment may include:
S110, determining the deployed component object information on the cluster, and reporting the component object information to the cloud platform to instruct the cloud platform to determine whether the component object to be updated exists in the deployed component object according to the component object information.
In this embodiment, on the basis of the Kubernetes CRD (Customer Resource Definition, user-defined resource) mechanism, a new CRD, that is, a component object, is extended to describe the component, that is, the component is encapsulated by the component object (or the resource is encapsulated by the component object). Alternatively, a component may be described by a component object, where the component object's meta-annotation (i.e., meta-section) records the entire description of the component, including, but not limited to, type, version, hash value, etc.; the object field (i.e., spec. Objects field) of the component object contains a complete definition of all Kubernetes Resource components, etc.
Component object information is issued by the cloud platform and may include, but is not limited to, the name and hash value of the component object. The hash value of the component object is determined by the cloud platform, and specifically can be determined by the cloud platform according to a component template associated with the component object. Alternatively, for each component supported by the cloud platform, the component object may be defined on the cloud platform and stored in YAML format, referred to as a component template. All the component templates are stored in a setting catalog in the cloud platform, and when any component template is updated, the corresponding component template in the setting catalog can be replaced by a new component template. It will be appreciated that the resources included in any component change (e.g., add, delete, modify, etc.), and that the component templates for that component will change, i.e., update.
When a user requests the cloud platform to deploy the specified component object into the specified Kubernetes cluster, the cloud platform can locate a locally stored component template associated with the specified component object according to the name of the component object specified by the user and calculate the hash value of the component template; and generating a corresponding component object according to the component template, taking the hash value of the component template as the hash value of the component object, and then the cloud platform can send the component object, the name of the component object and the hash value to a designated Kubernetes cluster together so that the Kubernetes cluster deploys the component object, deploys resources included in the component object and stores the hash value, the name and the like of the component object. That is, if the Kubernetes cluster receives the component object creation request issued by the cloud platform, the information of the component object to be created in the component object creation request can be stored, and resources are deployed for the component object to be created.
To facilitate querying, the Kubernetes cluster may optionally create a component object list, i.e., store all component object information that has been deployed in the cluster in list form. Further, the component object list is stored in the core control module of the Kubernetes cluster, i.e., kubernetes Master, where Kubernetes Master is the automation control center for all resources in the Kubernetes cluster. Further, if the component controller in the Kubernetes cluster receives the component object creation request issued by the cloud platform, the component object creation request may be sent to Kubernetes Master, so that Kubernetes Master stores the information of the component object to be created in the component object list, and at the same time, creates the component object to be created in the Kubernetes cluster and deploys resources for the component object to be created.
Specifically, the component controllers in the Kubernetes cluster can query the component object list in the Kubernetes cluster at regular time to acquire the deployed component object information on the cluster, and report the component object information to the cloud platform; and determining whether the component object to be updated exists in the deployed component objects or not by the cloud platform according to the component object information. For example, the cloud platform can locate a locally stored associated component template according to the name of the component object reported by the component controller in the Kubernetes cluster, and calculate the hash value of the associated component template; then, consistency comparison is carried out on the hash value of the associated component template and the hash value of the component object reported by the component controller in the Kubernetes cluster; if the two components are consistent, determining that the component object to be updated does not exist in the deployed component objects on the Kubernetes cluster; if the two components are inconsistent, determining that the component object to be updated exists in the deployed component objects on the Kubernetes cluster.
And S120, if the component object to be updated issued by the cloud platform is received, updating the component object to be updated.
Optionally, if the cloud platform determines that the component object to be updated exists in the deployed component objects on the Kubernetes cluster, the component object to be updated may be generated according to a component template associated with the component object to be updated, and the component object to be updated is issued to the Kubernetes cluster. Further, a component controller in the Kubernetes cluster receives a component object to be updated issued by the cloud platform, and updates the component object to be updated. In particular, the component object to be updated is used for replacing the deployed corresponding component object on the cluster, and one or more resources included in the corresponding component object can be updated.
For example, if the hash value of the deployed component object a on the Kubernetes cluster is inconsistent with the hash value determined by the associated component template of the component object a stored in the cloud platform, it is stated that the cloud platform updates the associated component template of the component object a after the Kubernetes cluster deploys the component object a, that is, the deployed component object a on the Kubernetes cluster has a component object to be updated. At this time, the cloud platform may generate the component object to be updated according to the associated component template of the component object a, that is, the component template associated with the component object to be updated, and issue the component object to be updated to the Kubernetes cluster. Further, the component controllers in the Kubernetes cluster receive the component object to be updated issued by the cloud platform, replace the deployed component object a with the component object to be updated, and update one or more resources and the like included in the deployed component object a.
In addition, the cloud platform can also send the name and the hash value of the component object to be updated to the Kubernetes cluster, and further the component controller in the Kubernetes cluster can also update the component object information list according to the name and the hash value of the component object to be updated.
It should be noted that, when a component deployed in a certain Kubernetes cluster has a Bug, that is, when a user needs to repair, that is, update, any resource of the component deployed in the certain Kubernetes cluster, the cloud platform is required to first traverse all clusters to locate the cluster in which the component is deployed and the component has the Bug, and then repair the cluster. The user can update the template file in the cloud platform at any time according to actual demands, and then the Kubernetes cluster actively interacts with the cloud platform to repair, namely update, the deployed components in the cluster, so that the complexity of repairing the deployed components in the Kubernetes cluster can be reduced, and the repair efficiency of the deployed components in the Kubernetes cluster is improved.
According to the technical scheme provided by the embodiment of the application, the Kubernetes cluster actively reports the deployed component object information on the cluster to the cloud platform, so that the cloud platform can determine whether the deployed component object has the component object to be updated according to the component object information, and when the component object to be updated is determined to exist, the component object to be updated is issued to the Kubernetes cluster, and further if the Kubernetes cluster receives the component object to be updated issued by the cloud platform, the component object to be updated is updated, so that the restoration of the deployed component in the cluster is realized. Compared with the existing method for repairing the deployed components of the clusters, the method for repairing the deployed components of the clusters by adopting the interaction between the active mode of the Kubernetes clusters and the cloud platform reduces the complexity of repairing the components of the Kubernetes clusters.
Second embodiment
Fig. 2A is a flowchart of a method for controlling components of a Kubernetes cluster according to the second embodiment of the present application, and fig. 2B is a signaling diagram of controlling components of a Kubernetes cluster according to the second embodiment of the present application. Based on the above embodiments, the specific operation process of the Kubernetes cluster is added when the deployed resources in the Kubernetes cluster are changed, such as deleted or modified. As shown in fig. 2A and 2B, the method for controlling components of the Kubernetes cluster provided in this embodiment may include:
S210, determining the deployed component object information on the cluster, and reporting the component object information to the cloud platform to instruct the cloud platform to determine whether a component object to be updated exists in the deployed component object according to the component object information.
And S220, if the component object to be updated issued by the cloud platform is received, updating the component object to be updated.
S230, if any resource change event is monitored, determining the component object to which the resource belongs.
In this embodiment, the event of changing the resource may be an event triggered by deleting or modifying any resource deployed in the Kubernetes cluster by a user, and may be a deletion event of the resource or a modification event of the resource. It will be appreciated that after a component object is defined, the functionality of the component described by the component object is determined, and if a user deletes or modifies any resource included in the component object, the component described by the component object may not be able to perform the intended function. In the embodiment, through the Kubernetes cluster, the component controller in the Kubernetes cluster further monitors the change of the deployed resources in the cluster in real time and performs corresponding processing, so that the deployed components in the cluster can be ensured to realize expected functions.
Alternatively, a component controller in the Kubernetes cluster may implement monitoring the change events of the resource by interacting with a Master in the Kubernetes cluster. In connection with fig. 2B, for example, if a user deletes any of the resources already deployed in the Kubernetes cluster, kubernetes Master will generate a deletion event of the resource, and send the deletion event of the resource to the component controller in the Kubernetes cluster, so that the component controller monitors the deletion event of the resource; the component controller may then determine, based on the home field (i.e., the ownerrreference field) of the resource, whether and to which component object the resource belongs. Optionally, if the ownerrreference field of the resource is empty, it indicates that the resource does not belong to any component object, no processing may be performed at this time, or a resource recreating event corresponding to the deletion event of the resource and including prompt information such as "the resource will not normally run" may be generated and sent to Kubernetes Master, so that Kubernetes Master presents the prompt information in the form of a visual interface, and the resource is redeployed in the Kubernetes cluster when the user clicks the recreating button on the visual interface.
If the ownerrreference field of the resource is not null, the component object to which the resource belongs may be determined according to the specific content of the ownerrreference field.
S240, the original resources of the determined component objects are compared with all the resources of the deployed component objects in the cluster in a consistent manner.
In this embodiment, the determined original resources of the component object include all the resources defined in the object field (i.e., spec. Objects field) of the component object.
With continued reference to fig. 2B, in particular, after determining the component object to which the resource belongs, the component controller in the Kubernetes cluster may query Kubernetes Master for the original resource of the determined component object; the determined original resources of the component object may then be compared for consistency with all of the resources of the component object that have been deployed in the cluster at that time.
S250, if the resources are inconsistent, recovering the resources.
Alternatively, if they do not agree, it is indicated that the deleted resource does belong to the component object, and at this time, the resource may be recreated according to the complete definition of the deleted resource in the object field (i.e., spec. Objects field) of the component object.
In addition, if the user modifies any of the resources already deployed in the Kubernetes cluster, the component controller in the Kubernetes cluster will monitor the modification event of the resource, then execute the processes of S230 and S240, and determine that the modified resource actually belongs to the component object if there is inconsistency in the comparison result, at this time, the resource may be corrected according to the complete definition of the modified resource in the object field (i.e., spec. Objects field) of the component object, and the modified resource is restored.
It should be noted that, the processing procedure of the resource change in the embodiments S230 to S250 and the processing procedure of the component object update in the embodiments S210 to S220 may be performed independently, and the embodiment provides only a preferred example and is not limited thereto.
According to the technical scheme provided by the embodiment of the application, the Kubernetes cluster can automatically monitor deletion or modification of any deployed resource on the cluster and restore the resource, so that the deployed components in the cluster can realize expected functions.
Third embodiment
Fig. 3 is a flowchart of a method for controlling components of a Kubernetes cluster according to a third embodiment of the present application, where the present embodiment may be applicable to a case of how to manage components of a Kubernetes cluster. The whole set of the component control method of the Kubernetes cluster can be cooperatively executed by the cloud platform and the Kubernetes cluster. The solution of the present embodiment may be executed by a cloud platform. The method can be executed by a component control device of the Kubernetes cluster, and the device can be realized in a software and/or hardware mode and can be integrated on a cloud platform. As shown in fig. 3, the method for controlling components of the Kubernetes cluster provided in this embodiment may include:
S310, receiving the deployed component object information on the cluster reported by the cluster.
In this embodiment, the component object information may include, but is not limited to, a name and a hash value of the component object. Optionally, the hash value of the component object may be determined by the cloud platform according to a component template associated with the component object when the component object is deployed to the Kubernetes cluster for the first time; alternatively, the hash value of the component object may also be determined by the cloud platform based on the updated component template associated with the component object when updating the deployed component object in the Kubernetes cluster.
Specifically, the component controllers in the Kubernetes cluster can query the component object list in the Kubernetes cluster at regular time to acquire the deployed component object information on the cluster, and report the component object information to the cloud platform; and the cloud platform can receive the component object information which is reported by the Kubernetes cluster and is deployed on the cluster.
S320, determining whether the component object to be updated exists in the deployed component objects according to the component object information.
Optionally, each time the cloud platform issues component object information to the Kubernetes cluster, the association relationship between the component object information, the component template and the component template creation timestamp may be stored synchronously. Because the user can update the component templates stored on the cloud platform at any time according to actual demands, in order to lighten the storage burden of the cloud platform, when any component template is updated, the corresponding component template in the setting catalog of the cloud platform, namely the old component template, can be replaced by the new component template, but the follow-up tracing is convenient, and the cloud platform can also store the association relation between the version number of the new component template and the version number of the old component template. Alternatively, the version number of the component template may be composed of a random number, a component template creation time stamp, and the like.
Further, after the cloud platform receives the component object information which is reported by the Kubernetes cluster and is deployed on the cluster, the cloud platform can determine the component template creation time stamp associated with the component object information according to the component object information and the association relationship among the locally stored component object information, the component template and the component template creation time stamp; then, a timestamp can be created according to the component template, and the association relation between the version number of the new component template and the version number of the old component template can be used for determining whether the deployed component object on the Kubernetes cluster corresponding to the component object information has the new component template or not; if yes, determining that the component object to be updated exists in the deployed component objects on the Kubernetes cluster.
Further, determining whether the component object to be updated exists in the deployed component object according to the component object information may be: positioning a locally stored association component template according to the name of the component object, and determining a hash value of the association component template; and determining whether the component object to be updated exists in the deployed component object according to a comparison result of the hash value of the associated component template and the hash value of the component object. The associated component template is a component template associated with the component object and stored in the cloud platform.
Specifically, the cloud platform can locate a locally stored associated component template according to the name of the component object reported by the Kubernetes cluster, and calculate the hash value of the associated component template; then, consistency comparison is carried out on the hash value of the associated component template and the hash value of the component object reported by the Kubernetes cluster; if the two components are consistent, determining that the component object to be updated does not exist in the deployed component objects on the Kubernetes cluster; if the two components are inconsistent, determining that the component object to be updated exists in the deployed component objects on the Kubernetes cluster.
S330, if the component object exists, the component object to be updated is issued to the cluster.
Specifically, if the cloud platform determines that the component object to be updated exists in the deployed component objects on the Kubernetes cluster, the component object to be updated can be generated according to the component template associated with the component object to be updated, and the component object to be updated is issued to the Kubernetes cluster. The Kubernetes cluster is used for receiving the component object to be updated issued by the cloud platform and updating the component object to be updated.
In addition, the cloud platform can also issue the name and the hash value of the component object to be updated to the Kubernetes cluster, so that the Kubernetes cluster can update the component object information list according to the name and the hash value of the component object to be updated.
According to the technical scheme provided by the embodiment of the application, the information of the deployed component object on the cluster is actively reported to the cloud platform through the Kubernetes cluster, the cloud platform determines whether the deployed component object has the component object to be updated according to the information of the component object, and when the component object to be updated is determined to exist, the component object to be updated is issued to the Kubernetes cluster, so that the Kubernetes cluster updates the object to be updated when receiving the component object to be updated issued by the cloud platform, and further the restoration of the deployed component in the cluster is realized. Compared with the existing method for repairing the deployed components of the clusters, the method for repairing the deployed components of the clusters by adopting the interaction between the active mode of the Kubernetes clusters and the cloud platform reduces the complexity of repairing the components of the Kubernetes clusters.
In addition, the cloud platform can issue the component object to the Kubernetes cluster according to the deployment requirement of the user so that the Kubernetes cluster deploys the component object. For example, if the cloud platform receives the component object deployment request, the cloud platform determines component object information to be deployed in the component object deployment request, and issues a component object creation request including the component object information to be deployed to the cluster. The component object deployment request may include, among other things, a name of the component object specified by the user, an identification of the Kubernetes cluster specified, and the like.
Specifically, when a user needs to deploy a specified component object to a specified Kubernetes cluster by a cloud platform, a component object deployment request can be sent to the cloud platform, the cloud platform further receives the component object deployment request sent by the user, locates a locally stored component template associated with the specified component object according to the name of the component object specified by the user, and calculates a hash value of the component template; and generating a corresponding component object according to the component template, taking the hash value of the component template as the hash value of the component object, and then the cloud platform can issue a component object creation request comprising the component object, the name of the component object and the hash value to the Kubernetes cluster, so that the Kubernetes cluster deploys the component object, deploys resources included in the component object, and stores the hash value, the name and the like of the component object.
Fourth embodiment
Fig. 4A is a block diagram of a component control of a Kubernetes cluster according to a fourth embodiment of the present application, and fig. 4B is a signaling diagram of a component control of a Kubernetes cluster according to a fourth embodiment of the present application, where a preferred example is provided based on the foregoing embodiment. The whole set of the component control method of the Kubernetes cluster can be cooperatively executed by a cloud platform, a component controller in the Kubernetes cluster and a core control module of the Kubernetes cluster, namely Kubernetes Master. As shown in fig. 4A and 4B, the method for controlling the components of the Kubernetes cluster provided in this embodiment may specifically be:
The component controllers in the Kubernetes cluster can query the component object list in the Kubernetes cluster from Kubernetes Master at regular time to acquire the component object information deployed on the Kubernetes cluster, and report the component object information to the cloud platform.
The cloud platform can locate a locally stored associated component template according to the name of the component object reported by the component controller in the Kubernetes cluster, and calculate the hash value of the associated component template; then, consistency comparison is carried out on the hash value of the associated component template and the hash value of the component object reported by the component controller in the Kubernetes cluster; if the two components are consistent, determining that the component object to be updated does not exist in the deployed component objects on the Kubernetes cluster; if the two components are inconsistent, determining that the component object to be updated exists in the deployed component objects on the Kubernetes cluster.
The cloud platform can generate the component object to be updated according to the component template associated with the component object to be updated and issue the component object to be updated to the Kubernetes cluster if the component object to be updated exists in the deployed component objects on the Kubernetes cluster.
The component controllers in the Kubernetes cluster receive the component objects to be updated issued by the cloud platform, replace the corresponding component objects deployed on the cluster with the component objects to be updated, and can update one or more resources included in the corresponding component objects.
According to the technical scheme provided by the embodiment of the application, the Kubernetes cluster actively reports the deployed component object information on the cluster to the cloud platform, so that the cloud platform can determine whether the deployed component object has the component object to be updated according to the component object information, and when the component object to be updated is determined to exist, the component object to be updated is issued to the Kubernetes cluster, and further if the Kubernetes cluster receives the component object to be updated issued by the cloud platform, the component object to be updated is updated, so that the restoration of the deployed component in the cluster is realized. Compared with the existing method for repairing the deployed components of the clusters, the method for repairing the deployed components of the clusters by adopting the interaction between the active mode of the Kubernetes clusters and the cloud platform reduces the complexity of repairing the components of the Kubernetes clusters.
Fifth embodiment
Fig. 5 is a schematic structural diagram of a device for controlling components of a Kubernetes cluster according to a fifth embodiment of the present application, where the device may be configured on the Kubernetes cluster, and in particular, may be configured on a component controller in the Kubernetes cluster. The device can execute the component control method of the Kubernetes cluster provided by the first embodiment and the second embodiment of the application, and has the corresponding functional modules and beneficial effects of the execution method. As shown in fig. 5, the apparatus may include:
The object information reporting module 510 is configured to determine deployed component object information on the cluster, and report the component object information to the cloud platform, so as to instruct the cloud platform to determine whether a component object to be updated exists in the deployed component object according to the component object information;
the object updating module 520 is configured to update the component object to be updated if the component object to be updated issued by the cloud platform is received.
According to the technical scheme provided by the embodiment of the application, the Kubernetes cluster actively reports the deployed component object information on the cluster to the cloud platform, so that the cloud platform can determine whether the deployed component object has the component object to be updated according to the component object information, and when the component object to be updated is determined to exist, the component object to be updated is issued to the Kubernetes cluster, and further if the Kubernetes cluster receives the component object to be updated issued by the cloud platform, the component object to be updated is updated, so that the restoration of the deployed component in the cluster is realized. Compared with the existing method for repairing the deployed components of the clusters, the method for repairing the deployed components of the clusters by adopting the interaction between the active mode of the Kubernetes clusters and the cloud platform reduces the complexity of repairing the components of the Kubernetes clusters.
Illustratively, the component object information includes a name and hash value of the component object.
Illustratively, the apparatus may further include:
and the object creation request execution module is used for storing the to-be-created component object information in the component object creation request and deploying resources for the to-be-created component object if the component object creation request issued by the cloud platform is received.
Illustratively, the apparatus may further include:
the object determining module is used for determining the component object to which the resource belongs if the change event of any resource is monitored; wherein the change event is a delete event or a modify event;
the resource comparison module is used for comparing the original resources of the determined component objects with the resources of the deployed component objects in the cluster in a consistent manner;
and the restoration module is used for restoring the resource if the resources are inconsistent.
Illustratively, the restoration module may be specifically configured to:
if the change event is a deletion event, the resource is re-created;
if the change event is a modification event, the resource is corrected.
Sixth embodiment
Fig. 6 is a schematic structural diagram of a device for controlling components of a Kubernetes cluster according to a sixth embodiment of the present application, where the device may be configured on a cloud platform. The device can execute the component control method of the Kubernetes cluster provided by the third embodiment of the application, and has the corresponding functional modules and beneficial effects of the execution method. As shown in fig. 6, the apparatus may include:
The object information receiving module 610 is configured to receive component object information deployed on a cluster reported by the cluster;
the to-be-updated object determining module 620 is configured to determine whether a component object to be updated exists in the deployed component objects according to the component object information;
and the object to be updated issuing module 630 is configured to issue the component object to be updated to the cluster if the component object to be updated exists.
According to the technical scheme provided by the embodiment of the application, the information of the deployed component object on the cluster is actively reported to the cloud platform through the Kubernetes cluster, the cloud platform determines whether the deployed component object has the component object to be updated according to the information of the component object, and when the component object to be updated is determined to exist, the component object to be updated is issued to the Kubernetes cluster, so that the Kubernetes cluster updates the object to be updated when receiving the component object to be updated issued by the cloud platform, and further the restoration of the deployed component in the cluster is realized. Compared with the existing method for repairing the deployed components of the clusters, the method for repairing the deployed components of the clusters by adopting the interaction between the active mode of the Kubernetes clusters and the cloud platform reduces the complexity of repairing the components of the Kubernetes clusters.
Illustratively, the component object information includes a name and hash value of the component object.
By way of example, the object to be updated determination module 620 may be specifically configured to:
positioning a locally stored association component template according to the name of the component object, and determining a hash value of the association component template;
and determining whether the component object to be updated exists in the deployed component object according to a comparison result of the hash value of the associated component template and the hash value of the component object.
Illustratively, the apparatus may further include:
the object deployment request execution module is used for determining the to-be-deployed component object information in the component object deployment request if the component object deployment request is received, and issuing a component object creation request comprising the to-be-deployed component object information to the cluster.
According to embodiments of the present application, an electronic device and a readable storage medium are also provided.
As shown in fig. 7, a block diagram of an electronic device of a component control method of Kubernetes cluster according to an embodiment of the present application. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the application described and/or claimed herein.
As shown in fig. 7, the electronic device includes: one or more processors 701, memory 702, and interfaces for connecting the various components, including high-speed interfaces and low-speed interfaces. The various components are interconnected using different buses and may be mounted on a common motherboard or in other manners as desired. The processor may process instructions executing within the electronic device, including instructions stored in or on memory to display graphical information of a graphical user interface (Graphical User Interface, GUI) on an external input/output device, such as a display device coupled to the interface. In other embodiments, multiple processors and/or multiple buses may be used, if desired, along with multiple memories and multiple memories. Also, multiple electronic devices may be connected, each providing a portion of the necessary operations, e.g., as a server array, a set of blade servers, or a multiprocessor system. One processor 701 is illustrated in fig. 7.
Memory 702 is a non-transitory computer-readable storage medium provided herein. The memory stores instructions executable by the at least one processor to cause the at least one processor to perform the method for controlling components of the Kubernetes cluster provided herein. The non-transitory computer readable storage medium of the present application stores computer instructions for causing a computer to perform the component control method of Kubernetes cluster provided herein.
The memory 702 is used as a non-transitory computer readable storage medium, and can be used to store a non-transitory software program, a non-transitory computer executable program, and a module, such as program instructions/modules corresponding to the component control method of the Kubernetes cluster in the embodiment of the present application, for example, the component object information reporting module 510 and the component object updating module 520 shown in fig. 5; alternatively, the component object information receiving module 610, the component object to be updated determining module 620, and the component object to be updated issuing module 630 shown in fig. 6. The processor 701 executes various functional applications of the server and data processing, namely, implements the component control method of the Kubernetes cluster in the above-described method embodiment by running non-transitory software programs, instructions, and modules stored in the memory 702.
Memory 702 may include a storage program area that may store an operating system, at least one application program required for functionality, and a storage data area; the storage data area may store data created according to the use of an electronic device used to implement the component control method of the Kubernetes cluster, and the like. In addition, the memory 702 may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory 702 optionally includes memory remotely located with respect to processor 701, which may be connected via a network to the electronics used to implement the component control method of the Kubernetes cluster. Examples of such networks include, but are not limited to, the internet, intranets, blockchain networks, local area networks, mobile communication networks, and combinations thereof.
The electronic device used to implement the component control method of the Kubernetes cluster may further include: an input device 703 and an output device 704. The processor 701, the memory 702, the input device 703 and the output device 704 may be connected by a bus or otherwise, in fig. 7 by way of example.
The input device 703 may receive input numeric or character information and generate key signal inputs related to user settings and function control of an electronic device used to implement the Kubernetes cluster component control method, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, a pointer stick, one or more mouse buttons, a track ball, a joystick, and the like. The output device 704 may include a display apparatus, an auxiliary lighting device such as a light emitting diode (Light Emitting Diode, LED), a haptic feedback device such as a vibration motor, and the like. The display device may include, but is not limited to, a liquid crystal display (Liquid Crystal Display, LCD), an LED display, and a plasma display. In some implementations, the display device may be a touch screen.
Various implementations of the systems and techniques described here can be implemented in digital electronic circuitry, integrated circuitry, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs, the one or more computer programs may be executed and/or interpreted on a programmable system including at least one programmable processor, which may be a special purpose or general-purpose programmable processor, that may receive data and instructions from, and transmit data and instructions to, a storage system, at least one input device, and at least one output device.
These computing programs are also referred to as programs, software applications, or code, including machine instructions of a programmable processor, and may be implemented in a high-level procedural and/or object-oriented programming language, and/or in assembly/machine language. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and/or device for providing machine instructions and/or data to a programmable processor, e.g., magnetic discs, optical disks, memory, programmable logic devices (Programmable Logic Device, PLD), including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal used to provide machine instructions and/or data to a programmable processor.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device for displaying information to a user, for example, a Cathode Ray Tube (CRT) or an LCD monitor; and a keyboard and pointing device, such as a mouse or trackball, by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user may be any form of sensory feedback such as visual feedback, auditory feedback, or tactile feedback; and input from the user may be received in any form, including acoustic input, speech input, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes background components, e.g., as a data server; or in a computing system including middleware components, such as an application server; or in a computing system that includes a front-end component, such as a user computer having a graphical user interface or web browser through which a user can interact with embodiments of the systems and techniques described here, or in a computing system that includes such a back-end component, middleware component, or any combination of front-end components. The components of the system may be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include: local area network (Local Area Network, LAN), wide area network (Wide Area Network, WAN) and blockchain networks, the internet.
The computer system may include a client and a server. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
According to the technical scheme of the embodiment of the application, the Kubernetes cluster actively reports the information of the deployed component object on the cluster to the cloud platform, so that the cloud platform determines whether the deployed component object has the component object to be updated according to the component object information, and when the component object to be updated is determined to exist, the Kubernetes cluster transmits the component object to be updated, and further if the Kubernetes cluster receives the component object to be updated transmitted by the cloud platform, the component object to be updated is updated, so that the restoration of the deployed component in the cluster is realized. Compared with the existing method for repairing the deployed components of the clusters, the method for repairing the deployed components of the clusters by adopting the interaction between the active mode of the Kubernetes clusters and the cloud platform reduces the complexity of repairing the components of the Kubernetes clusters.
It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps described in the present application may be performed in parallel, sequentially, or in a different order, provided that the desired results of the technical solutions disclosed in the present application can be achieved, and are not limited herein.
The above embodiments do not limit the scope of the application. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives are possible, depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present application are intended to be included within the scope of the present application.
Claims (10)
1. A method of controlling a component of a Kubernetes cluster, the method performed by the Kubernetes cluster, the method comprising:
determining deployed component object information on a cluster, and reporting the component object information to a cloud platform to instruct the cloud platform to determine whether a component object to be updated exists in the deployed component object according to the component object information; wherein the component object information includes a name and a hash value of the component object; the hash value is determined by the cloud platform according to the component template associated with the component object;
if the cloud platform is received to issue the component object to be updated, updating the component object to be updated, and monitoring the change of the deployed resources in the cluster in real time;
if any resource change event is monitored, judging whether the attribution field of the resource is empty or not; wherein the change event is a delete event or a modify event;
if the attribution field of the resource is not empty, determining the component object to which the resource belongs;
consistency comparison is carried out on the original resources of the determined component objects and the resources of the component objects deployed in the cluster;
if not, restoring the resource.
2. The method according to claim 1, wherein the method further comprises:
and if a component object creation request issued by the cloud platform is received, storing the component object information to be created in the component object creation request, and deploying resources for the component object to be created.
3. The method of claim 1, wherein recovering the resource comprises:
if the change event is a deletion event, the resource is re-created;
and if the change event is a modification event, correcting the resource.
4. A method for controlling components of a Kubernetes cluster, performed by a cloud platform, the method comprising:
receiving deployed component object information on a cluster reported by the cluster; the component object information comprises the name and hash value of the component object; the hash value is determined by the cloud platform according to the component template associated with the component object;
determining whether a component object to be updated exists in the deployed component object according to the component object information;
if so, issuing the component object to be updated to the cluster so that the cluster updates the component object to be updated, and monitoring the change of the deployed resources in the cluster in real time to ensure the consistency of the deployed resources and the original resources; wherein the deployed resources are updated correspondingly with the updating of the deployed component object.
5. The method of claim 4, wherein determining whether there is a component object to be updated in the deployed component objects based on the component object information comprises:
positioning a locally stored association component template according to the name of the component object, and determining a hash value of the association component template;
and determining whether a component object to be updated exists in the deployed component object according to a comparison result of the hash value of the associated component template and the hash value of the component object.
6. The method according to claim 4, wherein the method further comprises:
if a component object deployment request is received, determining component object information to be deployed in the component object deployment request, and issuing a component object creation request comprising the component object information to be deployed to the cluster.
7. A device for controlling components of a Kubernetes cluster, configured in the Kubernetes cluster, the device comprising:
the object information reporting module is used for determining the deployed component object information on the cluster and reporting the component object information to the cloud platform so as to instruct the cloud platform to determine whether a component object to be updated exists in the deployed component object according to the component object information; wherein the component object information includes a name and a hash value of the component object; the hash value is determined by the cloud platform according to the component template associated with the component object;
The object updating module is used for updating the component object to be updated if the component object to be updated issued by the cloud platform is received, and monitoring the change of the deployed resources in the cluster in real time;
the object updating module is specifically configured to:
if any resource change event is monitored, judging whether the attribution field of the resource is empty or not; wherein the change event is a delete event or a modify event;
if not, determining the component object to which the resource belongs;
consistency comparison is carried out on the original resources of the determined component objects and the resources of the component objects deployed in the cluster;
if not, restoring the resource.
8. A device for controlling components of a Kubernetes cluster, configured in a cloud platform, the device comprising:
the object information receiving module is used for receiving the deployed component object information on the cluster reported by the cluster; the component object information comprises a name and a hash value of a component object; the hash value is determined by the cloud platform according to the component template associated with the component object;
the to-be-updated object determining module is used for determining whether the to-be-updated component object exists in the deployed component object according to the component object information;
And the object to be updated issuing module is used for issuing the component object to be updated to the cluster if the object to be updated exists, so that the cluster updates the component object to be updated, and monitoring the change of the deployed resources in the cluster in real time.
9. An electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of controlling components of the Kubernetes cluster of any one of claims 1-3 or the method of controlling components of the Kubernetes cluster of any one of claims 4-6.
10. A non-transitory computer-readable storage medium storing computer instructions for causing the computer to perform the method of controlling components of the Kubernetes cluster of any of claims 1-3 or the method of controlling components of the Kubernetes cluster of any of claims 4-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010062862.2A CN111324417B (en) | 2020-01-19 | 2020-01-19 | Component control method and device of Kubernetes cluster, electronic equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010062862.2A CN111324417B (en) | 2020-01-19 | 2020-01-19 | Component control method and device of Kubernetes cluster, electronic equipment and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111324417A CN111324417A (en) | 2020-06-23 |
| CN111324417B true CN111324417B (en) | 2024-03-08 |
Family
ID=71171000
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010062862.2A Active CN111324417B (en) | 2020-01-19 | 2020-01-19 | Component control method and device of Kubernetes cluster, electronic equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111324417B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112019385B (en) * | 2020-08-28 | 2022-11-25 | 北京浪潮数据技术有限公司 | Cloud platform component deleting method, device, equipment and storage medium |
| CN112346816A (en) * | 2020-09-01 | 2021-02-09 | 北京京东尚科信息技术有限公司 | Cloud platform updating method and device |
| CN112306626B (en) * | 2020-09-01 | 2024-04-05 | 北京京东尚科信息技术有限公司 | Method and device for updating cloud platform |
| CN112083971B (en) * | 2020-09-15 | 2023-04-11 | 北京凌云雀科技有限公司 | Component processing method, device and storage medium |
| CN112199256A (en) * | 2020-10-16 | 2021-01-08 | 济南浪潮数据技术有限公司 | Deployment event monitoring method, device and equipment |
| CN112269640B (en) * | 2020-11-02 | 2023-03-28 | 浪潮云信息技术股份公司 | Method for realizing life cycle management of container cloud component |
| CN112395048B (en) * | 2020-11-27 | 2022-04-29 | 恒生电子股份有限公司 | Component management method and device and electronic equipment |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108874503A (en) * | 2018-06-05 | 2018-11-23 | 国云科技股份有限公司 | A kind of Configuration Agent update method of cloud platform application cluster |
| CN109067828A (en) * | 2018-06-22 | 2018-12-21 | 杭州才云科技有限公司 | Based on the more cluster construction methods of Kubernetes and OpenStack container cloud platform, medium, equipment |
| CN109656686A (en) * | 2018-12-17 | 2019-04-19 | 武汉烽火信息集成技术有限公司 | The upper deployment container cloud method of OpenStack, storage medium, electronic equipment and system |
| KR101998564B1 (en) * | 2018-07-19 | 2019-07-10 | 나무기술 주식회사 | Multi-cluster provisioning and managing method on cloud platform |
| CN110262899A (en) * | 2019-06-20 | 2019-09-20 | 无锡华云数据技术服务有限公司 | Monitor component elastic telescopic method, apparatus and controlled terminal based on Kubernetes cluster |
| CN110413287A (en) * | 2019-07-31 | 2019-11-05 | 北京百度网讯科技有限公司 | The dispositions method and device of software |
-
2020
- 2020-01-19 CN CN202010062862.2A patent/CN111324417B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108874503A (en) * | 2018-06-05 | 2018-11-23 | 国云科技股份有限公司 | A kind of Configuration Agent update method of cloud platform application cluster |
| CN109067828A (en) * | 2018-06-22 | 2018-12-21 | 杭州才云科技有限公司 | Based on the more cluster construction methods of Kubernetes and OpenStack container cloud platform, medium, equipment |
| KR101998564B1 (en) * | 2018-07-19 | 2019-07-10 | 나무기술 주식회사 | Multi-cluster provisioning and managing method on cloud platform |
| CN109656686A (en) * | 2018-12-17 | 2019-04-19 | 武汉烽火信息集成技术有限公司 | The upper deployment container cloud method of OpenStack, storage medium, electronic equipment and system |
| CN110262899A (en) * | 2019-06-20 | 2019-09-20 | 无锡华云数据技术服务有限公司 | Monitor component elastic telescopic method, apparatus and controlled terminal based on Kubernetes cluster |
| CN110413287A (en) * | 2019-07-31 | 2019-11-05 | 北京百度网讯科技有限公司 | The dispositions method and device of software |
Non-Patent Citations (3)
| Title |
|---|
| Elastic Scheduling Strategy for Private Cloud Resource Based on Kubernetes and Openstack;Ke-Ying, Zhang , et al;《Computer Technology and Development》;第29卷(第2期);第109-114页 * |
| 中国搜索Kubernetes应用平台部署方案;邵珂 等;《中国传媒科技》(第5期);第113-117页 * |
| 基于OpenStack和Kubernetes的双向部署技术研究;杜磊;《电脑知识与技术》;第16卷(第1期);第10-12页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111324417A (en) | 2020-06-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111324417B (en) | Component control method and device of Kubernetes cluster, electronic equipment and medium | |
| CN111258609B (en) | Upgrading method and device of Kubernetes cluster, electronic equipment and medium | |
| US20210232498A1 (en) | Method for testing edge computing, device, and readable storage medium | |
| CN113396393A (en) | Dynamic auto-configuration of multi-tenant PAAS components | |
| CN111770169A (en) | Method, device, equipment and storage medium for upgrading equipment firmware | |
| CN111966651B (en) | Data synchronization method, device, electronic equipment and storage medium | |
| US20140019429A1 (en) | Downtime reduction for lifecycle management events | |
| EP3462315A2 (en) | Systems and methods for service mapping | |
| CN111694857B (en) | Method, device, electronic equipment and computer readable medium for storing resource data | |
| CN111930521A (en) | Method and device for deploying application, electronic equipment and readable storage medium | |
| CN110995480B (en) | Block chain network deployment method, device, electronic equipment and medium | |
| CN111290768B (en) | Updating method, device, equipment and medium of containerized application system | |
| US11709853B2 (en) | Database-based management method, platform, electronic device and storage medium | |
| CN103118100A (en) | Guarantee method and guarantee system for improving usability of virtual machine application | |
| US11010238B2 (en) | Management system of storage system | |
| CN112035220A (en) | Processing method, device and equipment for operation task of development machine and storage medium | |
| CN111506401A (en) | Automatic driving simulation task scheduling method and device, electronic equipment and storage medium | |
| CN114721686A (en) | Configuration data updating method and device, electronic equipment and storage medium | |
| CN111782341A (en) | Method and apparatus for managing clusters | |
| US20230153290A1 (en) | Method for monitoring running state of distributed system, device, and storage medium | |
| CN111782357B (en) | Label control method and device, electronic equipment and readable storage medium | |
| CN111125451B (en) | Data production processing method and device, electronic equipment and storage medium | |
| US20200192763A1 (en) | Methods, apparatuses and systems for cloud-based disaster recovery | |
| CN112148447B (en) | Task processing method and system based on risk control and electronic equipment | |
| Ross et al. | SAP NetWeaver BI Accelerator |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |