CN109831500A - The synchronous method of configuration file and Pod in Kubernetes cluster - Google Patents
The synchronous method of configuration file and Pod in Kubernetes cluster Download PDFInfo
- Publication number
- CN109831500A CN109831500A CN201910089488.2A CN201910089488A CN109831500A CN 109831500 A CN109831500 A CN 109831500A CN 201910089488 A CN201910089488 A CN 201910089488A CN 109831500 A CN109831500 A CN 109831500A
- Authority
- CN
- China
- Prior art keywords
- configuration file
- pod
- simultaneously operating
- synchronous method
- monitor
- 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.)
- Granted
Links
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Present invention discloses the synchronous method of configuration file and Pod in a kind of Kubernetes cluster, comprising the following steps: is configured to monitor the whether changed monitor of configuration file corresponding to Pod；Triggering Pod is set and configuration file executes the initial trigger variable of simultaneously operating；The snoop results of configuration file are synchronized to API Server by monitor；Kubelet component simultaneously operating between the configuration file and Pod of the built-in label selector upper version that is not to wait for current configuration file whether complete, and the current configuration file is injected into Pod, to complete the simultaneously operating between Pod and current configuration file, and restore initial trigger variable.Through the invention, reduce simultaneously operating frequently invalid between Pod and configuration file, reasonable and real-time simultaneously operating is carried out to realize configuration file and Pod in Kubernetes cluster, the high availability that Kubernetes cluster can be taken into account while the loss of Kubernetes clustering performance is being reduced to the greatest extent, to improve user experience significantly.
Description
Technical field
The present invention relates to configuration file in field of cloud computer technology more particularly to a kind of Kubernetes cluster and Pod
Synchronous method.
Background technique
Kubernetes is initially derived from the Borg inside Google, provides application oriented container clustered deploy(ment) and management system
System.The target of Kubernetes is intended to eliminate the calculating of layout physical/virtual, the burden of network and storage infrastructure, and makes to answer
It is focused on completely with program operators and developer and carries out self-service operation on the primitive centered on container.
Kubernetes also provide stablize, compatible basis (platform), for construct the workflows of customization and more advanced automatic
Change task.Kubernetes has perfect cluster management ability, including multi-level security protection and mechanism of permitting the entrance, multi-tenant
Using enabling capabilities, transparent service registration and service discovery mechanisms, built-in load balanced device, fault discovery and self-regeneration energy
Power, service rolling upgrade and on-line rapid estimation, expansible resource Automatic dispatching mechanism, the resource quota managerial ability of more granularities.
Kubernetes also provides perfect management tool, covers the links such as exploitation, deployment test, O&M monitoring.
In Kubernetes cluster, Pod is the basis of all types of service, it is the combination of one or more containers.
The shared storage of these containers, network and NameSpace, and the specification how to run.In Pod, all containers are all by same peace
Row and scheduling, and operate in shared context.For concrete application, Pod is their Logical HEA, and Pod includes
The relevant multiple application containers (Container) of business.
(hereinafter referred to as based on computer cluster constructed by KubernetesKubernetes cluster) in, when some calculating
Node (including one or more Pod in calculate node) needs maintenance or business integration or original node load excessively high
When, it is necessary to the Pod in the calculate node is migrated into other calculate nodes；In addition, the project of kubernetes cluster is held
Sequel automates in the scenes such as building deployment (CICD) process example at (gitlab+harbor+Jenkins) to be needed to configuration text
Part is updated.Must be synchronous with Pod holding when being updated to configuration file, it is unavailable otherwise to will lead to Pod, to lead
It causes to be formed by application based on Pod or service provides top service.Meanwhile if being according to setting time, such as with ten seconds
If synchronizing cycle synchronizes operation to Pod and configuration, then can greatly it influence based on calculating constructed by Kubernetes
The system performance of machine cluster seriously causes to reduce user experience.
Summary of the invention
It is an object of the invention to disclose the synchronous method of configuration file and Pod in a kind of Kubernetes cluster, with reality
Configuration file and Pod carry out reasonable and real-time synchronized update operation in existing Kubernetes cluster, are reducing to the greatest extent
Kubernetes clustering performance takes into account the high availability of Kubernetes cluster while loss, to improve user experience.
To achieve the above object, present invention discloses configuration file sides synchronous with Pod's in a kind of Kubernetes cluster
Method, comprising the following steps:
It is configured to monitor the whether changed monitor of configuration file corresponding to Pod；
Triggering Pod is set and configuration file executes the initial trigger variable of simultaneously operating；
The snoop results of configuration file are synchronized to API Server by monitor；
Kubelet component built-in label selector be not to wait for current configuration file a upper version configuration file
Whether the simultaneously operating between Pod is completed, and the current configuration file is injected into Pod, to complete Pod and currently match
The simultaneously operating between file is set, and restores initial trigger variable.
As a further improvement of the present invention, the monitor is at least formed in ETCD component.
As a further improvement of the present invention, further includes: judge current configuration file whether the configuration with a upper version
File changes；
If so, the current configuration file is injected into Pod, to execute Pod by Kubelet component and be currently configured
Simultaneously operating between file；
If it is not, the configuration file of a upper version is injected into Pod, to execute Pod and upper one by Kubelet component
Simultaneously operating between the configuration file of a version.
As a further improvement of the present invention, the label selector is formed by label by Pod and search value is selected
Pod。
As a further improvement of the present invention, it after the simultaneously operating between Pod and configuration file is finished, also wraps
It includes:
Judge current configuration file corresponding to Pod whether and ETCD component in saved corresponding with the Pod match
File is set to match；
If so, determining that the simultaneously operating between configuration file and Pod is completed；
If it is not, then determining that the simultaneously operating between configuration file and Pod does not complete.
As a further improvement of the present invention, the initial trigger variable of the configuration file is set as FALSE, and only when
When the triggering variable of configuration file is TRUE, the simultaneously operating of Pod and configuration file are executed by Kubelet component.
As a further improvement of the present invention, after completing simultaneously operating between Pod and configuration file, further includes:
The initial trigger variable of configuration file is re-set as FALSE.
As a further improvement of the present invention, further includes: sent out when in the configuration file that monitor listens in ETCD component
When changing, the instruction for stopping to execute configuration file and Pod execution simultaneously operating is issued from monitor to Kubelet component, with
Current configuration file is injected into Pod by API Server.
As a further improvement of the present invention, further includes: by Pod send simultaneously operating record and synchronized result save to
In the log system of Pod coupling.
As a further improvement of the present invention, the configuration file is described jointly by ConfigMap and Secret.
Compared with prior art, the beneficial effects of the present invention are: in the present invention, Kubelet component built-in label
Whether the simultaneously operating that selector is not to wait between the configuration file and Pod of a upper version for current configuration file is completed, and
The current configuration file is injected into Pod, to complete the simultaneously operating between Pod and current configuration file, reduces Pod
The simultaneously operating frequently invalid between configuration file carries out to realize configuration file and Pod in Kubernetes cluster
Reasonable and real-time simultaneously operating can take into account Kubernetes while reducing the loss of Kubernetes clustering performance to the greatest extent
The high availability of cluster, to improve user experience significantly.
Detailed description of the invention
Fig. 1 is the Kubenetes cluster of the synchronous method of configuration file and Pod in operation Kubenetes cluster of the present invention
Architecture diagram；
Fig. 2 is the overall flow figure of the synchronous method of configuration file and Pod in Kubernetes cluster of the present invention.
Specific embodiment
The present invention is described in detail for each embodiment shown in reference to the accompanying drawing, but it should be stated that, these
Embodiment is not limitation of the present invention, those of ordinary skill in the art according to these embodiments made by function, method,
Or equivalent transformation or substitution in structure, all belong to the scope of protection of the present invention within.
Embodiment one:
It please join one of the synchronous method of configuration file and Pod in Fig. 1 and Kubenetes cluster of the present invention illustrated in fig. 2
Kind specific embodiment.
In the present embodiment, Kubenetes cluster is made of host node 10 with from node 20, multiple to constitute one from node 20
A slave node pool for being controlled by host node 10.ETCD component 104, APIServer101, controller 103 and scheduler 102 are disposed
In host node 10.The association of host node 10 is matched from node 20 to from the slave node (Node) 20 for forming one or more Pod
Kubelet component 201 and multiple Pod are set, it is exemplary in the present embodiment to show Pod202, Pod203 and Pod204.
ETCD component 104 is used to save the status information of Kubenetes cluster all network configurations and object, and consistent based on RAFT
Property algorithm realizes the consistency of each node or Pod state in Kubenetes cluster.
It include multiple Node (node) that each Node is made of one or more Pod from node 20.Node is
The workload node of Kubernetes cluster, host node 10 share out the work for it, when some Node delay machine, 10 meeting of host node
Its workload is automatically transferred to other nodes.For example, by the workload dynamic migration of Pod202 to Pod203 or
Pod204.Pod202~Pod204, can be by being located in each Node as the minimum unit dispatched in Kubernetes cluster
Set kube-proxy is responsible for the realization of service.External network (Internet) is accessed by firewall (Firewalls)
Kube-proxy, to be carried out by kube-proxy to one or more Pod in some node (being located at from node 20)
It accesses, and realizes service discovery and load balancing in the node by kube-proxy.
Scheduler 102 is connect by communication link 112 with API Server101, and is responsible for the scheduling of resource, and according to pre-
Pod is dispatched most user and provided on the machine (Machine) of service by fixed resource dispatching strategy.In the present embodiment, term
" resource " refer to based on be formed by Kubenetes cluster by Pod the computing resource that service can be provided for user, storage money
Source or Internet resources.Term " machine " can be virtual machine, and being also possible to physical machine can also be computer cluster or operation
There are server or the data center of Kubenetes cluster.
Controller 103 is connect by data link 113 with API Server101, and is responsible for maintenance Kubenetes cluster
State, such as is carried out by fault detection, automatic extension, rolls update by Pod etc..API Server101 is provided to resource operation
Sole inlet, and provide the mechanism such as certification, authorization, access control, API registration and discovery.Kubelet component 201 is responsible for dimension
The life cycle management of container (Container) is protected, and is responsible for Volume (CIS) and network (CNI) management.Kubelet component
201 are deployed in from node 20 and all Pod or node of pipe of receiving.
Meanwhile log system 21 is also deployed in from node 20 in the present embodiment.It is multiple to be formed from node 20 from node
Pond, and it is controlled by host node 10.
Next, how applicant realizes the specific of simultaneously operating with Pod to the configuration file in Kubernetes cluster
Realization process is illustrated.Meanwhile for the ease of statement, in the present embodiment, applicant with from node 20 Pod202 with
The configuration file saved in ETCD component 104 in host node 10 carries out executing simultaneously operating when Pod202 is changed
Specific implementation process is described.In the present embodiment, " change " that so-called Pod202 occurs includes, but are not limited to pair
The operation of creation performed by Pod202, modification operation, migration operation, delete operation, reboot operation, shutoff operation, pausing operation
Or opening operation etc..Pod202 may make to have upward business configuration file 100 and the Pod202 simultaneously operating executed
Real-time enabling capabilities.
In the present embodiment, in the Kubernetes cluster configuration file and Pod synchronous method, comprising the following steps:
It is configured to monitor the whether changed monitor 114 of configuration file 100 corresponding to Pod202.Monitor
114 can be configured to have and monitor acquired in configuration file 100 and API Server201 from Kubelet component 201 to being located at
Whether the configuration parameter that the ETCD component 104 on upper layer passes through obtained Pod202 during synchronous Pod202 is changed
Monitor process.
By may be with the configuration that is saved in ETCD component 104 from configuration file corresponding to the Pod202 in node 20
File there are nonsynchronous situation, so if Pod202 with its belonging to configuration file 100 it is asynchronous, then will lead to Pod202
It cannot respond to the request of user, to severely impact the performance and availability of Kubernetes cluster.In the present embodiment, should
Monitor 114 is formed in ETCD component 104.User can modify to configuration file 100 by API Server201.
Configuration file 100 is described jointly by ConfigMap115 and Secret116；Wherein, Secret116 is by password, order
The configuration datas such as board (Token), code key composition, and independently of image file perhaps Pod202 and can be with book or ring
The form of border variable is carried out mode and is used.ConfigMap115 is used to store the resource object of Kubernetes, can be used for that Pod is arranged
Context variable values, the information such as store path, Tag of command line parameter set in Container212, Pod202；Phase
For Secret116, ConfigMap115 can handle the character string not comprising sensitive information more conveniently.
As shown in connection with fig. 2, in the present embodiment, setting triggering Pod202 and configuration file 100 execute the first of simultaneously operating
Beginning triggering variable.Specifically, in the present embodiment, which is set as FALSE.Then monitor 114 is run.With
Family can operate resource by the API Server101, the operation, that is, described above " creation operation, is moved at modification operation
Move operation, delete operation, reboot operation, shutoff operation, pausing operation or opening operation etc. ".These operations will lead to specified
" change " occurs for configuration file 100 corresponding to Pod, decided whether in subsequent implementation procedure to Pod and configuration text
Part 100 synchronizes operation.When configuration file generation is not changed, execution step is jumped: operation monitor 114；It is literary when preparing
When part changes, modification triggering variable is TRUE.Then, whether it is that TRUE judges to modified triggering variable, if
It is then to start to execute the simultaneously operating between configuration file and Pod, if not, then it represents that do not need to hold between configuration file and Pod
Row simultaneously operating.After the simultaneously operating between row configuration file and Pod finishes, resetting initial trigger variable is
FALSE executes process shown in Fig. 2 with traversal.
The snoop results of configuration file 100 are synchronized to API Server201 by monitor 114.Wherein, Kubelet component
201 built-in label selector 211 be not to wait between the configuration file and Pod202 of a upper version of current configuration file
Simultaneously operating whether complete, and the current configuration file is injected into Pod, with complete Pod and current configuration file it
Between simultaneously operating, and restore initial trigger variable.It should be noted that " current configuration file " described above and " upper one
The configuration file of a version " with configuration file corresponding to Pod202 because Pod202 occur " change " scene in be two not
With configuration file, " current configuration file " described above and " configuration file of a upper version " with corresponding to Pod202
Configuration file do not occur to be two identical configuration files in the scene " changed " because of Pod202.
By the technical solution, so that working as configuration file 100 corresponding to Pod202 occurs invalid change, such as user will
Some is revised as " 321 " by " 123 " from the access password of the Pod in node 20, then in next second or shorter period
It is interior and password is revised as " 123 " from " 321 ".In this scene, if the configuration file 100 for frequently modifying the Pod,
It will lead to simultaneously operating frequently invalid between Pod and configuration file 100.
It is saved in ETCD component 104 simultaneously as being listened to by the monitor 114 being located in ETCD component 104
Whether configuration file 100 changes, and using the current configuration file to be injected into Pod202, with complete Pod202 with
Simultaneously operating this technological means between current configuration file reduces between Pod and configuration file frequently invalid synchronous
Operation.
Especially, compared with the existing technology in setting fixed simultaneously operating period synchronization policy, in the present embodiment,
By Kubelet component 201 built-in label selector 211 be not to wait for current configuration file a upper version configuration text
Whether the simultaneously operating between part and Pod202 is completed, and the current configuration file is injected into Pod, with complete Pod with
This strategy or method of simultaneously operating between current configuration file, had both reached between Pod202 and configuration file 100
Simultaneously operating, and can reduce significantly fixed simultaneously operating policy mechanism is set between configuration file 100 and Pod202
Stiff property greatly reduced to significantly reduce simultaneously operating frequent and invalid between configuration file 100 and Pod202
The scheduling of resource consumption of Kubernetes cluster, improves Kubernetes cluster and the high availability and stabilization of Pod202
Property.
Preferably, in the present embodiment, the synchronous method further include: judge current configuration file 100 whether with upper one
The configuration file of version changes；If so, the current configuration file is injected into Pod202, to pass through Kubelet group
Part 201 executes the simultaneously operating between Pod202 and current configuration file；If it is not, the configuration file of a upper version is injected into
In Pod202, to execute the simultaneously operating between Pod202 and the configuration file of a upper version by Kubelet component 201.
Label selector 211 is formed by label (that is, Tag) by Pod202 and selectes corresponding Pod with search, so that specifically
Pod can be selected from multiple Pod in node 20 from this.
After the simultaneously operating between Pod202 and configuration file 100 is finished, further includes: judge that Pod202 institute is right
The current configuration file 100 answered whether and ETCD component 104 in 100 phase of configuration file corresponding with the Pod202 that is saved
Matching；If so, determining that the simultaneously operating between configuration file 100 and Pod202 is completed；If it is not, then determining configuration file
Simultaneously operating between 100 and Pod202 does not complete.As for judging whether that matched foundation can be based on the ginseng in YAML file
Comparison of the number in computer processes, is also possible to pass through data in the database (not shown) that ETCD component 104 is configured
Library index operation is realized, is also possible to hold based on visual code on the computer of user or administrator with visual means
Pedestrian's work compares.
The initial trigger variable of configuration file 100 is set as FALSE, and only when the triggering variable of configuration file 100 is
When TRUE, the simultaneously operating of Pod202 and configuration file 100 are executed by Kubelet component 201.Meanwhile as Pod202 and configuration
After completing simultaneously operating between file 100, further includes: the initial trigger variable of configuration file 100 is re-set as FALSE.
When changing in the configuration file 100 that monitor 114 listens in ETCD component 104, from monitor 114 to
Kubelet component 201 issues the instruction for stopping to execute configuration file 100 and Pod202 execution simultaneously operating, to pass through API
Current configuration file is injected into Pod by Server101.Meanwhile by Pod202 send simultaneously operating record and synchronized result
It saves into the log system 21 coupled with Pod202, in order to which the simultaneously operating that Pod202 occurs for the later period records and synchronizes
As a result it is recorded and is inquired.
To sum up, as shown in connection with fig. 2, configuration file and Pod in a kind of revealed Kubernetes cluster of the present embodiment
In synchronous method, if executed in synchronizing process in Pod and configuration file, which has occurred primary or multiple update
Perhaps change then without waiting for it is last perhaps on simultaneously operating several times whether complete and to be not to wait for this primary or more
Whether secondary simultaneously operating is completed, and directly the current configuration file is injected into Pod, to complete Pod and be currently configured text
Simultaneously operating between part, and restore initial trigger variable, thus reduce because in synchronizing process because in Kubernetes cluster
Network failure caused by synchronization delay the problem of.
Embodiment two:
The synchronous method of configuration file and Pod and embodiment one in a kind of revealed Kubernetes cluster of the present embodiment
It compares, the main distinction is, in the present embodiment, monitor 114 is not formed in ETCD component 104, and is formed at
In host node 10, and it is logically mutually indepedent with ETCD component 104.The calculating of ETCD component 104 is further reduced as a result,
Expense.User can modify to configuration file 100 by API Server201.
Identical technical solution please join described in embodiment one in the present embodiment and embodiment one, and details are not described herein.
The series of detailed descriptions listed above only for feasible embodiment of the invention specifically
Protection scope bright, that they are not intended to limit the invention, it is all without departing from equivalent implementations made by technical spirit of the present invention
Or change should all be included in the protection scope of the present invention.
It is obvious to a person skilled in the art that invention is not limited to the details of the above exemplary embodiments, Er Qie
In the case where without departing substantially from spirit or essential attributes of the invention, the present invention can be realized in other specific forms.Therefore, no matter
From the point of view of which point, the present embodiments are to be considered as illustrative and not restrictive, and the scope of the present invention is by appended power
Benefit requires rather than above description limits, it is intended that all by what is fallen within the meaning and scope of the equivalent elements of the claims
Variation is included within the present invention.Any reference signs in the claims should not be construed as limiting the involved claims.
In addition, it should be understood that although this specification is described in terms of embodiments, but not each embodiment is only wrapped
Containing an independent technical solution, this description of the specification is merely for the sake of clarity, and those skilled in the art should
It considers the specification as a whole, the technical solutions in the various embodiments may also be suitably combined, forms those skilled in the art
The other embodiments being understood that.
Claims (10)
- The synchronous method of configuration file and Pod in 1.Kubernetes cluster, which comprises the following steps:It is configured to monitor the whether changed monitor of configuration file corresponding to Pod；Triggering Pod is set and configuration file executes the initial trigger variable of simultaneously operating；The snoop results of configuration file are synchronized to API Server by monitor；Kubelet component built-in label selector be not to wait for current configuration file a upper version configuration file with Whether the simultaneously operating between Pod is completed, and the current configuration file is injected into Pod, to complete Pod and be currently configured Simultaneously operating between file, and restore initial trigger variable.
- 2. synchronous method according to claim 1, which is characterized in that the monitor is at least formed in ETCD component.
- 3. synchronous method according to claim 2, which is characterized in that further include: judge current configuration file whether with it is upper The configuration file of one version changes；If so, the current configuration file is injected into Pod, to execute Pod and current configuration file by Kubelet component Between simultaneously operating；If it is not, the configuration file of a upper version is injected into Pod, to execute Pod and a upper version by Kubelet component Simultaneously operating between this configuration file.
- 4. synchronous method according to claim 1, which is characterized in that the label selector is formed by mark by Pod Label select Pod with search value.
- 5. synchronous method according to claim 1, which is characterized in that when the simultaneously operating between Pod and configuration file is held After row finishes, further includes:Judge current configuration file corresponding to Pod whether and ETCD component in saved configuration corresponding with the Pod text Part matches；If so, determining that the simultaneously operating between configuration file and Pod is completed；If it is not, then determining that the simultaneously operating between configuration file and Pod does not complete.
- 6. synchronous method according to claim 1, which is characterized in that the setting of the initial trigger variable of the configuration file For FALSE, and only when the triggering variable of configuration file is TRUE, it is synchronous with configuration file that Pod is executed by Kubelet component Operation.
- 7. synchronous method according to claim 6, which is characterized in that when completing simultaneously operating between Pod and configuration file Afterwards, further includes:The initial trigger variable of configuration file is re-set as FALSE.
- 8. the synchronous method according to any one of claim 2 to 7, which is characterized in that further include: when monitor listens to When changing in the configuration file in ETCD component, from monitor to Kubelet component issue suspension execute configuration file with Pod executes the instruction of simultaneously operating, current configuration file to be injected into Pod by API Server.
- 9. synchronous method according to claim 5, which is characterized in that further include: by Pod send simultaneously operating record and Synchronized result is saved into the log system coupled with Pod.
- 10. synchronous method according to claim 8, which is characterized in that the configuration file is by ConfigMap and Secret Common description.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910089488.2A CN109831500B (en) | 2019-01-30 | 2019-01-30 | Synchronization method for configuration file and Pod in Kubernetes cluster |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910089488.2A CN109831500B (en) | 2019-01-30 | 2019-01-30 | Synchronization method for configuration file and Pod in Kubernetes cluster |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109831500A true CN109831500A (en) | 2019-05-31 |
| CN109831500B CN109831500B (en) | 2020-04-28 |
Family
ID=66862960
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910089488.2A Active CN109831500B (en) | 2019-01-30 | 2019-01-30 | Synchronization method for configuration file and Pod in Kubernetes cluster |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109831500B (en) |
Cited By (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110297641A (en) * | 2019-06-25 | 2019-10-01 | 四川长虹电器股份有限公司 | Layout dispositions method is applied based on kubernetes |
| CN110888736A (en) * | 2019-11-15 | 2020-03-17 | 北京浪潮数据技术有限公司 | Application management method and system based on container cloud platform and related components |
| CN111262908A (en) * | 2020-01-09 | 2020-06-09 | 中国工商银行股份有限公司 | Task construction method and system based on jenkins |
| CN111708609A (en) * | 2020-06-19 | 2020-09-25 | 中国—东盟信息港股份有限公司 | Kubernetes container based implementation method and system for configuring dictionary and security dictionary |
| CN111740869A (en) * | 2020-08-19 | 2020-10-02 | 广东省新一代通信与网络创新研究院 | Physical network card-based kubernets network implementation method, system, equipment and medium |
| CN111857759A (en) * | 2020-07-29 | 2020-10-30 | 广州锦行网络科技有限公司 | Technical method for realizing honeypot service container distributed deployment based on kubernets |
| CN112000363A (en) * | 2020-07-30 | 2020-11-27 | 苏州浪潮智能科技有限公司 | Method and system for managing big data assembly configuration file |
| CN112068875A (en) * | 2020-08-04 | 2020-12-11 | 广州太平洋电脑信息咨询有限公司 | System and method for realizing thread filtering strategy based on java dynamic loading |
| CN112764886A (en) * | 2021-01-29 | 2021-05-07 | 上海弘积信息科技有限公司 | Load balancing controller based on Kubernetes platform |
| CN112860435A (en) * | 2021-01-29 | 2021-05-28 | 西藏宁算科技集团有限公司 | Method for solving edge node availability in 5G scene |
| CN113010385A (en) * | 2021-03-18 | 2021-06-22 | 山东英信计算机技术有限公司 | Task state updating method, device, equipment and medium |
| WO2021238301A1 (en) * | 2020-05-27 | 2021-12-02 | 华为技术有限公司 | Application update method, apparatus and device and medium |
| CN113760448A (en) * | 2021-04-30 | 2021-12-07 | 中科天玑数据科技股份有限公司 | Big data management platform based on kubernets |
| CN113872997A (en) * | 2020-06-30 | 2021-12-31 | 华为技术有限公司 | Container group POD reconstruction method based on container cluster service and related equipment |
| CN113985961A (en) * | 2021-10-22 | 2022-01-28 | 杭州博盾习言科技有限公司 | Clock synchronization device, method, electronic device, and storage medium |
| WO2022028056A1 (en) * | 2020-08-06 | 2022-02-10 | 苏州浪潮智能科技有限公司 | Mirror list query architecture of multi-architecture cloud platform mirror warehouse |
| CN115102877A (en) * | 2022-05-23 | 2022-09-23 | 苏州浪潮智能科技有限公司 | Virtual network card network detection method, device, equipment and medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106357447A (en) * | 2016-09-21 | 2017-01-25 | 努比亚技术有限公司 | Synchronizing method and device for configuration data |
| CN107908708A (en) * | 2017-11-09 | 2018-04-13 | 北京锐安科技有限公司 | A kind of method, system, equipment and the storage medium of group document synchronization |
| CN109062655A (en) * | 2018-06-05 | 2018-12-21 | 腾讯科技（深圳）有限公司 | A kind of containerization cloud platform and server |
| CN109213571A (en) * | 2018-08-30 | 2019-01-15 | 北京百悟科技有限公司 | A kind of internal memory sharing method, Container Management platform and computer readable storage medium |
| CN109271233A (en) * | 2018-07-25 | 2019-01-25 | 上海数耕智能科技有限公司 | The implementation method of Hadoop cluster is set up based on Kubernetes |
-
2019
- 2019-01-30 CN CN201910089488.2A patent/CN109831500B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106357447A (en) * | 2016-09-21 | 2017-01-25 | 努比亚技术有限公司 | Synchronizing method and device for configuration data |
| CN107908708A (en) * | 2017-11-09 | 2018-04-13 | 北京锐安科技有限公司 | A kind of method, system, equipment and the storage medium of group document synchronization |
| CN109062655A (en) * | 2018-06-05 | 2018-12-21 | 腾讯科技（深圳）有限公司 | A kind of containerization cloud platform and server |
| CN109271233A (en) * | 2018-07-25 | 2019-01-25 | 上海数耕智能科技有限公司 | The implementation method of Hadoop cluster is set up based on Kubernetes |
| CN109213571A (en) * | 2018-08-30 | 2019-01-15 | 北京百悟科技有限公司 | A kind of internal memory sharing method, Container Management platform and computer readable storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 周佳威: "Kubernetes跨集群管理的设计与实现", 《中国优秀硕士学位论文全文数据库 信息科技辑》 * |
Cited By (24)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110297641A (en) * | 2019-06-25 | 2019-10-01 | 四川长虹电器股份有限公司 | Layout dispositions method is applied based on kubernetes |
| CN110888736A (en) * | 2019-11-15 | 2020-03-17 | 北京浪潮数据技术有限公司 | Application management method and system based on container cloud platform and related components |
| CN111262908A (en) * | 2020-01-09 | 2020-06-09 | 中国工商银行股份有限公司 | Task construction method and system based on jenkins |
| WO2021238301A1 (en) * | 2020-05-27 | 2021-12-02 | 华为技术有限公司 | Application update method, apparatus and device and medium |
| CN111708609A (en) * | 2020-06-19 | 2020-09-25 | 中国—东盟信息港股份有限公司 | Kubernetes container based implementation method and system for configuring dictionary and security dictionary |
| CN113872997B (en) * | 2020-06-30 | 2022-08-26 | 华为技术有限公司 | Container group POD reconstruction method based on container cluster service and related equipment |
| CN113872997A (en) * | 2020-06-30 | 2021-12-31 | 华为技术有限公司 | Container group POD reconstruction method based on container cluster service and related equipment |
| CN111857759A (en) * | 2020-07-29 | 2020-10-30 | 广州锦行网络科技有限公司 | Technical method for realizing honeypot service container distributed deployment based on kubernets |
| CN112000363A (en) * | 2020-07-30 | 2020-11-27 | 苏州浪潮智能科技有限公司 | Method and system for managing big data assembly configuration file |
| CN112068875A (en) * | 2020-08-04 | 2020-12-11 | 广州太平洋电脑信息咨询有限公司 | System and method for realizing thread filtering strategy based on java dynamic loading |
| CN112068875B (en) * | 2020-08-04 | 2024-05-17 | 广州太平洋电脑信息咨询有限公司 | System and method for realizing thread filtering strategy based on java dynamic loading |
| WO2022028056A1 (en) * | 2020-08-06 | 2022-02-10 | 苏州浪潮智能科技有限公司 | Mirror list query architecture of multi-architecture cloud platform mirror warehouse |
| CN111740869B (en) * | 2020-08-19 | 2021-01-08 | 广东省新一代通信与网络创新研究院 | Physical network card-based kubernets network implementation method, system, equipment and medium |
| CN111740869A (en) * | 2020-08-19 | 2020-10-02 | 广东省新一代通信与网络创新研究院 | Physical network card-based kubernets network implementation method, system, equipment and medium |
| CN112860435A (en) * | 2021-01-29 | 2021-05-28 | 西藏宁算科技集团有限公司 | Method for solving edge node availability in 5G scene |
| CN112764886A (en) * | 2021-01-29 | 2021-05-07 | 上海弘积信息科技有限公司 | Load balancing controller based on Kubernetes platform |
| US11915035B1 (en) | 2021-03-18 | 2024-02-27 | Shandong Yingxin Computer Technologies Co., Ltd. | Task state updating method and apparatus, device, and medium |
| CN113010385A (en) * | 2021-03-18 | 2021-06-22 | 山东英信计算机技术有限公司 | Task state updating method, device, equipment and medium |
| CN113010385B (en) * | 2021-03-18 | 2022-10-28 | 山东英信计算机技术有限公司 | Task state updating method, device, equipment and medium |
| CN113760448A (en) * | 2021-04-30 | 2021-12-07 | 中科天玑数据科技股份有限公司 | Big data management platform based on kubernets |
| CN113985961A (en) * | 2021-10-22 | 2022-01-28 | 杭州博盾习言科技有限公司 | Clock synchronization device, method, electronic device, and storage medium |
| CN113985961B (en) * | 2021-10-22 | 2023-10-24 | 杭州博盾习言科技有限公司 | Clock synchronization device, clock synchronization method, electronic equipment and storage medium |
| CN115102877B (en) * | 2022-05-23 | 2023-08-04 | 苏州浪潮智能科技有限公司 | Virtual network card network detection method, device, equipment and medium |
| CN115102877A (en) * | 2022-05-23 | 2022-09-23 | 苏州浪潮智能科技有限公司 | Virtual network card network detection method, device, equipment and medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109831500B (en) | 2020-04-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109831500A (en) | The synchronous method of configuration file and Pod in Kubernetes cluster | |
| AU2018220059B2 (en) | Type-to-type analysis for cloud computing technical components | |
| US8442958B2 (en) | Server change management | |
| CN107247619B (en) | Live migration of virtual machine method, apparatus, system, storage medium and equipment | |
| CN107220100A (en) | One kind exploitation O＆M method, device and cloud computing PaaS platform | |
| CN110178357A (en) | Cellular service based on cloud in the accessible cloud of remote equipment | |
| US20060075076A1 (en) | Updating software while it is running | |
| CN106991035A (en) | A kind of Host Supervision System based on micro services framework | |
| CN109905492B (en) | Safety operation management system and method based on distributed modular data center | |
| CN106385329A (en) | Processing method and device of resource pool and equipment | |
| CN105635311A (en) | Method for synchronizing resource pool information in cloud management platform | |
| CN106878363A (en) | A kind of information processing method, apparatus and system | |
| CN110138876A (en) | Task deployment method, apparatus, equipment and platform | |
| CN107800781A (en) | A kind of configuration data processing method and device | |
| CN109740765A (en) | A kind of machine learning system building method based on Amazon server | |
| CN102789392A (en) | Method for constructing power system distributed platform | |
| CN112486630A (en) | Distributed training deployment system and method thereof | |
| CN108241558A (en) | A kind of mirror image warehouse back-up device and method | |
| CN106375109A (en) | Switch configuration simulated issuing method, system and computer | |
| WO2023050110A1 (en) | Method for implementing automatic password change having fault tolerance mechanism for cloud host and cloud bastion host | |
| CN113110883A (en) | Starting method, device, equipment and storage medium of block chain system | |
| CN104615485A (en) | Dynamic transparent switching method for virtual machine inter-domain communication mode | |
| CN113253995B (en) | Method, device, equipment and storage medium for developing block chain system | |
| JP5781652B1 (en) | Stack management device, stack management method, and stack management program | |
| CN108153484A (en) | Shared storage system and its management method under a kind of virtualized environment |
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 | ||
| CP01 | Change in the name or title of a patent holder | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 214000, science and software park, Binhu District, Jiangsu, Wuxi 6 Patentee after: Huayun data holding group Co., Ltd Address before: 214000, science and software park, Binhu District, Jiangsu, Wuxi 6 Patentee before: WUXI CHINAC DATA TECHNICAL SERVICE Co.,Ltd. |