CN117215596A - Helm-based gray level publishing method and device, electronic equipment and medium - Google Patents
Helm-based gray level publishing method and device, electronic equipment and medium Download PDFInfo
- Publication number
- CN117215596A CN117215596A CN202310968557.3A CN202310968557A CN117215596A CN 117215596 A CN117215596 A CN 117215596A CN 202310968557 A CN202310968557 A CN 202310968557A CN 117215596 A CN117215596 A CN 117215596A
- Authority
- CN
- China
- Prior art keywords
- gray
- project
- information
- gray level
- release
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 241000380131 Ammophila arenaria Species 0.000 title claims abstract description 33
- 238000000034 method Methods 0.000 title claims abstract description 32
- 238000012795 verification Methods 0.000 claims abstract description 39
- 235000014510 cooky Nutrition 0.000 claims description 18
- 230000011218 segmentation Effects 0.000 claims description 17
- 238000004590 computer program Methods 0.000 claims description 12
- 238000004806 packaging method and process Methods 0.000 claims description 5
- 238000012216 screening Methods 0.000 claims description 5
- 230000004083 survival effect Effects 0.000 claims description 3
- 241001270131 Agaricus moelleri Species 0.000 claims description 2
- 238000005096 rolling process Methods 0.000 claims description 2
- 238000012360 testing method Methods 0.000 abstract description 6
- 238000011084 recovery Methods 0.000 abstract description 3
- 238000004891 communication Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000003631 expected effect Effects 0.000 description 3
- 238000012856 packing Methods 0.000 description 3
- 238000010276 construction Methods 0.000 description 2
- 230000018109 developmental process Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000036541 health Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application discloses a gray level release method, a device, electronic equipment and a medium based on Helm, wherein the method comprises the steps of obtaining gray level configuration information and item codes for gray level release; according to the gray configuration information and the project codes, deploying the project gray environment clusters in a helm mode to obtain gray environment clusters; acquiring a gray level release rule; acquiring user request information, controlling user traffic to route to a gray environment cluster according to gray release rules and the user request information, performing gray release verification, and collecting user feedback data; and determining a gray verification result according to the user feedback data. The application can reduce the risk brought by problems existing in iteration update of the new version to the project, flexibly select the user to participate in the test of the new version of the project, has certain disaster recovery capability, can avoid service halt brought by global release to the project or access different risks, and improves the experience of the user. The method is widely applied to the technical field of project release.
Description
Technical Field
The application relates to the technical field of project release, in particular to a gray level release method, device, electronic equipment and medium based on Helm.
Background
With the development of internet technology, users have increasingly high demands on application software. To accommodate technology updates and user needs, developers often need to constantly update versions, and accordingly, software development processes need to be constantly tested.
If the new version of the application software is directly tested by using the global release mode, different risks of user access are easily brought, inconvenience is caused to the user, and meanwhile, the technical problem of iterative update of the new version is also easy to bring the risk of service shutdown to the application software.
Disclosure of Invention
In order to solve at least one technical problem in the related art, an embodiment of the application provides a gray level publishing method, a gray level publishing device, an electronic device and a medium based on Helm.
A first aspect of an embodiment of the present application provides a hell-based gray level distribution method, where the method includes:
acquiring gray configuration information and item codes for gray release;
according to the gray configuration information and the project codes, deploying a project gray environment cluster in a helm mode to obtain a gray environment cluster;
acquiring a gray level release rule; the gray level release rule is used for screening user traffic routed to the gray level environment cluster;
acquiring user request information, controlling user traffic to be routed to the gray environment cluster according to the gray release rule and the user request information, performing gray release verification, and collecting user feedback data;
and determining a gray verification result according to the user feedback data.
In some embodiments, the method further comprises:
and judging whether the gray environment cluster is added to a project formal cluster according to the gray verification result.
In some embodiments, the step of obtaining the gray scale configuration information, deploying the gray scale environment cluster of the project by adopting a helm mode, and obtaining the gray scale environment cluster specifically includes:
generating a gray scale configuration environment according to the gray scale configuration information;
packaging the item codes to generate gray item codes;
and according to the gray level project codes, deploying project gray level environment clusters in the gray level configuration environment in a helm mode to obtain the gray level environment clusters.
In some embodiments, the gray level distribution rule includes a cookie segmentation flow rule, a header segmentation flow rule, and a weight segmentation flow rule, and the step of obtaining the gray level distribution rule specifically includes:
acquiring project business demand information;
and selecting the gray level release rule according to the project service demand information, and determining the gray level release rule.
In some embodiments, the cookie segmentation traffic rule is specifically:
acquiring cookie information in the user request information;
when the cookie information contains gray scale identification information, controlling the user traffic to be routed to the gray scale environment cluster;
when the cookie information does not contain gray identification information, controlling the user traffic to be routed to the project formal cluster;
the header segmentation flow rule specifically comprises the following steps:
acquiring header information in the user request information;
when gray scale identification information exists in the header information, controlling user traffic to be routed to the gray scale environment cluster;
when the gray scale identification information does not exist in the header information, controlling the user flow to route to the project formal cluster;
the weight segmentation flow rule specifically comprises the following steps:
acquiring gray percentage information, and distributing the gray percentage information to the user request information;
and controlling the user traffic to be routed to the gray environment cluster according to the gray percentage information.
In some embodiments, the step of deploying a project gray environment cluster in the gray configuration environment according to the gray project code by a helm manner to obtain the gray environment cluster specifically includes:
determining project basic information corresponding to the gray project code aiming at the gray project code; the project basic information comprises project naming information, project version information and an address of a project chart warehouse;
acquiring gray release parameters, executing assignment operation, assigning the gray release parameters to corresponding first variables, and updating variable values of the first variables; the first variable is a variable in a palm variable file; the first variable comprises the number of item instances pod, item deployment selection server parameters, item domain names and certificate related parameters, item container ports, item mirror addresses, survival check related parameters, item container resource limit related parameters, rolling update related parameters and storage mounting related parameters;
and according to the gray scale item codes and the variable values of the first variables, deploying the gray scale environment clusters and releasing gray scales.
In some embodiments, the step of determining whether to add the gray environment cluster to the project formal cluster according to the gray verification result specifically includes:
when the gray level verification result is that the gray level verification is successful, adding the gray level environment cluster into the project formal cluster, deleting the gray level release rule, and off-line the gray level environment cluster;
and deleting the gray level release rule and off-line the gray level environment cluster when the gray level verification result is that the gray level verification fails.
A second aspect of an embodiment of the present application provides a gray scale distribution device based on Helm, including:
the first module is used for acquiring gray configuration information and project codes for gray release;
the second module is used for deploying the project gray environment cluster in a helm mode according to the gray configuration information and the project code to obtain a gray environment cluster;
a third module, configured to obtain a gray level distribution rule; the gray level release rule is used for screening user traffic routed to the gray level environment cluster;
a fourth module, configured to obtain user request information, control a user traffic route to the gray environment cluster according to the gray release rule and the user request information, perform gray release verification, and collect user feedback data;
and a fifth module, configured to determine a gray verification result according to the user feedback data.
A third aspect of an embodiment of the present application provides an electronic device, where the electronic device includes a memory and a processor, where the memory stores a computer program, and the processor implements the hell-based gray distribution method according to the first aspect when executing the computer program.
A fourth aspect of the embodiment of the present application proposes a computer-readable storage medium storing a computer program, wherein the computer program is executed by a processor to implement the hell-based grayscale distribution method according to the first aspect.
The application provides a gray level release method, a device, electronic equipment and a medium based on Helm, which are used for deploying a project gray level environment cluster in a Helm mode, determining a gray level release rule according to project business demand information, and controlling a user request to route to the gray level environment cluster according to the gray level release rule and user request information to perform gray level release verification. The application can reduce the risk brought by problems existing in iteration update of the new version to the project, flexibly select the user to participate in the test of the new version of the project according to the service demand information, has certain disaster recovery capability, can avoid service halt or different risks of accessing caused by global release to the project, and improves the experience of the user.
Drawings
FIG. 1 is a flowchart of a gray level publishing method based on Helm provided by an embodiment of the application;
fig. 2 is a schematic structural diagram of a gray level publishing device based on Helm according to an embodiment of the present application;
fig. 3 is a schematic hardware structure of an electronic device according to an embodiment of the present application.
Detailed Description
The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.
It should be noted that although functional block division is performed in a device diagram and a logic sequence is shown in a flowchart, in some cases, the steps shown or described may be performed in a different order than the block division in the device, or in the flowchart. The terms first, second and the like in the description and in the claims and in the above-described figures, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of the application only and is not intended to be limiting of the application.
Referring to fig. 1, fig. 1 is an optional flowchart of a gray level distribution method based on Helm according to an embodiment of the present application, including, but not limited to, steps S101 to S105:
step S101, acquiring gray configuration information and item codes for gray release;
step S102, according to gray configuration information and project codes, deploying project gray environment clusters in a helm mode to obtain gray environment clusters;
step S103, acquiring a gray level release rule;
step S104, obtaining user request information, controlling user traffic to route to a gray environment cluster according to gray release rules and the user request information, performing gray release verification, and collecting user feedback data;
step S105, according to the user feedback data, determining a gray verification result.
In step S101 of some embodiments, a kubernetes cluster environment on which the project runs depends is installed in advance, a helmchart template for the project running, including a gray published helmchart template, is uploaded in a harbor warehouse, a link url of the helmchart template is added in the kubernetes cluster environment by a helmspot through an account password mode, and the hart warehouse of the project is configured.
In step S103 of some embodiments, the gray scale distribution rule is used to filter user traffic routed to the gray scale environment cluster.
In some embodiments, the above-mentioned gray scale distribution method based on Helm further includes step S106:
and S106, judging whether to add the gray environment cluster into the project formal cluster according to the gray verification result.
In some embodiments, step S102 may include, but is not limited to including, step S201 to step S203:
step S201, generating a gray configuration environment according to gray configuration information;
step S202, packing item codes to generate gray item codes;
step S203, according to the gray scale project codes, project gray scale environment clusters are deployed in a gray scale configuration environment in a palm mode, and gray scale environment clusters are obtained.
In step S201 of some embodiments, gray level initialization is performed according to gray level configuration information to generate a gray level configuration environment, optionally, a node server is built in jenkins according to an account key manner, and a gray level pipeline script is invoked to issue the gray level configuration environment.
In step S202 of some embodiments, a dockerfile file for project code and code construction is pulled by a manner of constructing a credential by using a checkoutgit_ssh, where the dockerfile file is for project construction docker mirror image, then the project code is constructed by using a maven tool, packaged into a jar package, and the jar package is packaged by the manner of dockerfile mirror image.
Specifically, the step of constructing the project code by using a maven tool, packaging the project code into a jar packet and performing dock mirror packaging on the jar packet in a dock file manner comprises the following steps:
a public mirror image of a harbor mirror image private library is referenced, and packing of new project mirror images is carried out on the basis of the mirror image;
redefining the mirrored time zone and copying the jar packet of the project code to the user directory of the new mirror image in time;
defining configuration parameters of project start and a start health check;
packaging the new mirror images in a dockerbuild mode and naming the project mirror images;
logging in a harbor private library through a dockerin, and pushing the project mirror image in a dockerin mode.
In some embodiments, step S203 may include, but is not limited to including, step S301 to step S303:
step S301, aiming at gray scale item codes, determining item basic information corresponding to the gray scale item codes;
step S302, acquiring gray release parameters, executing assignment operation, assigning the gray release parameters to corresponding first variables, and updating variable values of the first variables;
step S303, according to the gray item code and the variable value of the first variable, the gray environment cluster is deployed and the gray is issued.
In some embodiments, the directory specification file in the palm includes:
char.yaml: basic information of the item chart comprises names, description information, versions and the like;
values. Yaml: for storing values of variables used in template files in templates directory;
the templates directory: storing all yaml template files in the catalogue;
reployment. Yaml: a basic list of project workloads;
ingress. Yaml: project workload keeps service outwards;
service. Yaml: the project workload creates a basic list of service terminals.
In step S301 of some embodiments, the item basic information includes item naming information, item version information, and an address of an item part repository.
In step S302 of some embodiments, the first variable is a variable in a helm variable file, where the helm variable file is specifically a value. Yaml variable file, and the first variable includes a number of item instances pod, a parameter of an item deployment selection server, a domain name of an item, a certificate related parameter, a port of an item container, a mirror address of an item, a survival check related parameter, a parameter related to resource limitation of an item container, a parameter related to scrolling update, a related parameter related to storage mount, and a preset gray release parameter is assigned to a corresponding first variable to update a variable value in the first variable.
In step S303 of some embodiments, a method of palm update-install is adopted to issue the gray level of the item through parameter transmission, optionally, the relevant value in the value s.yaml variable file is read to issue the item depoyment, the deployment of the item in the gray level environment is started, the relevant value in the value s.yaml variable file is read to issue the item service, the item is set to be exposed through service, the relevant value in the value s.yaml variable file is read to issue the item ingress, and the item is set to be externally served through domain name mode to issue the gray level of the item.
In step S103 of some embodiments, item service requirement information is obtained, gray level distribution rules are selected according to the item service requirement information, gray level distribution rules are determined, a user can request in an http manner or an https manner, and user request information is generated.
The gray level release rules comprise cookie segmentation flow rules, header segmentation flow rules and weight segmentation flow rules.
The cookie rule is specifically:
acquiring cookie information in the user request information;
when the gray scale identification information exists in the cookie information, controlling the user traffic to be routed to the gray scale environment cluster;
and when the cookie information does not contain gray identification information, controlling the user traffic to be routed to the project formal cluster.
In an exemplary embodiment, a key value of a gray release cookie is set to alwa in advance, that is, a key is equal to alwa and is set as gray identification information, when gray identification information with a key equal to alwa is in user request information, gray triggering takes effect, and when the key is equal to other values in the user request information, the user traffic is controlled to be routed to a project formal cluster, and a verification mode for judging whether gray identification information exists is as follows: and judging whether cookie information in the user request information has gray scale identification information according to the returned value of the curl-s-b 'key=always' domain name.
The header segmentation flow rule specifically comprises:
acquiring header information in user request information;
when gray scale identification information exists in the header information, controlling the user traffic to be routed to a gray scale environment cluster;
when the gray scale identification information does not exist in the header information, controlling the user flow to route to the project formal cluster.
By way of example, setting the name and the value of the gray level release header in advance, that is, the value of the name is equal to the value as gray level identification information, when the value of the name in the header information of the user request information is equal to the value, gray level triggering is effective, controlling the user traffic to be routed to the gray level environment cluster, and when the value of the name in the header information of the user request information is equal to other values, the user traffic to be routed to the project formal cluster is not walked, wherein the verification mode for judging whether the gray level identification information exists is as follows: and judging whether the header information in the user request information has gray scale identification information according to the returned value.
The weight segmentation flow rule specifically comprises the following steps:
acquiring gray percentage information, and distributing the gray percentage information to user request information;
and controlling the user traffic to be routed to the gray environment cluster according to the gray percentage information.
Illustratively, the gray scale percentage information is set in the ingress mode, the gray scale percentage information determines whether to route the user traffic to the gray scale environment cluster, the weight value in the gray scale percentage information is set to be in the range of 0-100, the hit probability of the gray scale environment is represented, and if the weight value is 0, the user traffic is not controlled to be routed to the gray scale environment cluster. The larger the value, the larger the hit probability, and when the weight value is set to 50, the routing of 50% of the user traffic to the gray scale environment cluster is controlled, and when the value=100, the routing of all the user traffic to the gray scale environment cluster is controlled, and the verification mode is as follows: and judging whether the user traffic is successfully routed to the gray environment cluster according to the returned value by the curl domain name.
In some embodiments, before gray level distribution is performed on an item, the operation and maintenance firstly uses one of a header mode, a cookie mode or a weight mode to access the domain name of the item for verification, after verification is performed, the gray level item formed by packing the item codes is tested, the test is performed according to the rule of the formulated test case, if the test is performed, a small number of gray level users are added into the gray level item (gray level environment cluster) for gray level distribution verification, and whether the gray level environment cluster of the item can achieve the expected effect is verified.
In step S106 of some embodiments, when the gray level verification result is that the gray level verification is successful, that is, the project gray level environment cluster reaches the expected effect, the gray level environment cluster is added to the project formal cluster, the gray level distribution rule is deleted, and the offline gray level environment cluster is deleted; when the gray level verification result is that the gray level verification fails, namely the project gray level environment cluster cannot achieve the expected effect, the gray level release rule is deleted, and the offline gray level environment cluster is deleted.
Referring to fig. 2, fig. 2 is a schematic structural diagram of an alternative gray-scale distribution device based on Helm according to an embodiment of the present application, where the device includes:
the first module is used for acquiring gray configuration information and project codes for gray release;
the second module is used for deploying the project gray environment clusters in a helm mode according to the gray configuration information and the project codes to obtain gray environment clusters;
a third module, configured to obtain a gray level distribution rule; the gray level release rule is used for screening users routed to the gray level environment cluster;
a fourth module, configured to obtain user request information, control a user traffic route to a gray environment cluster according to a gray release rule and the user request information, perform gray release verification, and collect user feedback data;
and a fifth module, configured to determine a gray verification result according to the user feedback data.
The embodiment of the application also provides electronic equipment, which comprises a memory and a processor, wherein the memory stores a computer program, and the processor realizes the gray level release method based on Helm when executing the computer program. The electronic equipment can be any intelligent terminal including a tablet personal computer, a vehicle-mounted computer and the like.
Referring to fig. 3, fig. 3 illustrates a hardware structure of an electronic device according to another embodiment, where the electronic device includes:
the processor 901 may be implemented by a general purpose CPU (central processing unit), a microprocessor, an application specific integrated circuit (ApplicationSpecificIntegratedCircuit, ASIC), or one or more integrated circuits, etc. for executing related programs to implement the technical solution provided by the embodiments of the present application;
the memory 902 may be implemented in the form of read-only memory (ReadOnlyMemory, ROM), static storage, dynamic storage, or random access memory (RandomAccessMemory, RAM). The memory 902 may store an operating system and other application programs, and when the technical solution provided in the embodiments of the present disclosure is implemented by software or firmware, relevant program codes are stored in the memory 902, and the processor 901 invokes the hell-based gray level distribution method for executing the embodiments of the present disclosure;
an input/output interface 903 for inputting and outputting information;
the communication interface 904 is configured to implement communication interaction between the device and other devices, and may implement communication in a wired manner (e.g. USB, network cable, etc.), or may implement communication in a wireless manner (e.g. mobile network, WIFI, bluetooth, etc.);
a bus 905 that transfers information between the various components of the device (e.g., the processor 901, the memory 902, the input/output interface 903, and the communication interface 904);
wherein the processor 901, the memory 902, the input/output interface 903 and the communication interface 904 are communicatively coupled to each other within the device via a bus 905.
The embodiment of the application also provides a computer readable storage medium, which stores a computer program, and the computer program realizes the gray level publishing method based on Helm when being executed by a processor.
The memory, as a non-transitory computer readable storage medium, may be used to store non-transitory software programs as well as non-transitory computer executable programs. In addition, the memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory optionally includes memory remotely located relative to the processor, the remote memory being connectable to the processor through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The embodiment of the application provides a gray level release method, a device, electronic equipment and a medium based on Helm, which are used for deploying a project gray level environment cluster in a Helm mode, determining a gray level release rule according to project business demand information, controlling a user request to route to the gray level environment cluster according to the gray level release rule and user request information, and carrying out gray level release verification. The application can reduce the risk brought by problems existing in iteration update of the new version to the project, flexibly select the user to participate in the test of the new version of the project according to the service demand information, has certain disaster recovery capability, can avoid service halt or different risks of accessing caused by global release to the project, and improves the experience of the user.
The embodiments described in the embodiments of the present application are for more clearly describing the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application, and those skilled in the art can know that, with the evolution of technology and the appearance of new application scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.
It will be appreciated by persons skilled in the art that the embodiments of the application are not limited by the illustrations, and that more or fewer steps than those shown may be included, or certain steps may be combined, or different steps may be included.
The preferred embodiments of the present application have been described above with reference to the accompanying drawings, and are not thereby limiting the scope of the claims of the embodiments of the present application. Any modifications, equivalent substitutions and improvements made by those skilled in the art without departing from the scope and spirit of the embodiments of the present application shall fall within the scope of the claims of the embodiments of the present application.
Claims (10)
1. The gray level publishing method based on Helm is characterized by comprising the following steps:
acquiring gray configuration information and item codes for gray release;
according to the gray configuration information and the project codes, deploying a project gray environment cluster in a helm mode to obtain a gray environment cluster;
acquiring a gray level release rule; the gray level release rule is used for screening user traffic routed to the gray level environment cluster;
acquiring user request information, controlling user traffic to be routed to the gray environment cluster according to the gray release rule and the user request information, performing gray release verification, and collecting user feedback data;
and determining a gray verification result according to the user feedback data.
2. The gradation release method according to claim 1, further comprising the step of:
and judging whether the gray environment cluster is added to a project formal cluster according to the gray verification result.
3. The gray scale distribution method according to claim 1, wherein the step of obtaining gray scale configuration information, deploying a project gray scale environment cluster by using a helm method, and obtaining the gray scale environment cluster comprises the following steps:
generating a gray scale configuration environment according to the gray scale configuration information;
packaging the item codes to generate gray item codes;
and according to the gray level project codes, deploying project gray level environment clusters in the gray level configuration environment in a helm mode to obtain the gray level environment clusters.
4. The gray scale distribution method according to claim 1, wherein the gray scale distribution rule includes a cookie segmentation flow rule, a header segmentation flow rule, and a weight segmentation flow rule, and the step of obtaining the gray scale distribution rule specifically includes:
acquiring project business demand information;
and selecting the gray level release rule according to the project service demand information, and determining the gray level release rule.
5. The gray scale distribution method according to claim 4, wherein the cookie segmentation flow rule specifically comprises: acquiring cookie information in the user request information;
when the cookie information contains gray scale identification information, controlling the user traffic to be routed to the gray scale environment cluster;
when the cookie information does not contain gray identification information, controlling the user traffic to be routed to the project formal cluster;
the header segmentation flow rule specifically comprises the following steps:
acquiring header information in the user request information;
when gray scale identification information exists in the header information, controlling user traffic to be routed to the gray scale environment cluster;
when the gray scale identification information does not exist in the header information, controlling the user flow to route to the project formal cluster;
the weight segmentation flow rule specifically comprises the following steps:
acquiring gray percentage information, and distributing the gray percentage information to the user request information;
and controlling the user traffic to be routed to the gray environment cluster according to the gray percentage information.
6. The gray scale distribution method according to claim 3, wherein the step of obtaining the gray scale environment cluster by performing deployment of a project gray scale environment cluster in the gray scale configuration environment according to the gray scale project code in a helm manner comprises:
determining project basic information corresponding to the gray project code aiming at the gray project code; the project basic information comprises project naming information, project version information and an address of a project chart warehouse;
acquiring gray release parameters, executing assignment operation, assigning the gray release parameters to corresponding first variables, and updating variable values of the first variables; the first variable is a variable in a palm variable file; the first variable comprises the number of item instances pod, item deployment selection server parameters, item domain names and certificate related parameters, item container ports, item mirror addresses, survival check related parameters, item container resource limit related parameters, rolling update related parameters and storage mounting related parameters;
and according to the gray scale item codes and the variable values of the first variables, deploying the gray scale environment clusters and releasing gray scales.
7. The gray scale distribution method according to claim 2, wherein the step of determining whether to add the gray scale environment cluster to the project formal cluster according to the gray scale verification result comprises:
when the gray level verification result is that the gray level verification is successful, adding the gray level environment cluster into the project formal cluster, deleting the gray level release rule, and off-line the gray level environment cluster;
and deleting the gray level release rule and off-line the gray level environment cluster when the gray level verification result is that the gray level verification fails.
8. A hell-based gray level distribution device, comprising:
the first module is used for acquiring gray configuration information and project codes for gray release;
the second module is used for deploying the project gray environment cluster in a helm mode according to the gray configuration information and the project code to obtain a gray environment cluster;
a third module, configured to obtain a gray level distribution rule; the gray level release rule is used for screening user traffic routed to the gray level environment cluster;
a fourth module, configured to obtain user request information, control a user traffic route to the gray environment cluster according to the gray release rule and the user request information, perform gray release verification, and collect user feedback data;
and a fifth module, configured to determine a gray verification result according to the user feedback data.
9. An electronic device comprising a memory storing a computer program and a processor that when executing the computer program implements the hell based gray distribution method of any one of claims 1 to 7.
10. A computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the hell-based gray level distribution method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310968557.3A CN117215596A (en) | 2023-08-02 | 2023-08-02 | Helm-based gray level publishing method and device, electronic equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310968557.3A CN117215596A (en) | 2023-08-02 | 2023-08-02 | Helm-based gray level publishing method and device, electronic equipment and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117215596A true CN117215596A (en) | 2023-12-12 |
Family
ID=89039698
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310968557.3A Pending CN117215596A (en) | 2023-08-02 | 2023-08-02 | Helm-based gray level publishing method and device, electronic equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117215596A (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112822272A (en) * | 2021-01-08 | 2021-05-18 | 上海理想信息产业（集团）有限公司 | Micro-service gray scale publishing method and device, computer equipment and storage medium |
| CN113422732A (en) * | 2021-06-22 | 2021-09-21 | 康键信息技术（深圳）有限公司 | Version updating method, device, equipment and storage medium based on total station gray scale |
| CN113791759A (en) * | 2021-09-09 | 2021-12-14 | 上海仙塔智能科技有限公司 | Code development processing method and device, electronic equipment and storage medium |
| CN114265607A (en) * | 2022-03-03 | 2022-04-01 | 杭州朗澈科技有限公司 | Gray scale publishing method and system, electronic device and storage medium |
| CN114840222A (en) * | 2022-04-26 | 2022-08-02 | 深圳市富途网络科技有限公司 | Gray scale publishing method based on ESOP system and related equipment |
| CN115168162A (en) * | 2022-09-08 | 2022-10-11 | 江苏博云科技股份有限公司 | Multi-gray-scale issuing method and device based on ingress controller in container environment and storage medium |
| CN115826997A (en) * | 2022-12-15 | 2023-03-21 | 平安银行股份有限公司 | Version release method and device, electronic equipment and storage medium |
| CN115993977A (en) * | 2022-12-29 | 2023-04-21 | 中国民航信息网络股份有限公司 | Application deployment method and device |
-
2023
- 2023-08-02 CN CN202310968557.3A patent/CN117215596A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112822272A (en) * | 2021-01-08 | 2021-05-18 | 上海理想信息产业（集团）有限公司 | Micro-service gray scale publishing method and device, computer equipment and storage medium |
| CN113422732A (en) * | 2021-06-22 | 2021-09-21 | 康键信息技术（深圳）有限公司 | Version updating method, device, equipment and storage medium based on total station gray scale |
| CN113791759A (en) * | 2021-09-09 | 2021-12-14 | 上海仙塔智能科技有限公司 | Code development processing method and device, electronic equipment and storage medium |
| CN114265607A (en) * | 2022-03-03 | 2022-04-01 | 杭州朗澈科技有限公司 | Gray scale publishing method and system, electronic device and storage medium |
| CN114840222A (en) * | 2022-04-26 | 2022-08-02 | 深圳市富途网络科技有限公司 | Gray scale publishing method based on ESOP system and related equipment |
| CN115168162A (en) * | 2022-09-08 | 2022-10-11 | 江苏博云科技股份有限公司 | Multi-gray-scale issuing method and device based on ingress controller in container environment and storage medium |
| CN115826997A (en) * | 2022-12-15 | 2023-03-21 | 平安银行股份有限公司 | Version release method and device, electronic equipment and storage medium |
| CN115993977A (en) * | 2022-12-29 | 2023-04-21 | 中国民航信息网络股份有限公司 | Application deployment method and device |
Non-Patent Citations (2)
| Title |
|---|
| 张挺: "《Python自动化接口测试自学手册 》", 30 November 2020, 中国铁道出版社有限公司, pages: 222 * |
| 心蓝: "《构建高质量软件 持续集成与持续交付***实践》", 30 September 2021, 机械工业出版社, pages: 264 - 265 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109976774B (en) | Block link point deployment method, device, equipment and storage medium | |
| CN109688222B (en) | Shared computing resource scheduling method, shared computing system, server and storage medium | |
| US10430172B2 (en) | Re-configuration in cloud computing environments | |
| CN102355500B (en) | Service push method and device | |
| JP6201917B2 (en) | System and method for configuring field devices | |
| CN113259479B (en) | Data processing method and equipment | |
| CN111901157B (en) | Service deployment method, device, equipment and medium based on k8s | |
| CN110750243A (en) | Project code development method and system | |
| CN111857733A (en) | Construction method, device and system of business environment and readable storage medium | |
| CN116257438A (en) | Updating method of interface test case and related equipment | |
| CN113419818B (en) | Basic component deployment method, device, server and storage medium | |
| CN109391658B (en) | Account data synchronization method and equipment, storage medium and terminal thereof | |
| CN112346758B (en) | Digital infrastructure service updating platform, updating method and electronic equipment | |
| CN114172811A (en) | Container mirror image deployment platform and deployment method thereof | |
| US20090150882A1 (en) | System and method for software application installation | |
| CN115129574A (en) | Code testing method and device | |
| CN117215596A (en) | Helm-based gray level publishing method and device, electronic equipment and medium | |
| CN116414407A (en) | Method, device, equipment and medium for component installation and data processing | |
| CN114756261B (en) | Container cluster upgrading method and system, electronic equipment and medium | |
| CN107682271B (en) | Method and device for generating routing line | |
| CN115883512A (en) | DNS domain name processing method, device, system, equipment and medium | |
| CN112685102B (en) | Gateway plug-in hot loading method, device, equipment and medium | |
| CN114490073A (en) | Electronic map operation and maintenance method, electronic map data using method and service system | |
| CN116701004A (en) | Cloud function development method, device, electronic device and storage medium | |
| JP6973063B2 (en) | Image processing system and information processing equipment |
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 |