CN111666088A - Pod replacement method and device, electronic equipment and computer-readable storage medium - Google Patents
Pod replacement method and device, electronic equipment and computer-readable storage medium Download PDFInfo
- Publication number
- CN111666088A CN111666088A CN202010509095.5A CN202010509095A CN111666088A CN 111666088 A CN111666088 A CN 111666088A CN 202010509095 A CN202010509095 A CN 202010509095A CN 111666088 A CN111666088 A CN 111666088A
- Authority
- CN
- China
- Prior art keywords
- pod
- preset number
- cluster
- creating
- image
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 56
- 230000010076 replication Effects 0.000 claims description 12
- 238000004590 computer program Methods 0.000 claims description 4
- 230000008569 process Effects 0.000 abstract description 15
- 238000005096 rolling process Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 3
- 238000005034 decoration Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000011022 operating instruction Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 235000019800 disodium phosphate Nutrition 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Abstract
The embodiment of the application provides a method and a device for replacing a Pod, electronic equipment and a computer readable storage medium. The method comprises the following steps: when the mirror image warehouse has the mirror images of the appointed version, deleting a first preset number of first Pod (Pod) in the cluster, wherein a second preset number of pods are deployed in the cluster, the first preset number is smaller than the second preset number, and the second preset number is at least two; and creating a first preset number of second Pods corresponding to the specified version images. According to the scheme provided by the embodiment of the application, in the Pod replacement process, the undeleted first Pod exists in the cluster to provide service for the system, so that the system service is available in the version upgrading or rollback process of the system, the normal service of the system can be maintained, the interruption of system service is avoided, and the service quality of the system is improved.
Description
Technical Field
The present application relates to the field of cloud computing technologies, and in particular, to a Pod replacement method, an apparatus, an electronic device, and a computer-readable storage medium.
Background
With the development of virtualization technology, many industries such as finance, insurance and the like have realized the conversion from a physical machine to virtualization. The business system can be containerized by the enterprise, for example, the bank can containerize the financial centralized payment electronic system.
At present, a containerized and transformed system is mostly upgraded in an automatic script mode, and automatic rollback is performed when upgrading fails. In the process of upgrading or rolling back after upgrading failure, the system cannot normally provide service, which may cause service interruption and affect the service quality of the system.
Disclosure of Invention
The present application aims to solve at least one of the above technical drawbacks. The technical scheme adopted by the application is as follows:
in a first aspect, an embodiment of the present application provides a method for replacing Pod, where the method includes:
when the mirror image warehouse has the mirror images of the appointed version, deleting a first preset number of first Pod (Pod) in the cluster, wherein a second preset number of pods are deployed in the cluster, the first preset number is smaller than the second preset number, and the second preset number is at least two;
and creating a first preset number of second Pods corresponding to the specified version images.
Optionally, after creating the first preset number of second Pod corresponding to the specified version image, the method further includes:
and repeating the operation of deleting the first Pod and creating a second Pod equal to the deleted first Pod until all the first pods deployed in the cluster are replaced by the second pods.
Optionally, the method further includes:
before deleting a first preset number of first Pod in the cluster, if one first Pod is deployed in the cluster, creating at least one first Pod.
Optionally, if no mirror image of the specified version exists in the mirror image repository, the method further includes:
and creating a specified version image and uploading the specified version image to an image warehouse.
Optionally, creating a second Pod corresponding to the specified version image includes:
modifying a first RC file in the cluster into a second RC file corresponding to the specified version mirror image;
creating a Replication Controller corresponding to the second RC file;
a second Pod corresponding to the specified version image by the Replication Controller.
Optionally, the version image is designated as a docker image.
In a second aspect, an embodiment of the present application provides an apparatus for replacing a Pod, where the apparatus includes:
the system comprises a deleting module, a storing module and a judging module, wherein the deleting module is used for deleting a first preset number of first Pod (Pod) in a cluster when a specified version mirror exists in a mirror image warehouse, the cluster is provided with a second preset number of the Pod, the first preset number is smaller than the second preset number, and the second preset number is at least two;
and the creating module is used for creating a first preset number of second Pods corresponding to the specified version images.
Optionally, the apparatus further comprises:
and the repeated replacement module is used for repeatedly executing the operation of deleting the first Pod and creating a second Pod which is equal to the deleted first Pod after the second pods with the first preset number corresponding to the specified version images are created until the first pods deployed in the cluster are completely replaced by the second pods.
Optionally, the creating module is further configured to:
before deleting a first preset number of first Pod in the cluster, if one first Pod is deployed in the cluster, creating at least one first Pod.
Optionally, the apparatus further comprises:
and the mirror image creating module is used for creating the mirror image of the specified version and uploading the mirror image of the specified version to the mirror image warehouse.
Optionally, the creating module is specifically configured to:
creating a second Pod corresponding to the specified version image, comprising:
modifying a first RC file in the cluster into a second RC file corresponding to the specified version mirror image;
creating a Replication Controller corresponding to the second RC file;
a second Pod corresponding to the specified version image by the Replication Controller.
Optionally, the version image is designated as a docker image.
In a third aspect, an embodiment of the present application provides an electronic device, including: a processor and a memory;
a memory for storing operating instructions;
a processor, configured to execute, by calling an operation instruction, an alteration method of Pod as shown in any implementation of the first aspect of the present application.
In a fourth aspect, the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the Pod replacement method shown in any one of the embodiments of the first aspect of the present application.
The technical scheme provided by the embodiment of the application has the following beneficial effects:
according to the device provided by the embodiment of the application, when the specified version mirror image exists in the mirror image warehouse, the first Pod with the specified number in the cluster is deleted, the second Pod with the specified number corresponding to the specified version mirror image is created, the first Pod is deleted, and the second Pod corresponding to the specified version mirror image is created, so that the Pod can be replaced when the system is updated or rolled back, and the first Pod which is not deleted exists in the cluster to provide service for the system in the replacement process of the Pod, so that the service of the system can be used in the process of version upgrading or rolling back of the system, the normal service of the system can be maintained, the interruption of the system service is avoided, and the service quality of the system is improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the description of the embodiments of the present application will be briefly described below.
Fig. 1 is a schematic flowchart of an alternative method for Pod provided in an embodiment of the present application;
fig. 2 is a schematic structural diagram of an apparatus for replacing Pod according to an embodiment of the present disclosure;
fig. 3 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
Reference will now be made in detail to embodiments of the present application, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are exemplary only for the purpose of explaining the present application and are not to be construed as limiting the present invention.
As used herein, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. It will be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may also be present. Further, "connected" or "coupled" as used herein may include wirelessly connected or wirelessly coupled. As used herein, the term "and/or" includes all or any element and all combinations of one or more of the associated listed items.
To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
The following describes the technical solutions of the present application and how to solve the above technical problems with specific embodiments. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.
Fig. 1 shows a schematic flowchart of a Pod replacement method provided in an embodiment of the present application, and as shown in fig. 1, the method mainly includes:
step S110: when the mirror image warehouse has the mirror images of the appointed version, deleting a first preset number of first Pod (Pod) in the cluster, wherein a second preset number of pods are deployed in the cluster, the first preset number is smaller than the second preset number, and the second preset number is at least two;
step S120: and creating a first preset number of second Pods corresponding to the specified version images.
In the embodiment of the application, the containerization-modified system can be managed through a kubernets platform, and the cluster is a containerization cluster corresponding to the system.
In the embodiment of the application, the mirror image can be a docker mirror image and is stored in a mirror image warehouse in the cloud. When the system is upgraded, the image corresponding to the upgraded system can be written and designated as the image of the specified version. The image corresponding to the previous version of the system may also be designated as the specified version image when the current system is rolled back to the previous version of the system.
Pod is the fundamental unit of the kubernets system, and is also the resource object for running containerized applications on the kubernets system. In this embodiment, the first Pod, that is, the Pod before Pod replacement, corresponds to the current system version before upgrading or rolling back. The second Pod, i.e., post-replacement Pod, corresponds to the specified version image.
In this embodiment of the application, the number of the deployed Pod in the cluster is pre-specified, and after deleting the first Pod, the kubernets system creates a second Pod with the same number as the deleted first Pod, so that the deployed Pod in the cluster maintains the specified number. By deleting the first Pod and creating the second Pod, it is possible to accomplish the replacement of the Pod at the time of system update or rollback.
In this embodiment of the application, the second preset number is the number of the specified deployments of the Pod in the cluster, that is, before Pod replacement is performed, the first Pod with the second preset number is deployed in the cluster, where the second preset number is at least two, so that after part of the first Pod is deleted and before the second Pod is not created, the undeleted Pod provides a service for the system, and availability of the system service is ensured. The system may also be serviced by the second Pod after the second Pod is created.
As an example, the second preset number may be 3, and the first preset number may be 1 or 2, that is, there are 3 first Pod in the cluster, and 1 of the first Pod may be deleted and then 1 second Pod may be created, or 2 of the first Pod may be deleted and then 2 second pods may be created.
According to the method provided by the embodiment of the application, when the specified version mirror image exists in the mirror image warehouse, the first Pod with the specified number in the cluster is deleted, the second Pod with the specified number corresponding to the specified version mirror image is created, the replacement of the Pod is completed when the system is updated or rolled back, and the first Pod which is not deleted exists in the cluster to provide service for the system in the replacement process of the Pod, so that the availability of the system service in the process of version upgrading or rolling back of the system is ensured, the normal service of the system can be maintained, the interruption of the system service is avoided, and the service quality of the system is improved.
In an optional manner of the embodiment of the present application, after creating the first preset number of second Pod corresponding to the specified version image, the method further includes:
and repeating the operation of deleting the first Pod and creating a second Pod equal to the deleted first Pod until all the first pods deployed in the cluster are replaced by the second pods.
In this embodiment of the application, after deleting the first Pod and creating a corresponding number of second pods for the first time, the first Pod still exists in the cluster, and in order to implement replacement of all the first pods, operations of deleting the first Pod and creating a second Pod equal to the deleted first Pod may be repeatedly performed until all the first pods deployed in the cluster are replaced with the second pods.
As an example, the total number of the first Pod in the cluster is 5, and after the operations of deleting 1 first Pod and creating 1 second Pod are completed for the first time, the operations of deleting 1 first Pod and creating 1 second Pod may be repeatedly performed until all of the 5 first pods in the cluster are replaced by the second Pod.
In actual use, the number of the first Pod to be deleted at each time may be set according to actual needs, and the number of the first Pod to be deleted at each time may be the same or different.
In the process of repeatedly deleting the first Pod and creating a corresponding number of second pods, if a service request is received, the service request may be forwarded to the first Pod which is not deleted for processing, or forwarded to the second Pod which is created for processing.
In an optional manner of the embodiment of the present application, the method further includes:
before deleting a first preset number of first Pod in the cluster, if one first Pod is deployed in the cluster, creating at least one first Pod.
In practical use, only one first Pod may be deployed in a cluster, and in order to ensure availability of a system during Pod replacement, at least one first Pod may be created first, so that the number of the first pods in the cluster is at least two.
In an optional manner of the embodiment of the present application, if there is no mirror image of a specified version in the mirror image repository, the method further includes:
and creating a specified version image and uploading the specified version image to an image warehouse.
In the embodiment of the application, if the specified version mirror does not exist in the mirror image warehouse, the specified version mirror can be created, and the specified version mirror is uploaded to the mirror image warehouse. Taking system upgrade as an example, a new version of the image may be created and uploaded to the image repository.
In actual use, after the system upgrade is completed, the image of the old version is generally stored in the cloud continuously, so that the image can be used in the subsequent rollback of the system version.
In an optional manner of the embodiment of the present application, creating a second Pod corresponding to the specified version image includes:
modifying a first RC file in the cluster into a second RC file corresponding to the specified version mirror image;
creating a Replication Controller corresponding to the second RC file;
a second Pod corresponding to the specified version image by the Replication Controller.
In the embodiment of the application, the Replication Controller is configured to manage the Pod, and ensure that the number of the pods is the specified number, and the Pod creation is performed when the number of the pods is less than the specified number. The RC file provides a resource file for the replicationController.
In the embodiment of the application, the first RC file corresponds to the current system version before upgrading or rollback, and the version number in the first RC file can be modified to correspond to the specified version image, so as to obtain the second RC file.
In the embodiment of the application, a second Pod corresponding to the specified version image can be created through the Replication Controller corresponding to the second RC file.
Based on the same principle as the method shown in fig. 1, fig. 2 shows a schematic structural diagram of an apparatus for replacing a Pod according to an embodiment of the present application, and as shown in fig. 2, the apparatus 20 for replacing a Pod may include:
the deleting module 210 is configured to delete a first preset number of first Pod in the cluster when the specified version mirror exists in the mirror repository, where a second preset number of pods are deployed in the cluster, the first preset number is smaller than the second preset number, and the second preset number is at least two;
the creating module 220 is configured to create a first preset number of second Pod corresponding to the specified version image.
According to the device provided by the embodiment of the application, when the specified version mirror image exists in the mirror image warehouse, the first Pod with the specified number in the cluster is deleted, the second Pod with the specified number corresponding to the specified version mirror image is created, the first Pod is deleted, and the second Pod corresponding to the specified version mirror image is created, so that the Pod can be replaced when the system is updated or rolled back, and the first Pod which is not deleted exists in the cluster to provide service for the system in the replacement process of the Pod, so that the service of the system can be used in the process of version upgrading or rolling back of the system, the normal service of the system can be maintained, the interruption of the system service is avoided, and the service quality of the system is improved.
Optionally, the apparatus further comprises:
and the repeated replacement module is used for repeatedly executing the operation of deleting the first Pod and creating a second Pod which is equal to the deleted first Pod after the second pods with the first preset number corresponding to the specified version images are created until the first pods deployed in the cluster are completely replaced by the second pods.
Optionally, the creating module is further configured to:
before deleting a first preset number of first Pod in the cluster, if one first Pod is deployed in the cluster, creating at least one first Pod.
Optionally, the apparatus further comprises:
and the mirror image creating module is used for creating the mirror image of the specified version and uploading the mirror image of the specified version to the mirror image warehouse.
Optionally, the creating module is specifically configured to:
creating a second Pod corresponding to the specified version image, comprising:
modifying a first RC file in the cluster into a second RC file corresponding to the specified version mirror image;
creating a Replication Controller corresponding to the second RC file;
a second Pod corresponding to the specified version image by the Replication Controller.
Optionally, the version image is designated as a docker image.
It is understood that the above modules of the Pod replacement apparatus in the present embodiment have functions of implementing the corresponding steps of the Pod replacement method in the embodiment shown in fig. 1. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above. The modules can be software and/or hardware, and each module can be implemented independently or by integrating a plurality of modules. For the functional description of each module of the Pod replacement device, reference may be specifically made to the corresponding description of the Pod replacement method in the embodiment shown in fig. 1, and details are not repeated here.
The embodiment of the application provides an electronic device, which comprises a processor and a memory;
a memory for storing operating instructions;
and the processor is used for executing the Pod replacement method provided by any embodiment of the application by calling the operation instruction.
As an example, fig. 3 shows a schematic structural diagram of an electronic device to which an embodiment of the present application is applicable, and as shown in fig. 3, the electronic device 2000 includes: a processor 2001 and a memory 2003. Wherein the processor 2001 is coupled to a memory 2003, such as via a bus 2002. Optionally, the electronic device 2000 may also include a transceiver 2004. It should be noted that the transceiver 2004 is not limited to one in practical applications, and the structure of the electronic device 2000 is not limited to the embodiment of the present application.
The processor 2001 is applied to the embodiment of the present application to implement the method shown in the above method embodiment. The transceiver 2004 may include a receiver and a transmitter, and the transceiver 2004 is applied to the embodiments of the present application to implement the functions of the electronic device of the embodiments of the present application to communicate with other devices when executed.
The Processor 2001 may be a CPU (Central Processing Unit), general Processor, DSP (Digital Signal Processor), ASIC (Application specific integrated Circuit), FPGA (Field Programmable Gate Array) or other Programmable logic device, transistor logic device, hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor 2001 may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs and microprocessors, and the like.
The Memory 2003 may be a ROM (Read Only Memory) or other type of static storage device that can store static information and instructions, a RAM (Random Access Memory) or other type of dynamic storage device that can store information and instructions, an EEPROM (Electrically erasable programmable Read Only Memory), a CD-ROM (Compact disk Read Only Memory) or other optical disk storage, optical disk storage (including Compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to these.
Optionally, the memory 2003 is used for storing application program code for performing the disclosed aspects, and is controlled in execution by the processor 2001. The processor 2001 is configured to execute the application program code stored in the memory 2003 to implement the Pod replacement method provided in any of the embodiments of the present application.
The electronic device provided by the embodiment of the application is applicable to any embodiment of the method, and is not described herein again.
Compared with the prior art, the embodiment of the application provides the electronic equipment, when the specified version mirror image exists in the mirror image warehouse, the first Pod with the specified number in the cluster is deleted, the second Pod with the specified number corresponding to the specified version mirror image is created, the replacement of the Pod is completed when the system is updated or rolled back by deleting the first Pod and creating the second Pod corresponding to the specified version mirror image, and because the undeleted first Pod exists in the cluster to provide service for the system in the replacement process of the Pod, the availability of the system service in the process of version upgrade or rolling back of the system is ensured, the normal service of the system can be maintained, the interruption of the system service is avoided, and the service quality of the system is improved.
The embodiment of the application provides a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, the program implements the Pod replacement method shown in the above method embodiment.
The computer-readable storage medium provided in the embodiments of the present application is applicable to any of the embodiments of the foregoing method, and is not described herein again.
Compared with the prior art, the embodiment of the application provides a computer-readable storage medium, and the method includes deleting a specified number of first Pods in a cluster when a specified version mirror exists in a mirror warehouse, creating a specified number of second Pods corresponding to the specified version mirror, deleting the first Pods, and creating the second Pods corresponding to the specified version mirror, so that the replacement of the Pods is completed when a system is updated or rolled back, and because the undeleted first Pods exist in the cluster in the replacement process of the Pods to provide service for the system, the availability of the system service is ensured in the process of version upgrade or rolling back of the system, the normal service of the system can be maintained, the interruption of system service is avoided, and the service quality of the system is improved.
It should be understood that, although the steps in the flowcharts of the figures are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and may be performed in other orders unless explicitly stated herein. Moreover, at least a portion of the steps in the flow chart of the figure may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed alternately or alternately with other steps or at least a portion of the sub-steps or stages of other steps.
The foregoing is only a partial embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.
Claims (10)
1. A method for replacing Pod, comprising:
when the mirror image warehouse has the mirror image with the appointed version, deleting a first Pod with a first preset number in the cluster, wherein the cluster is deployed with a second preset number of pods, the first preset number is smaller than the second preset number, and the second preset number is at least two;
and creating a first preset number of second Pods corresponding to the specified version mirror images.
2. The method of claim 1, wherein after creating the first preset number of second Pod corresponding to the specified version image, the method further comprises:
and repeating the operation of deleting the first Pod and creating a second Pod equal to the deleted first Pod until all the first pods deployed in the cluster are replaced by the second pods.
3. The method of claim 1 or 2, further comprising:
before deleting a first preset number of first Pod in the cluster, if one first Pod is deployed in the cluster, creating at least one first Pod.
4. The method of claim 3, wherein if no specified version image exists in the image repository, the method further comprises:
creating a specified version image and uploading the specified version image to an image warehouse.
5. The method of claim 3, wherein creating the second Pod corresponding to the specified version image comprises:
modifying the first RC file in the cluster into a second RC file corresponding to the specified version mirror image;
creating a Replication Controller corresponding to the second RC file;
and a second Pod corresponding to the specified version image through the Replication Controller.
6. The method of claim 3, wherein the specified version image is a docker image.
7. An apparatus for replacing Pod, comprising:
the system comprises a deleting module, a storing module and a judging module, wherein the deleting module is used for deleting a first preset number of first Pod (Pod) in a cluster when a specified version mirror exists in a mirror warehouse, the cluster is provided with a second preset number of the Pod, the first preset number is smaller than the second preset number, and the second preset number is at least two;
and the creating module is used for creating a first preset number of second Pods corresponding to the specified version images.
8. The apparatus of claim 7, further comprising:
and the replacing module is used for repeatedly executing the operation of deleting the first Pod and creating a second Pod which is equal to the deleted first Pod after the second pods with the first preset number corresponding to the specified version images are created until the first pods deployed in the cluster are completely replaced by the second pods.
9. An electronic device comprising a processor and a memory;
the memory is used for storing operation instructions;
the processor is used for executing the method of any one of claims 1-6 by calling the operation instruction.
10. A computer-readable storage medium, characterized in that the storage medium has stored thereon a computer program which, when being executed by a processor, carries out the method of any one of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010509095.5A CN111666088A (en) | 2020-06-07 | 2020-06-07 | Pod replacement method and device, electronic equipment and computer-readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010509095.5A CN111666088A (en) | 2020-06-07 | 2020-06-07 | Pod replacement method and device, electronic equipment and computer-readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111666088A true CN111666088A (en) | 2020-09-15 |
Family
ID=72386515
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010509095.5A Pending CN111666088A (en) | 2020-06-07 | 2020-06-07 | Pod replacement method and device, electronic equipment and computer-readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111666088A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113297031A (en) * | 2021-05-08 | 2021-08-24 | 阿里巴巴新加坡控股有限公司 | Container group protection method and device in container cluster |
| CN113626054A (en) * | 2021-08-16 | 2021-11-09 | 聚好看科技股份有限公司 | Business service updating method and device |
| CN114756261A (en) * | 2022-03-23 | 2022-07-15 | 广域铭岛数字科技有限公司 | Container cluster upgrading method and system, electronic equipment and medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107515776A (en) * | 2017-07-18 | 2017-12-26 | 深信服科技股份有限公司 | The uninterrupted upgrade method of business, node to be upgraded and readable storage medium storing program for executing |
| CN108804129A (en) * | 2018-05-31 | 2018-11-13 | 新华三技术有限公司 | A kind of method for upgrading software and device |
| CN110413300A (en) * | 2019-07-30 | 2019-11-05 | 中国工商银行股份有限公司 | Rolling upgrade control method, device, equipment and storage medium |
| US20200073655A1 (en) * | 2018-09-05 | 2020-03-05 | Nanum Technologies Co., Ltd. | Non-disruptive software update system based on container cluster |
-
2020
- 2020-06-07 CN CN202010509095.5A patent/CN111666088A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107515776A (en) * | 2017-07-18 | 2017-12-26 | 深信服科技股份有限公司 | The uninterrupted upgrade method of business, node to be upgraded and readable storage medium storing program for executing |
| CN108804129A (en) * | 2018-05-31 | 2018-11-13 | 新华三技术有限公司 | A kind of method for upgrading software and device |
| US20200073655A1 (en) * | 2018-09-05 | 2020-03-05 | Nanum Technologies Co., Ltd. | Non-disruptive software update system based on container cluster |
| CN110413300A (en) * | 2019-07-30 | 2019-11-05 | 中国工商银行股份有限公司 | Rolling upgrade control method, device, equipment and storage medium |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113297031A (en) * | 2021-05-08 | 2021-08-24 | 阿里巴巴新加坡控股有限公司 | Container group protection method and device in container cluster |
| CN113626054A (en) * | 2021-08-16 | 2021-11-09 | 聚好看科技股份有限公司 | Business service updating method and device |
| CN114756261A (en) * | 2022-03-23 | 2022-07-15 | 广域铭岛数字科技有限公司 | Container cluster upgrading method and system, electronic equipment and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111666088A (en) | Pod replacement method and device, electronic equipment and computer-readable storage medium | |
| CN110532098B (en) | Method and system for providing GPU (graphics processing Unit) service | |
| CN102971711A (en) | An apparatus for processing a batched unit of work | |
| CN111367659B (en) | Resource management method, equipment and medium for nodes in Kubernetes | |
| CN108776643B (en) | Target code merging control method and system based on version control process | |
| CN111143446A (en) | Data structure conversion processing method and device of data object and electronic equipment | |
| CN110162344B (en) | Isolation current limiting method and device, computer equipment and readable storage medium | |
| CN108664343B (en) | State calling method and device for micro-service | |
| KR102106449B1 (en) | Method, device and server for checking a defective function | |
| US20240045787A1 (en) | Code inspection method under weak memory ordering architecture and corresponding device | |
| CN110968339B (en) | Method and device for front-end building tool and electronic equipment | |
| CN110908644B (en) | Configuration method and device of state node, computer equipment and storage medium | |
| CN111294377B (en) | Dependency network request sending method, terminal device and storage medium | |
| CN116226078A (en) | Data migration method, device, equipment and storage medium | |
| CN115714706A (en) | Access acceleration system and method based on embedded H5, storage medium and electronic equipment | |
| CN110502296B (en) | Method, equipment and storage medium for displaying firmware upgrading command | |
| CN109150993B (en) | Method for obtaining network request tangent plane, terminal device and storage medium | |
| CN111459570B (en) | PDF plug-in loading method, electronic equipment and computer storage medium | |
| CN110543351A (en) | Data processing method and computer device | |
| CN116680277B (en) | Information verification method, device, equipment and storage medium | |
| CN111427868B (en) | Processing method and device for operation request in database migration and electronic equipment | |
| EP4174645A1 (en) | Mirror image distribution method, electronic device, and storage medium | |
| CN111078658B (en) | Method and device for mounting cluster file system | |
| CN115392485A (en) | Data processing method and system for deep learning framework | |
| CN116954991A (en) | Data processing method, device, electronic equipment and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200915 |