Cloud Native Application Version Management Method, System, Device and Readable Storage Medium

Abstract

The present invention provides a cloud native application version management method, a cloud native application version management system, a cloud native application version management device and a readable storage medium; the cloud native application version management method is used for a cloud native platform, and the cloud native application version management method includes: obtaining a first update patch for the cloud native application; detecting whether the first update patch conflicts with at least one second update patch of the cloud native application stored in the cloud platform; and storing the first update patch in the cloud platform based on the fact that the first update patch does not conflict with at least one second update patch. This application avoids the need for cloud native application operators to operate and maintain the cloud native application version management system by performing detection and management of cloud native application patches on the cloud platform, thereby reducing the version management cost of cloud native applications, reducing the operation and maintenance cost of cloud native applications, and thus reducing the cloud native application operation cost borne by cloud native application operators.

Description

Technical Field

[0001] The present invention relates to the field of cloud computing technology, and in particular to a cloud-native application version management method, a cloud-native application version management system, a cloud-native application version management device, and a readable storage medium. Background Art

[0002] Currently, in related technologies, the management of cloud-native application versions requires a complete cloud-native application version management system. For cloud-native application operators using mainstream private cloud or hybrid cloud deployment models, the cost of running and maintaining the cloud-native application version management system is high, resulting in cloud-native application operators having to pay additional operating costs to ensure the normal management of cloud-native application versions. Summary of the Invention

[0003] The present invention aims to solve at least one of the technical problems existing in the prior art or related art.

[0004] To this end, a first aspect of the present invention proposes a cloud-native application version management method.

[0005] A second aspect of the present invention provides a cloud-native application version management system.

[0006] A third aspect of the present invention provides a cloud-native application version management device.

[0007] A fourth aspect of the present invention provides a readable storage medium.

[0008] In view of this, the first aspect of the present invention provides a cloud native application version management method, which is used for a cloud native platform. The cloud native application version management method includes: obtaining a first update patch for the cloud native application; detecting whether the first update patch conflicts with at least one second update patch of the cloud native application stored in the cloud platform; and storing the first update patch in the cloud platform based on the fact that the first update patch does not conflict with the at least one second update patch.

[0009] The present application provides a cloud native application version management method, which is applied in a cloud native platform. The method obtains a first update patch that can be used to update a cloud native application through the cloud native platform, performs conflict detection on the first update patch that can be used to update a cloud native application, detects whether the first update patch conflicts with other update patches of the cloud native application that have been stored in the cloud platform, and stores the first update patch for updating the cloud native application in the cloud platform if the first update patch does not conflict with other update patches of the cloud native application. By performing detection and management of cloud native application patches on the cloud platform, the operator of the cloud native application is prevented from having to operate and maintain the cloud native application version management system by himself, thereby reducing the version management cost of the cloud native application, and reducing the operation and maintenance cost of the cloud native application, thereby reducing the cloud native application operation cost that the operator of the cloud native application needs to bear.

[0010] A second aspect of the present invention provides a cloud-native application version management system, which is used for a cloud-native platform. The cloud-native application version management system includes an acquisition unit, a detection unit, and a storage unit; the acquisition unit is used to acquire a first update patch for a cloud-native application; the detection unit is used to detect whether the first update patch conflicts with at least one second update patch of a cloud-native application stored in the cloud platform; the storage unit is used to store the first update patch in the cloud platform based on the fact that the first update patch does not conflict with at least one second update patch.

[0011] In this technical solution, by setting an acquisition unit, a first update patch for updating a cloud-native application can be obtained. By setting a detection unit, a conflict detection is performed on the first update patch that can be used to update the cloud-native application to detect whether the first update patch conflicts with other update patches of the cloud-native application that have been stored in the cloud platform. By setting a storage unit, if the first update patch does not conflict with other update patches of the cloud-native application, the first update patch for updating the cloud-native application is stored in the cloud platform. By performing cloud-native application patch detection and management on the cloud platform, the cloud-native application operator is prevented from having to operate and maintain the cloud-native application version management system on its own, thereby reducing the version management cost of the cloud-native application, reducing the operation and maintenance cost of the cloud-native application, and thus reducing the cloud-native application operation cost that the cloud-native application operator needs to bear.

[0012] A third aspect of the present invention provides a cloud-native application version management device, comprising a memory configured to store programs or instructions and a processor configured to execute the stored programs or instructions to implement the steps of the cloud-native application version management method described in any of the above technical solutions. Therefore, the cloud-native application version management device has all the beneficial technical effects of the cloud-native application version management method described in any of the above technical solutions, and will not be further elaborated here.

[0013] A fourth aspect of the present invention provides a readable storage medium having a program or instruction stored thereon. When executed by a processor, the program or instruction implements the steps of the cloud-native application version management method as described in any of the above technical solutions. Therefore, the readable storage medium has all the beneficial technical effects of the cloud-native application version management method described in any of the above technical solutions, and no further description is given here.

[0014] Additional aspects and advantages of the present invention will be set forth in part in the description which follows and, in part, will be obvious from the description which follows, or may be learned by practice of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The above and / or additional aspects and advantages of the present invention will become apparent and readily understood from the following description of the embodiments with reference to the accompanying drawings, in which:

[0016] Figure 1 One of the flowcharts of the cloud native application version management method according to one embodiment of the present invention is shown;

[0017] Figure 2 A second flowchart of a method for managing cloud-native application versions according to an embodiment of the present invention is shown;

[0018] Figure 3 A third flowchart of a cloud native application version management method according to an embodiment of the present invention is shown;

[0019] Figure 4 A fourth flowchart of a cloud-native application version management method according to an embodiment of the present invention is shown;

[0020] Figure 5 A fifth flowchart of a cloud-native application version management method according to an embodiment of the present invention is shown;

[0021] Figure 6 A sixth flowchart of a cloud native application version management method according to an embodiment of the present invention is shown;

[0022] Figure 7 FIG7 shows a seventh flowchart of a cloud native application version management method according to an embodiment of the present invention;

[0023] Figure 8 An eighth flowchart of a cloud native application version management method according to an embodiment of the present invention is shown;

[0024] Figure 9 A ninth flowchart of a method for managing cloud-native application versions according to an embodiment of the present invention is shown;

[0025] Figure 10 A block diagram of a cloud-native application version management system according to an embodiment of the present invention is shown;

[0026] Figure 11 One of the block diagrams of a cloud native application version management apparatus according to an embodiment of the present invention is shown;

[0027] Figure 12 A second block diagram of a cloud native application version management device according to an embodiment of the present invention is shown;

[0028] Figure 13 A flowchart of a cloud-native application patch development method according to an embodiment of the present invention is shown. DETAILED DESCRIPTION

[0029] In order to more clearly understand the above-mentioned objects, features and advantages of the present invention, the present invention is further described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be noted that, in the absence of conflict, the embodiments of the present application and the features therein can be combined with each other.

[0030] In the following description, many specific details are set forth to facilitate a full understanding of the present invention. However, the present invention may also be implemented in other ways different from those described herein. Therefore, the scope of protection of the present invention is not limited to the specific embodiments disclosed below.

[0031] Refer to the following Figures 1 to 13 A cloud-native application version management method, a cloud-native application version management system, a cloud-native application version management device, a readable storage medium, and a cloud-native application patch development method according to some embodiments of the present invention are described.

[0032] The present invention provides a cloud native application version management method, which is used for cloud native platforms, such as Figure 1 As shown in the figure, cloud-native application version management methods include:

[0033] Step 102: Obtain a first update patch for the cloud native application;

[0034] Step 104 , detecting whether the first update patch conflicts with at least one second update patch of the cloud native application stored in the cloud platform;

[0035] Step 106: Based on the fact that the first update patch does not conflict with at least one second update patch, the first update patch is stored in the cloud platform.

[0036] In this embodiment, a cloud-native application version management method is provided. The cloud-native application version management method is applied in a cloud-native platform. A first update patch that can be used to update the cloud-native application is obtained through the cloud-native platform. A conflict detection is performed on the first update patch that can be used to update the cloud-native application. The first update patch is detected to see if there is a conflict with other update patches of the cloud-native application that are already stored in the cloud platform. If the first update patch does not conflict with other update patches of the cloud-native application, the first update patch for updating the cloud-native application is stored in the cloud platform. By performing cloud-native application patch detection and management on the cloud platform, the cloud-native application operator is prevented from having to operate and maintain the cloud-native application version management system on its own, thereby reducing the version management cost of the cloud-native application, and reducing the operation and maintenance cost of the cloud-native application, thereby reducing the cloud-native application operation cost that the cloud-native application operator needs to bear.

[0037] When running cloud-native applications, a complete cloud-native application version management system is usually required to manage the versions of cloud-native applications. For cloud-native application operators who use mainstream private cloud or hybrid cloud deployment models, they usually need to run and maintain the cloud-native application version management system by themselves. This application designs a cloud-native application version management method based on a cloud platform, so that cloud-native application operators do not need to run and maintain the cloud-native application version management system by themselves. The cloud platform on which the cloud-native application runs can manage the version of the cloud-native application, thereby reducing the operating costs of cloud-native application operators and improving operational capabilities. In addition, this application changes the version management of cloud-native applications from traditional image management to management through patches, which reduces the management granularity, improves the degree of management refinement, and improves the flexibility and stability of version management.

[0038] This embodiment provides a cloud-native application version management method. In addition to the technical features of the above embodiments, this embodiment further includes the following technical features.

[0039] After detecting whether the first update patch conflicts with at least one second update patch of the cloud native application stored in the cloud platform, a patch conflict prompt message is sent to the patch developer based on the conflict between the first update patch and the second update patch.

[0040] In this embodiment, when detecting whether there is a conflict between the first update patch and other update patches of the cloud native application already stored in the cloud platform, if it is found that the first update patch conflicts with other update patches already stored in the cloud platform, the storage of the first update patch is canceled and a conflict prompt message is sent to the patch developer. By detecting that the first update patch conflicts with other update patches already stored in the cloud platform, the probability of the first update patch conflicting with other patches after storage can be reduced, the probability of data damage to the first update patch or other patches due to the conflict can be reduced, the probability of cloud native applications updated by the patch running errors due to patch damage can be reduced, the probability of losses caused by cloud native application running errors can be reduced, and the update stability and reliability of the cloud native application can be improved. In addition, after the conflict is detected, a patch conflict prompt message will be sent to the patch developer, which can enable the patch developer to be informed of the patch conflict in a timely manner, so that the patch developer can adjust the patch in a timely manner, and improve the efficiency and reliability of patch development.

[0041] Specifically, if Figure 2 As shown, in this embodiment, the cloud native application version management method includes:

[0042] Step 202: Obtain a first update patch for the cloud native application;

[0043] Step 204 , detecting whether the first update patch conflicts with at least one second update patch of the cloud native application stored in the cloud platform;

[0044] Step 206: Send a patch conflict prompt message to the patch developer based on the conflict between the first update patch and the second update patch.

[0045] This embodiment provides a cloud-native application version management method. In addition to the technical features of the above embodiments, this embodiment further includes the following technical features.

[0046] After storing the first update patch on the cloud platform, the cloud-native application version management method includes: obtaining the version of the cloud-native application that needs to be updated based on the update instruction of the cloud-native application; obtaining a third update patch corresponding to the version of the cloud-native application that needs to be updated according to the version of the cloud-native application that needs to be updated; updating the image of the cloud-native application according to the third update patch; wherein the third update patch is at least one update patch among the first update patch and at least one second update patch; and publishing the updated image of the cloud-native application.

[0047] In this embodiment, after the first update patch is stored in the cloud platform, when the update instruction of the cloud native application is received, the cloud platform obtains the version information that needs to be updated for the cloud native application, obtains the update required patch corresponding to the version information based on the version information that needs to be updated for the cloud native application, and updates the image of the currently running cloud native application through the obtained update required patch. After the image update is completed, the updated image is applied to the cloud native application to complete the version update of the cloud native application. Among them, the update required patch can be a patch stored in the cloud platform or a patch that has been previously updated by the cloud native application. This application can manage the version of the cloud native application through the cloud platform by completing the version confirmation of the cloud native application update, obtaining the update patch of the corresponding version, and updating the cloud native application through the update patch, thereby reducing the operating cost of the cloud native application.

[0048] Specifically, if Figure 3 As shown, in this embodiment, the cloud native application version management method includes:

[0049] Step 302: Obtain a first update patch for the cloud native application;

[0050] Step 304 , detecting whether the first update patch conflicts with at least one second update patch of the cloud native application stored in the cloud platform;

[0051] Step 306: storing the first update patch in the cloud platform based on the fact that the first update patch does not conflict with at least one second update patch;

[0052] Step 308: Based on the update instruction of the cloud native application, obtain the version that the cloud native application needs to update;

[0053] Step 310: Obtain a third update patch corresponding to the version required to be updated for the cloud native application according to the version required to be updated for the cloud native application;

[0054] Step 312: Update the image of the cloud-native application according to the third update patch;

[0055] Step 314: Release the updated cloud-native application image.

[0056] The third update patch is at least one update patch among the first update patch and the at least one second update patch;

[0057] Specifically, this application completes the process of confirming the updated version of the cloud native application, searching for updated patches, updating the patch image, and publishing the updated image on the cloud platform, thereby avoiding the need for cloud native application operators to operate and maintain the cloud native application version management system by themselves, reducing the version management cost of cloud native applications, reducing the operation and maintenance costs of cloud native applications, and thus reducing the cloud native application operating costs that cloud native application operators need to bear. In addition, this application adopts the patch update method when updating the version, avoiding the need to cover the entire content of the cloud native application when updating through the image, resulting in repeated modifications of the same content, which prolongs the update time, reduces the update efficiency, and increases the error rate of the original content. It improves the efficiency and stability of the update, and can reduce the management granularity, improve the degree of management refinement, and improve the flexibility and stability of version management.

[0058] This embodiment provides a cloud-native application version management method. In addition to the technical features of the above embodiments, this embodiment further includes the following technical features.

[0059] According to the version that the cloud-native application needs to be updated, obtaining the third update patch corresponding to the version that the cloud-native application needs to be updated includes: when the version that the cloud-native application needs to be updated is the first version, using the patch corresponding to the first version as the third update patch; wherein the first version is the previous version of the version corresponding to the cloud-native application.

[0060] In this embodiment, when obtaining the update patch corresponding to the version that the cloud native application needs to update, if the version that needs to be updated is the previous version of the version currently used by the cloud native application, the patch corresponding to the previous version of the version currently used by the cloud native application is used as the patch required for the cloud native application update, and the cloud native application is updated by obtaining the patch corresponding to the previous version of the version currently used by the cloud native application. By updating the cloud native application using the patch corresponding to the previous version of the version currently used by the cloud native application, the purpose of version rollback is achieved, so that the cloud native application can be easily rolled back to the previous version, which improves the flexibility of version rollback and reduces the impact on the operation of the cloud native application when problems occur in the current cloud native application version. In addition, the version rollback method using patches solves the problem of inflexible version rollback when version management is performed through mirroring, and solves the problem of low rollback efficiency and high probability of travel problems caused by the need to completely overwrite the current image with the historical image when performing version rollback through mirroring, thereby improving the efficiency and stability of rollback and the flexibility and stability of version management.

[0061] Specifically, if Figure 4 As shown, in this embodiment, the cloud native application version management method includes:

[0062] Step 402: Obtain a first update patch for the cloud native application;

[0063] Step 404 , detecting whether the first update patch conflicts with at least one second update patch of the cloud native application stored in the cloud platform;

[0064] Step 406: storing the first update patch in the cloud platform based on the fact that the first update patch does not conflict with at least one second update patch;

[0065] Step 408: Based on the update instruction of the cloud native application, obtain the version that the cloud native application needs to update;

[0066] Step 410: When the version that the cloud native application needs to update is the first version, the patch corresponding to the first version is used as the third update patch;

[0067] Step 412: Update the image of the cloud-native application according to the third update patch;

[0068] Step 414: Release the updated cloud-native application image.

[0069] Among them, the first version is the previous version corresponding to the cloud native application.

[0070] This embodiment provides a cloud-native application version management method. In addition to the technical features of the above embodiments, this embodiment further includes the following technical features.

[0071] According to the version that the cloud-native application needs to be updated, obtaining the third update patch corresponding to the version that the cloud-native application needs to be updated also includes: when the version that the cloud-native application needs to be updated is the second version, based on the fact that the second version does not conflict with the first version, using the patch corresponding to the second version as the third update patch; when the version that the cloud-native application needs to be updated is the second version, based on the fact that the second version conflicts with the first version, using the patch corresponding to the first version and the patch corresponding to the second version as the third update patch; wherein the second version is at least the previous version of the first version.

[0072] In this embodiment, when obtaining the update patch corresponding to the version that needs to be updated for the cloud native application, if the version that needs to be updated is a version before the first version, the version that needs to be updated is detected for conflicts with the first version. If no conflict is detected, the patch corresponding to the version that needs to be updated is used as the update patch for the cloud native application. If a conflict is detected, the patch corresponding to the first version and the patch corresponding to the version that needs to be updated are used together as the update patch for the cloud native application. The version of the cloud native application is rolled back to the version that needs to be updated in sequence through the update patch of the cloud native application, completing the version rollback when there is a version conflict. By using the patch corresponding to the version before the first version to update the cloud native application, the purpose of version rollback is achieved, so that the cloud native application can be easily rolled back to any historical version. Even if there is a conflict between versions during version rollback, the version rollback can be completed smoothly, thereby improving the flexibility of version rollback. In addition, the version rollback method using patches solves the problem of inflexible version rollback when version management is performed through images. It also solves the problem of low rollback efficiency and high probability of travel problems caused by the need to completely overwrite the current image with the historical image when performing version rollback through images. It also solves the problem of being unable to roll back normally when there is a conflict between images of different versions, thereby improving the efficiency and flexibility of rollback and the flexibility and stability of version management.

[0073] Specifically, if Figure 5 As shown, in this embodiment, when the version that the cloud-native application needs to update is the first version, the cloud-native application version management method includes:

[0074] Step 502: Obtain a first update patch for the cloud native application;

[0075] Step 504 , detecting whether the first update patch conflicts with at least one second update patch of the cloud native application stored in the cloud platform;

[0076] Step 506: storing the first update patch in the cloud platform based on the fact that the first update patch does not conflict with at least one second update patch;

[0077] Step 508: Based on the update instruction of the cloud native application, obtain the version that the cloud native application needs to update;

[0078] Step 510: When the version that the cloud native application needs to update is the first version, the patch corresponding to the first version is used as the third update patch;

[0079] Step 512: Update the image of the cloud-native application according to the third update patch;

[0080] Step 514: Release the updated cloud-native application image.

[0081] Specifically, when the version that the cloud-native application needs to update is the second version, based on the fact that the second version does not conflict with the first version, the cloud-native application version management method includes:

[0082] Step 502: Obtain a first update patch for the cloud native application;

[0083] Step 504 , detecting whether the first update patch conflicts with at least one second update patch of the cloud native application stored in the cloud platform;

[0084] Step 506: storing the first update patch in the cloud platform based on the fact that the first update patch does not conflict with at least one second update patch;

[0085] Step 508: Based on the update instruction of the cloud native application, obtain the version that the cloud native application needs to update;

[0086] When the version that the cloud-native application needs to update is the second version, based on the assumption that the second version does not conflict with the first version, the patch corresponding to the second version is used as the third update patch;

[0087] Step 512: Update the image of the cloud-native application according to the third update patch;

[0088] Step 514: Release the updated cloud-native application image.

[0089] The second version is at least a previous version of the first version.

[0090] Specifically, when the version that the cloud-native application needs to update is the second version, based on the conflict between the second version and the first version, the cloud-native application version management method includes:

[0091] Step 502: Obtain a first update patch for the cloud native application;

[0092] Step 504 , detecting whether the first update patch conflicts with at least one second update patch of the cloud native application stored in the cloud platform;

[0093] Step 506: storing the first update patch in the cloud platform based on the fact that the first update patch does not conflict with at least one second update patch;

[0094] Step 508: Based on the update instruction of the cloud native application, obtain the version that the cloud native application needs to update;

[0095] When the version that the cloud-native application needs to update is the second version, based on the conflict between the second version and the first version, the patch corresponding to the first version and the patch corresponding to the second version are used as the third update patch;

[0096] Step 512: Update the image of the cloud-native application according to the third update patch;

[0097] Step 514: Release the updated cloud-native application image.

[0098] This embodiment provides a cloud-native application version management method. In addition to the technical features of the above embodiments, this embodiment further includes the following technical features.

[0099] Updating the image of the cloud native application according to the third update patch includes: restarting the application program interface of the cloud platform; obtaining the storage address of the third update patch; pulling the third update patch according to the storage address; marking the third update patch; and updating the image of the cloud native application according to the marked third update patch.

[0100] In this embodiment, when using a cloud-native application update patch to update the cloud-native application image, it is necessary to restart the cloud platform's application program interface. During the restart, the storage address of the cloud-native application update patch is obtained. The cloud-native application update patch is pulled according to the obtained storage address. After pulling the cloud-native application update patch, the cloud-native application update patch is marked so that the system can know which version of the patch is required to update the cloud-native application version. The cloud-native application image is updated according to the marked cloud-native application update patch, thereby completing the cloud-native application version change. By actively obtaining the storage address of the update patch and actively pulling the update patch, the problem of low update efficiency when updating the cloud-native application version through the push image method is solved, the update process is simplified, and the update efficiency is improved. In addition, by marking the cloud-native application update patch, the probability of using the wrong update patch when updating the cloud-native application version is reduced, the probability of update errors is reduced, and the accuracy of the update is improved.

[0101] Specifically, if Figure 6 As shown, in this embodiment, the cloud native application version management method includes:

[0102] Step 602: Obtain a first update patch for the cloud native application;

[0103] Step 604 , detecting whether the first update patch conflicts with at least one second update patch of the cloud native application stored in the cloud platform;

[0104] Step 606: storing the first update patch in the cloud platform based on the fact that the first update patch does not conflict with at least one second update patch;

[0105] Step 608: Based on the update instruction of the cloud native application, obtain the version that the cloud native application needs to update;

[0106] Step 610: Obtain a third update patch corresponding to the version required to be updated for the cloud native application according to the version required to be updated for the cloud native application;

[0107] Step 612: Restart the application program interface of the cloud platform;

[0108] Step 614, obtaining the storage address of the third update patch;

[0109] Step 616: Pull the third update patch according to the storage address;

[0110] Step 618: Mark the third update patch;

[0111] Step 620: Update the image of the cloud-native application according to the marked third update patch;

[0112] Step 622: Release the updated cloud-native application image.

[0113] This embodiment provides a cloud-native application version management method. In addition to the technical features of the above embodiments, this embodiment further includes the following technical features.

[0114] Updating the image of the cloud-native application according to the marked third update patch includes: based on the presence of a mark in the marked third update patch, executing the update of the image of the cloud-native application according to the marked third update patch; based on the absence of a mark in the marked third update patch, re-marking the marked third update patch, and updating the image of the cloud-native application according to the re-marked marked third update patch.

[0115] In this embodiment, when using the marked cloud native application update patch to update the image of the cloud native application, the tag of the marked cloud native application update patch is detected. If the tag of the cloud native application update patch is marked normally, the image of the cloud native application can be updated through the marked cloud native application update patch. When it is detected that the cloud native application update patch is not marked normally, that is, the cloud native application update patch does not have a tag, it returns to the marking step, re-marks the cloud native application update patch, and again detects the tag of the marked cloud native application update patch. After normal marking, the image of the cloud native application can be updated through the marked cloud native application update patch. By detecting the tag of the marked cloud native application update patch, the probability of using the wrong update patch when the cloud native application is updated can be further reduced, the probability of update errors can be further reduced, and the accuracy of the update can be further improved.

[0116] Specifically, if Figure 7 As shown, in this embodiment, the cloud native application version management method includes:

[0117] Step 702: Obtain a first update patch for the cloud native application.

[0118] Step 704 , detecting whether the first update patch conflicts with at least one second update patch of the cloud native application stored in the cloud platform;

[0119] Step 706: storing the first update patch in the cloud platform based on the fact that the first update patch does not conflict with at least one second update patch;

[0120] Step 708: Based on the update instruction of the cloud native application, obtain the version that the cloud native application needs to update;

[0121] Step 710: Obtain a third update patch corresponding to the version required to be updated for the cloud native application according to the version required to be updated for the cloud native application;

[0122] Step 712: Restart the application program interface of the cloud platform;

[0123] Step 714, obtaining the storage address of the third update patch;

[0124] Step 716: Pull the third update patch according to the storage address;

[0125] Step 718: Mark the third update patch;

[0126] Step 720, determine whether the marked third update patch has a mark;

[0127] Step 722 : Based on the presence of a mark on the marked third update patch, update the image of the cloud-native application according to the marked third update patch;

[0128] Step 724: based on the absence of a mark on the marked third update patch, re-mark the marked third update patch, and update the image of the cloud-native application according to the re-marked marked third update patch;

[0129] Step 726: Publish the updated cloud-native application image.

[0130] This embodiment provides a cloud-native application version management method. In addition to the technical features of the above embodiments, this embodiment further includes the following technical features.

[0131] Marking the third update patch includes: preprocessing the third update patch and marking the preprocessed third update patch; wherein the preprocessing includes splitting the third update patch or merging multiple third update patches.

[0132] In this embodiment, after the third update patch is pulled, the third update patch can be split or multiple third update patches can be merged, and the split or merged third update patches can be marked as ready for release. By splitting or merging the third update patch, the impact of cloud-native transformation of traditional application systems on traditional software delivery models can be reduced, reducing the learning curve and workload for R&D, testers, and operations personnel, and lowering version management costs.

[0133] Specifically, if Figure 8 As shown, in this embodiment, the cloud native application version management method includes:

[0134] Step 802: Obtain a first update patch for the cloud native application.

[0135] Step 804 , detecting whether the first update patch conflicts with at least one second update patch of the cloud native application stored in the cloud platform;

[0136] Step 806: storing the first update patch in the cloud platform based on the fact that the first update patch does not conflict with at least one second update patch;

[0137] Step 808: Based on the update instruction of the cloud native application, obtain the version that the cloud native application needs to update;

[0138] Step 810: Obtain a third update patch corresponding to the version required to be updated for the cloud native application according to the version required to be updated for the cloud native application;

[0139] Step 812: Restart the application program interface of the cloud platform;

[0140] Step 814, obtaining the storage address of the third update patch;

[0141] Step 816: Pull the third update patch according to the storage address;

[0142] Step 818: pre-process the third update patch and mark the pre-processed third update patch;

[0143] Step 820: Update the image of the cloud-native application according to the marked third update patch;

[0144] Step 822: Release the updated cloud-native application image.

[0145] The preprocessing includes splitting the third update patch or merging multiple third update patches.

[0146] This embodiment provides a cloud-native application version management method. In addition to the technical features of the above embodiments, this embodiment further includes the following technical features.

[0147] Publishing the updated cloud-native application image includes: calling the first application program interface of the cloud platform to generate the updated cloud-native application image; calling the second application program interface of the cloud platform to push the updated cloud-native application image; calling the third application program interface of the cloud platform to restart the cloud-native application; and the updated cloud-native application image takes effect.

[0148] In this embodiment, the cloud platform invokes its image creation function, which creates a new image from the patched image. The cloud platform then invokes its image push function, which pushes the created new image to the cloud-native application. Finally, the cloud platform invokes its application restart function, which restarts the cloud-native application, making the new image effective and completing the update of the cloud-native application. By completing the image creation, push, and update processes through the cloud platform's multiple application programming interfaces (APIs), the update efficiency of cloud-native applications is improved, the update steps required for cloud-native applications are reduced, the update duration for cloud-native applications is shortened, and the impact of updates on cloud-native applications is mitigated.

[0149] Specifically, if Figure 9 As shown, in this embodiment, the cloud native application version management method includes:

[0150] Step 902: Obtain a first update patch for the cloud native application;

[0151] Step 904 , detecting whether the first update patch conflicts with at least one second update patch of the cloud native application stored in the cloud platform;

[0152] Step 906: storing the first update patch in the cloud platform based on the fact that the first update patch does not conflict with at least one second update patch;

[0153] Step 908: Based on the update instruction of the cloud native application, obtain the version that the cloud native application needs to update;

[0154] Step 910: Obtain a third update patch corresponding to the version required to be updated for the cloud native application according to the version required to be updated for the cloud native application;

[0155] Step 912: Update the image of the cloud-native application according to the third update patch;

[0156] Step 914: Call the first application program interface of the cloud platform to generate an updated image of the cloud native application;

[0157] Step 916: Call the second application programming interface of the cloud platform to push the updated cloud native application image;

[0158] Step 918: Call the third application programming interface of the cloud platform to restart the cloud native application;

[0159] In step 920 , the updated cloud-native application image takes effect.

[0160] An embodiment of the present application also proposes a cloud native application version management system, which is used in a cloud native platform, such as Figure 10 As shown, the management system 1100 includes an acquisition unit 1102, a detection unit 1104 and a storage unit 1106; the acquisition unit 1102 is used to acquire a first update patch for a cloud native application; the detection unit 1104 is used to detect whether the first update patch conflicts with at least one second update patch of a cloud native application stored in the cloud platform; the storage unit 1106 is used to store the first update patch in the cloud platform based on the condition that the first update patch does not conflict with at least one second update patch.

[0161] In this embodiment, by setting an acquisition unit 1102, a first update patch for updating a cloud native application can be obtained. By setting a detection unit 1104, a conflict detection is performed on the first update patch that can be used to update a cloud native application to detect whether the first update patch conflicts with other update patches of the cloud native application that have been stored in the cloud platform. By setting a storage unit 1106, if the first update patch does not conflict with other update patches of the cloud native application, the first update patch for updating the cloud native application is stored in the cloud platform. By performing detection and management of cloud native application patches on the cloud platform, the operator of the cloud native application is prevented from having to operate and maintain the cloud native application version management system on its own, thereby reducing the version management cost of the cloud native application, reducing the operation and maintenance cost of the cloud native application, and thus reducing the cloud native application operation cost borne by the operator of the cloud native application.

[0162] An embodiment of the present application also proposes a cloud native application version management device, such as Figure 11 As shown, the management device 1200 includes a memory 1204 and a processor 1202; the memory 1204 is configured to store programs or instructions; the processor 1202 is configured to execute the stored programs or instructions to implement the steps of the cloud-native application version management method as any one of the above embodiments.

[0163] In this embodiment, since the cloud-native application version management device is configured through processor 1202 to execute stored programs or instructions to implement the steps of the cloud-native application version management method as any one of the above embodiments, the cloud-native application version management device has all the beneficial technical effects of the cloud-native application version management method as any one of the above embodiments, which will not be repeated here.

[0164] An embodiment of the present application also proposes a cloud native application version management device, such as Figure 12 As shown, the management device 1300 includes a patch management module 1310, a file management module 1340, a version management module 1330 and a patch deployment module 1320; wherein, the patch management module 1310 includes a browsing unit 1312, an analysis unit 1314 and a configuration unit 1316; the version management module 1330 includes a deployment unit 1331, a rollback unit 1332, a version recording unit 1333, a conflict analysis unit 1334, an image management unit 1335 and a cloud platform interaction unit 1336; the patch deployment module 1320 includes a pulling unit 1322 and an effectiveness unit 1324.

[0165] In this embodiment, a patch management module 1310, a file management module 1340, a version management module 1330, and a patch deployment module 1320 are provided to enable a cloud-native application patch management system to operate on a cloud platform. By detecting and managing cloud-native application patches on the cloud platform, cloud-native application operators are relieved of the need to independently operate and maintain a cloud-native application version management system, thereby reducing the cost of version management, operation, and maintenance of cloud-native applications, and thereby reducing the operating costs of cloud-native application operators.

[0166] A browsing unit 1312 is configured to obtain a version of the cloud native application that needs to be updated based on an update instruction of the cloud native application;

[0167] The version recording unit 1333 is configured to obtain, according to the version that the cloud native application needs to be updated, a third update patch corresponding to the version that the cloud native application needs to be updated;

[0168] The rollback unit 1332 is configured to use a patch corresponding to the first version as a third update patch when the version to be updated by the cloud native application is the first version;

[0169] The conflict analysis unit 1334 is configured to, when the version to be updated for the cloud-native application is the second version, use the patch corresponding to the second version as the third update patch based on the fact that the second version does not conflict with the first version; and, when the version to be updated for the cloud-native application is the second version, use the patch corresponding to the first version and the patch corresponding to the second version as the third update patch based on the fact that the second version conflicts with the first version;

[0170] The pulling unit 1322 is configured to pull the third update patch according to the storage address;

[0171] An analyzing unit 1314 is configured to pre-process the third update patch;

[0172] The validation unit 1324 is configured to mark the third update patch;

[0173] Configuration unit 1316 is configured to update the image of the cloud native application according to the marked third update patch based on the presence of a mark in the marked third update patch; and re-mark the marked third update patch based on the absence of a mark in the marked third update patch, and update the image of the cloud native application according to the re-marked marked third update patch;

[0174] The image management unit 1335 is configured to update the image of the cloud-native application according to the third update patch;

[0175] A deployment unit 1331 is used to publish the updated cloud native application image;

[0176] The cloud platform interaction unit 1336 is used to call the first application program interface of the cloud platform to generate an updated image of the cloud native application; call the second application program interface of the cloud platform to push the updated image of the cloud native application; and call the third application program interface of the cloud platform to restart the cloud native application.

[0177] An embodiment of the present application also proposes a readable storage medium on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the cloud-native application version management method as described in any of the above embodiments are implemented.

[0178] In this embodiment, a readable storage medium is provided, in which a control program or control instruction is stored. When the control program or control instruction is executed by the processor, the steps of the cloud-native application version management method as described in any one of the above embodiments are implemented. Therefore, the readable storage medium has all the beneficial technical effects of the cloud-native application version management method as described in any one of the above embodiments, which will not be repeated here.

[0179] An embodiment of the present application further proposes a cloud native application patch development method, which is used by patch developers, such as Figure 13 As shown in the figure, cloud-native application patch development methods include:

[0180] Step 1002: Obtain version information of the cloud-native application, and determine the development version of the cloud-native application patch based on the version information of the cloud-native application;

[0181] Step 1004: Download the patch for the version corresponding to the cloud native application;

[0182] Step 1006: confirm the development environment based on the patch of the version corresponding to the cloud native application;

[0183] Step 1008, determine whether it is an incremental patch;

[0184] Step 1010: Based on the incremental patch, a cloud-native application patch is developed using a standard development environment.

[0185] Step 1012: Based on the fact that the patch is not an incremental patch, a cloud-native application patch is developed using a development environment corresponding to the patch of the corresponding version of the cloud-native application.

[0186] Step 1014: Export the cloud native application patch to the development environment;

[0187] Step 1016: Upload the cloud native application patch.

[0188] In this embodiment, a cloud native application patch development method is provided. The patch development method is used for patch developers to develop cloud native application patches. Before developing the patch, it is necessary to obtain the version information currently used by the cloud native application, determine the patch version to be developed based on the obtained version information, download the patch used by the current version of the cloud native application, and determine whether it is an incremental patch based on the patch used by the current version. If it is an incremental patch, the developed patch will not modify the content of the patch used by the current version, and the standard patch development environment can be used to develop the patch. If it is not an incremental patch, the developed patch will modify the content of the patch used by the current version, and the patch development environment needs to be set to the development environment corresponding to the patch used by the current version. When the patch development is completed, the patch is exported from the patch development environment and the patch is uploaded. When using the cloud native application patch development method of this application, the version information of the patch is determined by the version information of the cloud native application, which can improve the matching effect between the patch and the cloud native application and improve the adaptability of the patch. In addition, by downloading the patches currently in use for cloud-native applications and confirming whether the newly developed patches need to modify the content of the patches in use based on the patches in use, the development environment to be used can be determined, reducing the chance of errors or version conflicts when using patches due to mismatched development environments, further improving the adaptability of patches, and improving the stability and reliability of patches when used.

[0189] In the claims, specification and drawings of the present invention, the term "plurality" refers to two or more. Unless otherwise expressly defined, the orientation or positional relationship indicated by the terms "upper" and "lower" is based on the orientation or positional relationship shown in the drawings. It is only for the purpose of more conveniently describing the present invention and making the description process simpler. It is not intended to indicate or imply that the device or element referred to must have the specific orientation described, be constructed and operated in a specific orientation. Therefore, these descriptions cannot be understood as limiting the present invention. The terms "connect", "install", "fix" and the like should be understood in a broad sense. For example, "connection" can be a fixed connection between multiple objects, or a detachable connection between multiple objects, or an integral connection; it can be a direct connection between multiple objects, or an indirect connection between multiple objects through an intermediate medium. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood based on the specific circumstances of the above data.

[0190] In the claims, specification, and drawings of the present invention, the terms "one embodiment," "some embodiments," "a specific embodiment," and the like mean that the specific features, structures, materials, or characteristics described in conjunction with that embodiment or example are included in at least one embodiment or example of the present invention. In the claims, specification, and drawings of the present invention, schematic representations of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.

[0191] The foregoing description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Those skilled in the art will readily appreciate that various modifications and variations of the present invention are possible. Any modifications, equivalent substitutions, or improvements made within the spirit and principles of the present invention are intended to be within the scope of protection of the present invention.

Claims

1. A cloud native application version management method, characterized in that: The cloud-native application version management method is used for a cloud-native platform, and the cloud-native application version management method includes: Get the first update patch for cloud-native applications; detecting whether the first update patch conflicts with at least one second update patch of a cloud native application stored in the cloud platform; storing the first update patch in the cloud platform based on the fact that the first update patch does not conflict with the at least one second update patch; Based on the update instructions of the cloud-native application, obtain the version that the cloud-native application needs to update; According to the version of the cloud native application that needs to be updated, obtain a third update patch corresponding to the version of the cloud native application that needs to be updated; Updating the image of the cloud-native application according to the third update patch; The third update patch is at least one of the first update patch and the at least one second update patch; Release the updated image of the cloud-native application; The method includes: calling a first application program interface (API) of the cloud platform to generate an updated image of the cloud native application; calling a second application program interface (API) of the cloud platform to push the updated image of the cloud native application; calling a third application program interface (API) of the cloud platform to restart the cloud native application; and the updated image of the cloud native application takes effect. Updating the image of the cloud-native application according to the third update patch includes: Restarting the application program interface of the cloud platform; Obtaining the storage address of the third update patch; Pulling the third update patch according to the storage address; Marking the third update patch; Updating the image of the cloud-native application according to the marked third update patch; The marking of the third update patch includes: pre-processing the third update patch and marking the pre-processed third update patch; The preprocessing includes splitting the third update patch or merging multiple third update patches.

2. The cloud native application version management method according to claim 1, characterized in that: In the event that the first update patch conflicts with the second update patch, patch conflict prompt information is sent to a patch developer.

3. The cloud native application version management method according to claim 1, characterized in that: The obtaining, according to the version that the cloud native application needs to be updated, a third update patch corresponding to the version that the cloud native application needs to be updated includes: When the version that needs to be updated for the cloud-native application is the first version, the patch corresponding to the first version is used as the third update patch; The first version is the previous version of the version corresponding to the cloud native application.

4. The cloud native application version management method according to claim 3, characterized in that: The step of obtaining, according to the version that the cloud native application needs to be updated, a third update patch corresponding to the version that the cloud native application needs to be updated further includes: When the version that needs to be updated for the cloud-native application is the second version, based on the fact that the second version does not conflict with the first version, a patch corresponding to the second version is used as the third update patch; When the version that the cloud-native application needs to update is the second version, based on the conflict between the second version and the first version, the patch corresponding to the first version and the patch corresponding to the second version are used as the third update patch; The second version is at least a previous version of the first version.

5. The cloud native application version management method according to claim 1, characterized in that: Updating the image of the cloud-native application according to the marked third update patch includes: Based on the existence of a mark on the marked third update patch, executing the method of updating the image of the cloud native application according to the marked third update patch; Based on the fact that the marked third update patch does not have a mark, the marked third update patch is re-marked, and the image of the cloud-native application is updated according to the re-marked marked third update patch.

6. A cloud native application version management system, characterized in that: The cloud-native application version management system is used for the cloud-native platform, and the cloud-native application version management system includes: an acquisition unit, configured to acquire a first update patch for a cloud-native application; a detection unit, configured to detect whether the first update patch conflicts with at least one second update patch of a cloud native application stored in the cloud platform; a storage unit, configured to store the first update patch in the cloud platform based on the condition that the first update patch does not conflict with the at least one second update patch; A browsing unit is used to obtain the updated version of the cloud native application based on the update instruction of the cloud native application; A version recording unit, configured to obtain, according to the version required to be updated for the cloud native application, a third update patch corresponding to the version required to be updated for the cloud native application; an image management unit, configured to update the image of the cloud-native application according to the third update patch; The third update patch is at least one of the first update patch and the at least one second update patch; A deployment unit, configured to release an updated image of the cloud-native application; The method includes: calling a first application program interface (API) of the cloud platform to generate an updated image of the cloud native application; calling a second application program interface (API) of the cloud platform to push the updated image of the cloud native application; calling a third application program interface (API) of the cloud platform to restart the cloud native application; and the updated image of the cloud native application takes effect. The image management unit is specifically configured to restart the application program interface of the cloud platform; obtain the storage address of the third update patch; pull the third update patch according to the storage address; mark the third update patch; and update the image of the cloud native application according to the marked third update patch; The marking of the third update patch includes: pre-processing the third update patch and marking the pre-processed third update patch; The preprocessing includes splitting the third update patch or merging multiple third update patches.

7. A cloud native application version management device, characterized in that: include: a memory configured to store programs or instructions; A processor configured to execute stored programs or instructions to implement the steps of the cloud-native application version management method according to any one of claims 1 to 5.

8. A readable storage medium having a program or instruction stored thereon, characterized in that: When the program or the instruction is executed by the processor, the steps of the cloud-native application version management method according to any one of claims 1 to 5 are implemented.

Images