CN111176713A - Gray scale publishing and arranging method based on Kubernetes platform and Istio grid technology - Google Patents
Gray scale publishing and arranging method based on Kubernetes platform and Istio grid technology Download PDFInfo
- Publication number
- CN111176713A CN111176713A CN201911226935.0A CN201911226935A CN111176713A CN 111176713 A CN111176713 A CN 111176713A CN 201911226935 A CN201911226935 A CN 201911226935A CN 111176713 A CN111176713 A CN 111176713A
- Authority
- CN
- China
- Prior art keywords
- service
- version
- traffic
- gray
- istio
- 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.)
- Withdrawn
Links
Images
Classifications
-
- 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1433—Saving, restoring, recovering or retrying at system level during software upgrading
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/085—Retrieval of network configuration; Tracking network configuration history
- H04L41/0859—Retrieval of network configuration; Tracking network configuration history by keeping history of different configuration generations or by rolling back to previous configuration versions
- H04L41/0863—Retrieval of network configuration; Tracking network configuration history by keeping history of different configuration generations or by rolling back to previous configuration versions by rolling back to previous configuration versions
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Software Systems (AREA)
- Quality & Reliability (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a gray release arrangement method based on a Kubernets platform and an Istio grid technology, which utilizes the characteristics of virtual service virtualService and target rule destinationRule module of the Istio and the label characteristics of kubernets, adopts a helm release tool to flexibly generate a deployment template of the kubernets and the related attribute value of a dynamic control template to dynamically and smoothly schedule the flow of a micro-service AB version in the kubernets cluster, and quickly and stably realizes smooth gray release, thereby solving the test cost of testers and reducing the range of influencing services.
Description
Technical Field
The invention relates to the technical field of cloud computing and infrastructure, in particular to a gray scale publishing and arranging method based on a Kubernetes platform and an Istio grid technology.
Background
A service grid (ServiceMesh) is used to describe the micro-service networks that make up such applications and the interactions between them. As the size and complexity of the services grid grows, it becomes increasingly difficult to understand and manage. Its requirements may include discovery, load balancing, fault recovery, indexing and monitoring. Service grids also typically have more complex operational requirements such as A/B testing, golden silk pushing, rate limiting, access control and end-to-end identity verification, and Istio provides behavioral insights and operational control throughout the service grid, thereby providing a complete solution to meet the various needs of microservice applications.
Kubernets is an open source platform that can automate Linux container operations. It can help us to omit many manual deployment and expansion operations of the application containerization process. That is, we can cluster together groups of hosts running Linux containers, and kubernets helps you easily and efficiently manage these clusters. Moreover, these clusters may deploy hosts across public, private, or hybrid clouds. Therefore, kubernets is an ideal hosting platform for cloud-native applications that require rapid expansion.
Gray scale distribution refers to a distribution method that can smoothly transition between black and white. If the user has no problem in the test of the version B, the flow range is gradually expanded, and all the users are migrated to the version B. Just so, the stability of whole system can be guaranteed in grey scale release, just can discover, debug the problem in initial grey scale to guarantee its influence degree.
In the process of project iteration, project online is inevitably required, service change is frequent, the release period is short, speed and quality are always difficult to achieve, testing work on the project excessively depends on testers, a data structure is required to be constructed manually for offline testing, risks and influences brought to release are increased, local gray scale release is achieved by using gateway technologies similar to ingress-nginx and trafik, some are complex, the switching of services is not smooth enough in the release process, a large influence range is caused on the services, partial functions can also need extra development workload, flexibility is lacked, safety of enterprise data and the like.
How to rapidly realize smooth release of the Kubernets platform micro-service gray scale is a main problem to be solved by the invention, which not only reduces code intrusion and development cost, but also is safe and reliable.
Disclosure of Invention
The technical problem to be solved by the invention is to provide a gray release arrangement method based on Istio micro-service grid real Kubernets platform service smoothness, which can quickly realize coexistence of multiple versions of online services and flexibly schedule flow of different versions, thereby realizing gray release of services, further reducing the risk of daily iteration update and release of kubernets platform micro-services and reducing the range of influence on the services; in addition, the dependence on testers is reduced, the data construction cost of offline self-test is reduced, the quick rollback of the service can be realized, and the stability of the service is ensured.
The invention adopts the following technical scheme for solving the technical problems:
a gray release arrangement method based on Kubernetes platform and Istio grid technology specifically comprises the following steps;
step 1, respectively creating two charts release list files of the example microservice A, wherein the files comprise prod-dp
The method comprises the following steps of (1) gray-dp.yml, service.yml and value.yml, wherein files of rod-dp.yml and gray-dp.yml are deployment objects in kubbernees, service.yml is a service object exposing micro service A, value.yml is a dynamic regulation and control configuration file issued by the gray scale, and the files can be flexibly scheduled through the helm;
step3, deploying a micro service new version v2 to a kubernets cluster by using a Helm charts mode;
step 4, configuring destinationRule objects of the istio service, and adding and injecting new versions v2 to subsets of the micro service;
step 5, configuring a virtualservice object module of the istio service, and routing all service traffic in an initial stable state to a production version by modifying the traffic weight and copy number of the production version and a new version in a value.yml configuration file of the hell and a tag version of a mirror image;
step 6, modifying the weight value of weight of a new version 10 in the real. yml of the hem by configuring a virtaulacervice object template of the Micro service idio service, wherein the number of copies is 2, namely distributing 10% of service traffic to a new version v2, and testing the service effect of the 10% of traffic at the moment;
step 7, adding the service flow to the new version v2, namely configuring a virtauervice object template of the istio and modifying the weight value 90 of the new version weight value in value.ym, wherein the copy is unchanged, namely distributing 90% of the service flow to route to the new version v2, and testing the service effect of the 90% of the flow at the moment;
step 8, adding all the service flows to the new version v2, namely adjusting the weight of the new version in the value. yml configuration file to be 100, keeping the copy number unchanged, and routing 100% of the service flows to the new version v2 by the weight value of the weight of the version 0, namely, distributing the 100% of the service flows, and at the moment, testing the service effect of the 100% of the flows by service personnel;
step 9, like step 8, modifying the weight of the production version in the vault. yml configuration file to be 100, keeping the copy number unchanged, and keeping the mirror version to be v2, and routing 100% of service traffic to the new version v2, with the weight of the new version being 0 and the copy number being 0, until the release is completed.
As a further preferable scheme of the gray scale publishing and arranging method based on the Kubernets platform and the Istio grid technology, Micro services are packaged into separate Helm charts and are deployed in a kubernets cluster.
As a further preferable scheme of the Gray scale publishing and arranging method based on the kubernets platform and the isotio grid technology, the application a is labeled, and the main difference between the product deployment file and the Gray deployment file is that the Gray label value of Pod deployed by the product is false, the Gray label value of Pod deployed by the Gray is True, and the other difference is that in a stable state, the number of copies deployed by the Gray version is 0, so that there is no Pod deployed by the Gray in the stable state.
As a further preferable scheme of the gray release arrangement method based on the kubernets platform and the isotio grid technology, the step3 deploys the micro service new version v2 to the kubernets cluster by using a Helm charts mode, and specifically includes five stages as follows:
phase 1, in release, with 2 copies of v2 and v2 version of the application, tg labeled v2, 10% of the traffic is routed to v2 version, 90% of the traffic is routed to production version v 1;
adjusting the new version of the traffic value, wherein 90% of the traffic is routed to the v2 version deployment service, and 10% of the traffic is routed to the production version v1 service;
stage 3, helm operation value, routing 100% of traffic into the v2 version of micro service;
stage 4, rolling and updating the product version Pod to the application program of the new version, tg being changed to v2, and simultaneously routing 100% of traffic to the deployment Pod;
Compared with the prior art, the invention adopting the technical scheme has the following technical effects:
1. the release speed of the application is increased, and the error rate of manual release is checked;
2. the influence on user experience and the influence range of service in the process of releasing the application are reduced;
3. the dependence on testing personnel is reduced, and the data construction cost of offline self-testing is reduced;
3. if a fault occurs after release, the service can be quickly rolled back to the previous version, and the quick self-healing capability of the online service is ensured.
Drawings
Fig. 1 is a deployment profile, yml and service, yml, of the Mirco service in kubernets in the present invention;
FIG. 2 is a schematic diagram of a configuration file of a micro service in an istio injection version in the invention;
FIG. 3 is a schematic diagram of a configuration file for gray scale publishing flow weight control of istio in the present invention;
FIG. 4 is a dynamic profile of the helm operation and orchestration step 1 of smooth gray release;
FIG. 5 is a dynamic profile of the helm operation and orchestration step 2 of smooth gray scale distribution;
FIG. 6 is a diagram of an arrangement process for implementing the gray release of kubernets platform services based on the Istio micro-service grid according to the present invention.
Detailed Description
The technical scheme of the invention is further explained in detail by combining the attached drawings:
the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be obtained by a person skilled in the art without any inventive step based on the embodiments of the present invention, are within the scope of the present invention
In order to solve the technical problems, the invention provides a smooth gray release arrangement method based on an Istio micro-service grid real kubernets platform service, which can quickly realize the coexistence of multiple versions of online services and flexibly schedule the flow of different versions, thereby realizing the gray release of the service, further reducing the risks of daily iteration update and release of the kubernets platform micro-service and reducing the range of influencing the service; in addition, the dependence on testers is reduced, the data construction cost of offline self-test is reduced, the rapid rollback of the service can be realized, and the stability of the service is ensured, as shown in fig. 6.
A smooth gray release arrangement method based on an Istio micro-service grid real-kubernets platform service utilizes the characteristics of Istio virtual service (virtual service) and target rule (destinationRule) modules and the label characteristics of kubernets, adopts a helm release tool to flexibly generate a deployment template of the kubernets and the related attribute values of a dynamic control template to dynamically and smoothly schedule the flow of a micro-service AB version in a kubernets cluster, and quickly and stably realizes smooth gray release, so that the test cost of testers is reduced, and the range of influencing the service is reduced.
Fig. 1 is a deployment profile, yml and service, yml, of the Mirco service in kubernets in the present invention; FIG. 2 is a schematic diagram of a configuration file of a micro service in an istio injection version in the invention; FIG. 3 is a schematic diagram of a configuration file for gray scale publishing flow weight control of istio in the present invention; fig. 4-5 are the dynamic profile of the helm operation and the orchestration steps of smooth gray scale distribution.
Further comprising the steps of:
as shown in fig. 1, Micro services are packaged as separate hellm charts, deployed in a kubernets cluster.
As shown in fig. 1, the main difference between the production deployment file and the Gray deployment file is that the Gray tag value of Pod of the production deployment is false, and the Gray tag value of Gray deployment Pod is True. Another difference is that in steady state, the number of copies of the gray version deployment is 0, so there is no Pod of the gray deployment in steady state.
As shown in FIG. 5, phase 1, steady state, 100% traffic for a production deployment with the current v1 version application. There is no ongoing version, grayscale version v1 deployments have 0 copies, and no traffic is routed to the grayscale deployment container
As shown in fig. 5, phase 2, in release, has 2 copies of v2 and a v2 version of the application (tg labeled v 2). 10% of the traffic is routed to version v2 and 90% to production version v1.
As shown in fig. 5, phase 3, the helm adjusts traffic to a new version v2, 90% of the traffic is routed into the v2 version deployment service, and 10% of the traffic is routed into the production version v1 service.
As shown in fig. 5, phase 4, followed by the helm operation value, routes 100% of the traffic into the v2 version of the micro service.
As shown in fig. 5, phase 5 updates the roll of production deployment Pod to the new version v2 of the application (tg mark v2) while routing 100% of the traffic to the greyscale version v2 deployment Pod. This step needs to be performed before routing traffic back to the production deployment pod.
As shown in FIG. 5, stage 6, 100% of the traffic is switched back to production version v2, when the pod of the production deployment has the latest version v2 of the application.
As shown in FIG. 5, stage 7, the new steady state, the count of the gram version copy is again modified to 0, the production deployment Pod has processed 100% of the traffic, and the production Pod now has the latest application version (container image label v2)
We can use the helm command to roll back to the previous version v1 (phase 1) of the application in any phase, with roll-back in any phase
Wherein, the basic environment construction steps that above technical scheme involved are as follows:
setp 1: the service grid Istio has been installed on the kubernets cluster;
setp 2: installing an open source kubernets release tool (helm v 3);
step 3: each Micro service should be packaged as a separate Helm charts;
1) as shown in fig. 1, two charts release list files of the exemplary microservice a are respectively created, including (pro-dp.yml, gray-dp.yml, service.yml, and value.yml), where the pro-dp.yml and the gray-dp.yml files are deployment objects in kubberenets, the service.yml is a service object exposing the microservice a, and the value.yml is a dynamic regulation configuration file of this time of gray release, and the files are flexibly scheduled through hell.
And (3) a destinationRule object template corresponding to istio of the micro service is configured, and a production version v1 is annotated into subsets, so that the later gray scale release scheduling is facilitated.
The same Helm charts method is used for deploying the new micro service version (v2) into the kubernets cluster.
Next, the destinationRule object of the istio is configured, added and injected into subsets of the micro service according to the v2 version.
Configure virtauervice of istio and route all traffic initially in steady state to production version by modifying traffic weight and copy number of production version and new version in value.
5) By configuring a virtauervice object template of Micro service istio, a weight value of 10 of weight of a new version in yml of vacuum of hem is modified, the number of copies is 2, namely 10% of service traffic is distributed to be routed to the new version (v2), and at the moment, the service effect of the 10% of traffic can be tested.
6) Next, we continue to add the traffic to the new version (v2), that is, configure virtualservice object template of istio and modify weight value 90 of the new version in value.ym, and the copy is unchanged, that is, 90% of the traffic is distributed and routed to the new version (v2), at this time, the traffic effect of the 90% of the traffic can be tested.
7) Further, step 6) adds all the service flows to the new version (v2), that is, the weight of the new version in the value. yml configuration file is adjusted to 100, the number of copies is unchanged, and the weight value of the weight of the version is 0, that is, 100% of the service flows are distributed to be routed to the new version (v2), at this time, the service personnel tests the service effect of the 100% of the flows.
8) And finally, as in step 7), finally modifying the weight of the production version in the vacuum. yml configuration file to be 100, keeping the copy number unchanged, and setting the mirror version to be v2, and setting the weight of the new version to be 0 and the copy number to be 0, namely, routing 100% of service traffic to the new version (v2) until the release is completed.
After each stage, a manual judgment is needed to enter the next release stage, and if an exception occurs, the application program can be quickly rolled back to the previous production version of the application program in the same way of Helm Charts at each stage. ,
it will be understood by those skilled in the art that, unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the prior art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
The above embodiments are only for illustrating the technical idea of the present invention, and the protection scope of the present invention is not limited thereby, and any modifications made on the basis of the technical scheme according to the technical idea of the present invention fall within the protection scope of the present invention. While the embodiments of the present invention have been described in detail, the present invention is not limited to the above embodiments, and various changes can be made without departing from the spirit of the present invention within the knowledge of those skilled in the art.
Claims (4)
1. A gray release arrangement method based on Kubernetes platform and Istio grid technology is characterized in that
The method comprises the following steps: the method specifically comprises the following steps;
step 1, respectively creating two charts release list files of the example microservice A, wherein the files comprise prod-dp
The method comprises the following steps of (1) gray-dp.yml, service.yml and value.yml, wherein files of rod-dp.yml and gray-dp.yml are deployment objects in kubbernees, service.yml is a service object exposing micro service A, value.yml is a dynamic regulation and control configuration file issued by the gray scale, and the files can be flexibly scheduled through the helm;
step 2, configuring a destinationRule object template of a micro service corresponding to istio, and injecting a production version v1 into subsets for gray release scheduling;
step3, deploying a micro service new version v2 to a kubernets cluster by using a Helm charts mode;
step 4, configuring destinationRule objects of the istio service, and adding and injecting new versions v2 to subsets of the micro service;
step 5, configuring a virtualservice object module of the istio service, and routing all service traffic in an initial stable state to a production version by modifying the traffic weight and copy number of the production version and a new version in a value.yml configuration file of the hell and a tag version of a mirror image;
step 6, modifying the weight value of weight of a new version 10 in the real. yml of the hem by configuring a virtaulacervice object template of the Micro service idio service, wherein the number of copies is 2, namely distributing 10% of service traffic to a new version v2, and testing the service effect of the 10% of traffic at the moment;
step 7, adding the service flow to the new version v2, namely configuring a virtauervice object template of the istio and modifying the weight value 90 of the new version weight value in value.ym, wherein the copy is unchanged, namely distributing 90% of the service flow to route to the new version v2, and testing the service effect of the 90% of the flow at the moment;
step 8, adding all the service flows to the new version v2, namely adjusting the weight of the new version in the value. yml configuration file to be 100, keeping the copy number unchanged, and routing 100% of the service flows to the new version v2 by the weight value of the weight of the version 0, namely, distributing the 100% of the service flows, and at the moment, testing the service effect of the 100% of the flows by service personnel;
step 9, like step 8, modifying the weight of the production version in the vault. yml configuration file to be 100, keeping the copy number unchanged, and keeping the mirror version to be v2, and routing 100% of service traffic to the new version v2, with the weight of the new version being 0 and the copy number being 0, until the release is completed.
2. The gray scale publishing and arranging method based on the Kubernets platform and the Istio grid technology according to claim 1, wherein: in one embodiment, Micro services are packaged as individual Helm charts deployed in a kubernets cluster.
3. The gray scale publishing and arranging method based on the Kubernets platform and the Istio grid technology according to claim 1, wherein: in one embodiment, the a application is tagged, and the main difference between the product deployment file and the Gray deployment file is that the Gray tag value of Pod deployed by product is false, while the Gray tag value of Pod deployed by Gray is True, and another difference is that in steady state, the number of copies deployed by the Gray version is 0, so there is no Pod deployed by Gray in steady state.
4. The gray scale publishing and arranging method based on the Kubernets platform and the Istio grid technology according to claim 1, wherein: in one embodiment, the step3 deploys the micro service new version v2 to the kubernets cluster by using a Helm charts method, which specifically includes five stages as follows:
phase 1, in release, with 2 copies of v2 and v2 version of the application, tg labeled v2, 10% of the traffic is routed to v2 version, 90% of the traffic is routed to production version v 1;
adjusting the new version of the traffic value, wherein 90% of the traffic is routed to the v2 version deployment service, and 10% of the traffic is routed to the production version v1 service;
stage 3, helm operation value, routing 100% of traffic into the v2 version of micro service;
stage 4, rolling and updating the product version Pod to the application program of the new version, tg being changed to v2, and simultaneously routing 100% of traffic to the deployment Pod;
phase 5, 100% of the traffic is switched back to production version v 2.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911226935.0A CN111176713A (en) | 2019-12-04 | 2019-12-04 | Gray scale publishing and arranging method based on Kubernetes platform and Istio grid technology |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911226935.0A CN111176713A (en) | 2019-12-04 | 2019-12-04 | Gray scale publishing and arranging method based on Kubernetes platform and Istio grid technology |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111176713A true CN111176713A (en) | 2020-05-19 |
Family
ID=70650123
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911226935.0A Withdrawn CN111176713A (en) | 2019-12-04 | 2019-12-04 | Gray scale publishing and arranging method based on Kubernetes platform and Istio grid technology |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111176713A (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112732274A (en) * | 2021-01-08 | 2021-04-30 | 上海汇付数据服务有限公司 | Container application issuing method and management platform based on gray level issuing |
| CN112905210A (en) * | 2021-03-24 | 2021-06-04 | 青岛聚看云科技有限公司 | Server and gray scale publishing method |
| CN112988394A (en) * | 2021-04-20 | 2021-06-18 | 北京世纪好未来教育科技有限公司 | Business service publishing method, device, medium and equipment based on cloud native container |
| CN114064062A (en) * | 2022-01-17 | 2022-02-18 | 北京快成科技有限公司 | Kubernetes platform and load balancing component-based default gray level issuing method and device |
| CN114205280A (en) * | 2021-11-17 | 2022-03-18 | 广州云擎互动信息技术有限公司 | Application publishing method and flow routing method based on container cloud and service grid |
| CN114706611A (en) * | 2022-04-19 | 2022-07-05 | 广域铭岛数字科技有限公司 | Version management method, system, electronic device and medium |
-
2019
- 2019-12-04 CN CN201911226935.0A patent/CN111176713A/en not_active Withdrawn
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112732274A (en) * | 2021-01-08 | 2021-04-30 | 上海汇付数据服务有限公司 | Container application issuing method and management platform based on gray level issuing |
| CN112905210A (en) * | 2021-03-24 | 2021-06-04 | 青岛聚看云科技有限公司 | Server and gray scale publishing method |
| CN112905210B (en) * | 2021-03-24 | 2023-09-15 | 青岛聚看云科技有限公司 | Server and gray level publishing method |
| CN112988394A (en) * | 2021-04-20 | 2021-06-18 | 北京世纪好未来教育科技有限公司 | Business service publishing method, device, medium and equipment based on cloud native container |
| CN112988394B (en) * | 2021-04-20 | 2021-08-17 | 北京世纪好未来教育科技有限公司 | Business service publishing method, device, medium and equipment based on cloud native container |
| CN114205280A (en) * | 2021-11-17 | 2022-03-18 | 广州云擎互动信息技术有限公司 | Application publishing method and flow routing method based on container cloud and service grid |
| CN114205280B (en) * | 2021-11-17 | 2023-03-31 | 广州云擎互动信息技术有限公司 | Application publishing method and flow routing method based on container cloud and service grid |
| CN114064062A (en) * | 2022-01-17 | 2022-02-18 | 北京快成科技有限公司 | Kubernetes platform and load balancing component-based default gray level issuing method and device |
| CN114064062B (en) * | 2022-01-17 | 2022-05-13 | 北京快成科技有限公司 | Kubernetes platform and load balancing component-based default gray level issuing method and device |
| CN114706611A (en) * | 2022-04-19 | 2022-07-05 | 广域铭岛数字科技有限公司 | Version management method, system, electronic device and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111176713A (en) | Gray scale publishing and arranging method based on Kubernetes platform and Istio grid technology | |
| US11093227B1 (en) | Computer-automated software release and deployment architecture | |
| US9703660B2 (en) | Testing a virtualized network function in a network | |
| WO2020017847A1 (en) | Method for provisioning and managing multi-cluster on cloud platform | |
| US10303450B2 (en) | Systems and methods for a policy-driven orchestration of deployment of distributed applications | |
| CN106790483A (en) | Hadoop group systems and fast construction method based on container technique | |
| Casazza et al. | Securing virtual network function placement with high availability guarantees | |
| CN103109275A (en) | Systems, methods and apparatus using virtual appliances in a semiconductor test environment | |
| CN112099917B (en) | Regulation and control system containerized application operation management method, system, equipment and medium | |
| CN110389766B (en) | HBase container cluster deployment method, system, equipment and computer readable storage medium | |
| Svorobej et al. | Orchestration from the Cloud to the Edge | |
| CN104461693A (en) | Virtual machine updating method and virtual machine updating system under desktop cloud computing environment | |
| CN105893545A (en) | Efficient Hadoop cluster deployment method | |
| CA3006099A1 (en) | Automatic display unit backup during failures of one more display units through the utilization of graphic user interface objects defined for control transfer and reversion after resolution of the failures | |
| CN106528170A (en) | Software package release method and system based on multi-language environment | |
| CN110858356A (en) | Manufacturing execution system based on micro-service architecture | |
| CN107294771A (en) | A kind of efficient deployment system and application method suitable for big data cluster | |
| CN113918276A (en) | SDN controller deployment method, device and medium based on container | |
| Rafiq et al. | Intent-Based Slicing between Containers in SDN Overlay Network. | |
| CN112486630A (en) | Distributed training deployment system and method thereof | |
| CN106909197B (en) | Virtualization host time management method and virtualization host system | |
| Dobaj et al. | Towards digital twin-enabled DevOps for CPS providing architecture-based service adaptation & verification at runtime | |
| EP4369183A1 (en) | Cloud platform management architecture, method and device, and storage medium | |
| CN110784347A (en) | Node management method, system, equipment and storage medium for container cluster | |
| CN116243930A (en) | Multi-version parallel environment design method and construction system |
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 | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20200519 |
|
| WW01 | Invention patent application withdrawn after publication |