CN117749799A - Gray release method and device, electronic equipment and storage medium - Google Patents
Gray release method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN117749799A CN117749799A CN202211114866.6A CN202211114866A CN117749799A CN 117749799 A CN117749799 A CN 117749799A CN 202211114866 A CN202211114866 A CN 202211114866A CN 117749799 A CN117749799 A CN 117749799A
- Authority
- CN
- China
- Prior art keywords
- service grid
- gateway
- container cloud
- service
- component
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 49
- 238000003860 storage Methods 0.000 title claims abstract description 13
- 238000009826 distribution Methods 0.000 claims description 23
- 238000004590 computer program Methods 0.000 claims description 11
- 238000002347 injection Methods 0.000 claims description 7
- 239000007924 injection Substances 0.000 claims description 7
- 238000010586 diagram Methods 0.000 description 10
- 238000007726 management method Methods 0.000 description 10
- 230000004048 modification Effects 0.000 description 8
- 238000012986 modification Methods 0.000 description 8
- 230000008569 process Effects 0.000 description 7
- 230000006870 function Effects 0.000 description 6
- 230000008676 import Effects 0.000 description 6
- 238000012545 processing Methods 0.000 description 5
- 230000009471 action Effects 0.000 description 3
- 239000000243 solution Substances 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 230000002441 reversible effect Effects 0.000 description 2
- 238000011144 upstream manufacturing Methods 0.000 description 2
- 241000287219 Serinus canaria Species 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004140 cleaning Methods 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000012634 fragment Substances 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000003032 molecular docking Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The application provides a gray level release method, a gray level release device, electronic equipment and a storage medium, relates to the technical field of computers, and aims to realize gray level release of services in a container cloud based on a service grid. The method comprises the following steps: injecting a service grid into a container cloud, and adding a target workload for gray scale release, wherein a gateway inlet of the service grid and a gateway inlet of the container cloud are controlled by a load equalizer; setting a gray scale rule of the service grid to point to the target workload; when a gray level release request is received, controlling the load balancer to guide flow into a gateway inlet of the service grid so as to access the target workload in the container cloud through the service grid, and further realizing gray level release.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a gray level publishing method, a gray level publishing device, an electronic device, and a storage medium.
Background
In order to carry out flow control on services in the container cloud, service grids are introduced in the related technology, and can solve the flow control problem by the lightest modification without affecting the stability of a service system. Numerous services often require version iterations of the service, and version releases of the newly added service. Gray scale publishing through a service grid is typically required during version iteration of the service and version publishing of the newly added service.
The service grid flow management is realized according to the configuration of virtual service and DestinationRule, but related services access the container cloud in a node port mode, and the access priority of the node port is higher than that of the virtual service, so that the gray release based on the service grid cannot be effective due to the fact that the node port enters the container cloud, the gray release cannot be issued according to the flow of the gray rule, and the purpose of service management cannot be achieved.
Disclosure of Invention
In view of the above, embodiments of the present application provide a gray scale distribution method, apparatus, electronic device, and storage medium, so as to overcome or at least partially solve the above problem.
In a first aspect of an embodiment of the present application, a gray scale publishing method is provided, including:
injecting a service grid into a container cloud, and adding a target workload for gray scale release, wherein a gateway inlet of the service grid and a gateway inlet of the container cloud are controlled by a load equalizer;
setting a gray scale rule of the service grid to point to the target workload;
when a gray level release request is received, controlling the load balancer to guide flow into a gateway inlet of the service grid so as to access the target workload in the container cloud through the service grid, and further realizing gray level release.
Optionally, the method further comprises:
when a request for gray level release is received, the load balancer is controlled to guide the flow into a gateway inlet of the container cloud so as to directly access an original workload in the container cloud, and gray level release is further achieved.
Optionally, the setting the gray scale rule of the service grid points to the target workload includes:
configuring access forms of the container cloud to obtain the container cloud with two access forms, wherein the two access forms comprise: accessing the container cloud through a NodePort, accessing the service grid through an IP, and accessing the container cloud through the service grid;
configuring an Istio-gateway component of the service grid, and enabling the traffic to be diverted from the Istio-gateway component to the gateway component;
the gateway component is configured to distribute the traffic to a virtual service component;
and configuring the virtual service component and the DestinationRule component, so that the flow flows to the target workload pointed by the DestinationRule component after reaching the DestinationRule component from the virtual service component.
Optionally, when the gray level publishing request is received, controlling the load balancer to import traffic into a gateway portal of the service grid to access the target workload in the container cloud through the service grid, including:
when the gray level release request is received, controlling the load balancer to guide the flow into the Istio-gateway component so as to initiate an access request from the Sidecar of the service grid according to the gray level release request, wherein the access request is used for accessing the target workload in the container cloud through the service grid;
after the controlling the load balancer to direct the traffic to a gateway portal of the container cloud, further comprising:
and importing the flow into the NodePort according to the NodePort mapped by the gateway inlet of the container cloud.
Optionally, before the controlling the load balancer to direct the traffic to the gateway portal of the container cloud, the method further comprises:
modifying the gray scale rule of the service grid to enable the service grid to point to the original workload;
deleting the target workload;
after the controlling the load balancer to direct the traffic to a gateway portal of the container cloud, further comprising:
clearing the configuration of each component in the Sidecar of the service grid, wherein each component in the Sidecar comprises: the Istio-gateway component, the VirtualService component and the DestinationRule component;
restarting the Pod of the container cloud where the service grid is located.
Optionally, the method further comprises:
when a gray level release request for another workload is received, adding the other workload in a service naming space where the service grid is located;
and modifying the gray scale rule of the service grid to lead the gray scale rule of the service grid to point to the other target workload.
In a second aspect of the embodiments of the present application, there is provided a gray scale distribution device, including:
the system comprises an injection module, a load equalizer and a gray level distribution module, wherein the injection module is used for injecting a service grid in a container cloud and adding a target workload for gray level distribution, and a gateway inlet of the service grid and a gateway inlet of the container cloud are controlled by the load equalizer;
the setting module is used for setting the gray rule of the service grid to point to the target workload;
and the control module is used for controlling the load balancer to guide the flow into the gateway entrance of the service grid when receiving the gray release request so as to access the target workload in the container cloud through the service grid and further realize gray release.
In a third aspect of the embodiments of the present application, there is provided an electronic device, including: a processor; a memory for storing the processor-executable instructions; wherein the processor is configured to execute the instructions to implement the gray scale distribution method according to the first aspect.
In a fourth aspect of embodiments of the present application, there is provided a computer-readable storage medium, which when executed by a processor of an electronic device, causes the electronic device to perform the grayscale distribution method according to the first aspect.
In a fifth aspect of embodiments of the present application, a computer program product is provided, comprising a computer program, which when executed by a processor implements the gray scale distribution method according to the first aspect.
Embodiments of the present application include the following advantages:
in this embodiment, the load balancer is controlled to guide the flow into the gateway portal of the service grid, so as to access the container cloud from the service grid, and solve the technical problem that gray release based on the service grid cannot be effective due to the fact that the container cloud is directly accessed in the form of NodePort. The gray scale rule of the service grid points to the target workload used for gray scale release in the container cloud, so that the target workload in the container cloud can be accessed through the service grid, and gray scale release of the target workload is realized under the condition that traffic is led into the service grid.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments of the present application will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flowchart illustrating steps of a gray scale distribution method according to an embodiment of the present application;
FIG. 2 is a schematic diagram of upstream gateway switching in a system architecture according to an embodiment of the present application;
FIG. 3 is a flow chart of the process of the traffic import Istio-gateway according to an embodiment of the present application;
FIG. 4 is a flow chart of introducing traffic into a service grid according to an embodiment of the present application;
FIG. 5 is a flow chart of introducing traffic into a container cloud according to an embodiment of the present application;
fig. 6 is a block diagram of a gradation issuing apparatus according to an embodiment of the present application.
Detailed Description
In order that the above-recited objects, features and advantages of the present application will become more readily apparent, a more particular description of the invention briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings.
Some nouns in the embodiments of the application are described below:
gray level release: by adjusting the traffic policy, one part of user traffic is led to one version of workload, and the other part of user traffic is led to the other version of workload, so that the two versions of workload are smoothly transited. The gray level release can ensure the stability of the whole system, and the problems can be found and debugged in the initial gray level. The modes of gray scale distribution include bluish green distribution, canary distribution, and AB testing.
Container (Container): a lightweight, portable, self-contained software packaging technique, a container may contain code, dependency packages, and even operating systems required for an application. One container corresponds to one application.
Container cloud (Kubernetes cluster): the cluster management system of the container can omit a plurality of manual deployment and expansion operations of the application container process, can gather a plurality of groups of hosts running the container together, and can easily and efficiently manage the clusters of the container.
Service Mesh: consisting of a network proxy paired with each service in an application and a set of task management flows, business independent service governance capabilities can be decoupled to individual service Sidecar (Sidecar mode) processing. The service grid may implement traffic management for the service.
Istio: typically deployed in Kubernetes clusters, an Istio can be understood as a service grid by the Sidecar deploying traffic Sidecar Proxy in the Pod, the side car Proxy using Envoy (a service Proxy program) to effect control of ingress and egress traffic to the Pod.
Pod (play old data, a data structure): including one or more containers, as well as some shared resources (e.g., shared storage, networks, operating information, etc.) of these containers.
VirtualService: distribution rules for controlling service grid traffic, docking gateways, target rules, and other virtual services.
DestinationRule: the method is used for configuring the target instance and the load rule, and can be matched with the VirtualService for use.
Referring to fig. 1, a flowchart illustrating steps of a gray scale distribution method in an embodiment of the present application is shown, and as shown in fig. 1, the gray scale distribution method may specifically include the following steps:
step S11: injecting a service grid in a container cloud, and adding a target workload for gray scale publishing, wherein a gateway inlet of the service grid and a gateway inlet of the container cloud are controlled by a load balancer.
A service grid is injected in one business NameSpace (NameSpace) of the container cloud. The namespaces are logically divided into container clouds, and different code functions can be distinguished by classifying the container clouds through the namespaces, so that conflicts caused by identical variable names among different codes when different code fragments are used simultaneously are avoided.
After the service grid is injected into the service naming space, a target workload for gray level release is added into the service naming space. The workload is a workload required for the service, the target workload may be another version of the workload in the container cloud, in which case gray scale publication of the target workload may enable version iteration of the service; the target workload may also be a new workload, in which case the gray scale release of the target workload may implement release of the version of the newly added service.
It should be noted that the service grid needs to be injected first and then the target workload is added, otherwise the traffic is distributed directly to the target workload and other workloads.
The gateway portal of the service grid and the gateway portal of the container cloud are governed by the same load balancer, i.e. one load balancer is responsible for directing traffic to the gateway portal of the service grid or to the gateway portal of the container cloud. Fig. 2 is a schematic diagram of a system architecture upstream gateway switching in an embodiment of the present application, where a load balancer nminix (engine x, reverse proxy server) may implement switching of gateway portals.
Step S12: setting a gray scale rule of the service grid to point to the target workload.
The DestinationRule component of the service grid points to the target workload by modifying a plurality of components of the service grid, so that setting of the gray rule of the service grid is completed, and the gray rule pointing to the target workload is obtained.
Step S13: when a gray level release request is received, controlling the load balancer to guide flow into a gateway inlet of the service grid so as to access the target workload in the container cloud through the service grid, and further realizing gray level release.
The gradation release request may be generated by an external operation script. When a gray level release request is received, the load balancer can guide the flow into a gateway inlet of the service grid, so that the service grid accesses a target workload in the container cloud, and further, when a user corresponding to the flow guided into the service grid requests the service, the service adopts the target workload, so that the gray level release of the service corresponding to the target workload is completed.
Alternatively, the load balancer may employ nmlnx of a 4-layer configuration rule and maintain a long link through keep alive (mechanism for detecting dead connection), so as to facilitate fast switching between the gateway portal of the service grid and the gateway portal of the container cloud.
By adopting the technical scheme of the embodiment of the application, the load balancer can be controlled to guide the flow into the gateway entrance of the service grid, the container cloud is accessed from the service grid, and the technical problem that gray release based on the service grid cannot be effective due to the fact that the container cloud is accessed directly through the NodePort mode is solved. The gray scale rule of the service grid points to the target workload used for gray scale release in the container cloud, so that the target workload in the container cloud can be accessed through the service grid, and further gray scale release of the target workload is realized under the condition that the traffic is led into the service grid.
Optionally, on the basis of the above technical solution, setting the gray rule of the service grid to point to the target workload may specifically include the following steps:
step S21: configuring access forms of the container cloud to obtain the container cloud with two access forms, wherein the two access forms comprise: accessing the container cloud through a NodePort, and accessing the service grid through an IP, and further accessing the container cloud through the service grid.
In the related art, a common access form of the container cloud is access through a NodePort. Because the priority of the NodePort is higher than that of the virtual service, the NodePort is directly accessed, and the gray level release of the service grid is not effective.
In order to enable gray level release to be effective, the embodiment of the application configures an access form for the container cloud, wherein the access form is as follows: the service grid is accessed via IP (Internet Protocol Address ) and the container cloud is accessed via the service grid. The service grid is used for accessing the container cloud, and the service grid is used for directly accessing the workload in the container cloud according to the workload in the container cloud pointed by the rule inside the service grid after the flow is in the service grid. Because the container cloud is accessed through the service grid, the gray scale rule of the service grid can be validated, and gray scale release can be realized. Where IP is the IP of the host that provides the hardware services for the container cloud.
In order to realize the switching between gray release and gray release, another access form is configured for the container cloud, wherein the access form is as follows: the container cloud is accessed directly through the NodePort. The container cloud is directly accessed through the NodePort, and the priority of the NodePort is higher, so that the gray rule of the service grid can be ignored, gray release is not effective, and gray release is realized.
Step S22: and configuring an Istio-gateway component of the service grid, and enabling the traffic to be diverted from the Istio-gateway component to the gateway component.
The gateway component corresponds to the routing of the container cloud, and after configuration, the distribution of the traffic can be realized. However, the gateway component has no out-of-line capability, so traffic needs to go from the Istio-gateway component and then turn to the gateway component.
The Istio-gateway component is equivalent to a gateway portal of a service grid, is exposed data of NodePort, and has external capability. The flow enters the service grid through the Istio-gateway component, so that the security can be improved, and a shielding function and the like can be realized.
Step S23: and configuring the gateway component to enable the gateway component to distribute the traffic to a virtual service component.
The gateway component is connected to one or more virtual service components, and by configuring the gateway component, the gateway component can confirm to which virtual service component the received traffic is distributed.
Step S24: and configuring the virtual service component and the DestinationRule component, so that the flow flows to the target workload pointed by the DestinationRule component after reaching the DestinationRule component from the virtual service component.
A VirtualService component and a DestinationRule component are matched, so that after the flow reaches a VirtualService component, the flow flows to the DestinationRule component matched with the VirtualService component.
The virtual service component and the DestinationRule component are combined to be configured, the configuration of the virtual service component can determine how much traffic is distributed to the corresponding DestinationRule component, and the configuration of the DestinationRule component can determine how many nodes to distribute the traffic. The DestinationRule component points to a workload, and the DestinationRule component is configured to point to a target workload, so that gray release is finally enabled.
FIG. 3 is a flow chart of the process of the flow import Istio-gateway according to an embodiment of the present application. The load balancer imports traffic into the Service grid by importation of traffic into the Istio-gateway component, which diverts traffic to the gateway component, which determines to which virtual Service component to distribute traffic, one virtual Service component being connected to one DestinationRule component, which directs the Service to invoke the required workload from the container.
In the embodiment of the present application, configuring each component refers to modifying parameters of each component. By configuring the Istio-gateway component, virtual service component and destinationRule component, the flow is led into the service grid, so that the request is initiated from the Envoy Sidecar of Istio in the system, and the gray rule is validated.
Optionally, the load balancer directs traffic to a gateway portal of the service grid to access a target workload in the container cloud through the service grid, which may be specifically: the load equalizer imports the traffic into an Istio-gateway component, the Istio-gateway component turns the traffic to the gateway component, the gateway component determines to which virtual service component the traffic is distributed, and finally the traffic flows to the workload pointed by the DestinationRule component, thereby realizing that an access request is initiated from the Sidecar of the service grid according to the gray release request, and the access request is used for accessing the target workload in the container cloud through the service grid.
Fig. 4 is a flow chart of introducing traffic into a service grid according to an embodiment of the present application. The method comprises the steps of deploying services and workloads corresponding to the services in a naming space of a container cloud, injecting service grids into the naming space, creating gray level release rules of the service grids, enabling the gray level release rules to point to default workloads, switching ports of keep and Nginx to Istio inlets (Istio-gateway), adding the workloads, modifying the gray level rules, enabling the gray level release rules to point to the workloads corresponding to the services, and accordingly achieving gray level release of the services.
Optionally, the load balancer may also direct traffic to the gateway portals of the container cloud. When a request for gray level release is received, the load balancer can be controlled to guide the flow into a gateway inlet of the container cloud through an external script so as to directly access the original workload in the container cloud, and further the gray level release is realized.
Because the container cloud is accessed directly through the gateway portal of the container cloud without passing through the service grid, gray scale release can be disabled, thereby achieving gray scale release. The gray scale release is not performed.
Therefore, the traffic can be led into different gateway inlets by controlling the load equalizer, thereby realizing the free switching between gray release and gray release, ensuring the high availability of service and reducing the influence of service management on service.
Optionally, the access to the container cloud through the node port is realized by introducing the flow into the node port according to the node port mapped by the gateway inlet of the container cloud after the load balancer introduces the flow into the gateway inlet of the container cloud.
Optionally, on the basis of the above technical solution, before controlling the load balancer to direct the traffic to the gateway portal of the container cloud, the method further includes: modifying the gray scale rule of the service grid to enable the service grid to point to the original workload; and deleting the target workload, closing the service name space to ensure that the target workload is not accessed any more, and accessing the original workload, thereby realizing gray level release. The original workload refers to an original workload in the container cloud, and may be a workload of a version before updating the target workload.
After directing the traffic to the gateway portal of the container cloud, further comprising: the configuration of each component in the Sidecar of the service grid is cleared, and each component in the Sidecar at least comprises: an Istio-gateway component, a VirtualService component and a DestinationRule component; restarting the Pod in the container cloud where the service grid is located.
The Sidecar stores the service governance capabilities of the service grid, so the Istio-gateway component, visual service component, and DestinationRule component are stored in the Sidecar. The configuration of each component in the Sidecar is cleared, which is equivalent to the deletion of the gray rule, so that the gray release is realized. Because the Pod is restarted, the modification can be validated, and therefore the Pod is restarted.
Fig. 5 is a flow chart of introducing traffic into a container cloud according to an embodiment of the present application. And modifying the gray rule of the service grid, enabling all traffic of the gray rule to point to a single workload, and deleting the workload of the version of the gray rule, which is pointed to by the gray rule and is used for carrying out gray release. And switching the ports of the Keepalive and the Nginx to a gateway inlet of the container cloud, cleaning Sidecar of Istio, and recording historical operation.
Alternatively, all operations may be recorded for tracing or subsequent analysis.
Optionally, in the case of gray level publishing of the target workload, if the modification is needed to perform gray level publishing of another workload, the other workload may be added in the service namespace where the service grid is located, and the gray level rule of the service grid may be modified, so that the gray level rule of the service grid points to the other target workload.
If the attribute of the other workload is the same as the attribute of the target workload, modifying the gray rule of the service grid may be modifying the workload pointed to by the DestinationRule component from the target workload to the other workload. If the attributes of the other workload and the target workload are not the same, it may be necessary to modify the configuration of each of the gateway component, the virtual service component, and the DestinationRule component.
Thus, the gray level release of the target workload can be realized from the gray level release of the other workload to the gray level release of the other workload, and various requirements are further met.
According to the gateway portal management method and device for the Istio, convenient packaging is carried out on gateway portal management of Istio, so that the user threshold is reduced, the gateway portal management method and device are popular and easy to understand, and the gateway portal management method and device are convenient to implement on the ground. And by switching links such as reverse proxy and container layer increasing and decreasing rules at the gateway layer, the capability of rapidly injecting service grids and rapidly switching container clouds is realized, and the implementation is more effectively carried out in the actual production environment. With the landing of gray release, the service grid is enabled to not only check problems more conveniently and control the flow of the service more conveniently, but also switch freely in multiple versions, so that the service can be developed stably in rapid iteration.
It should be noted that, for simplicity of description, the method embodiments are shown as a series of acts, but it should be understood by those skilled in the art that the embodiments are not limited by the order of acts described, as some steps may occur in other orders or concurrently in accordance with the embodiments. Further, those skilled in the art will appreciate that the embodiments described in the specification are all preferred embodiments and that the acts referred to are not necessarily required by the embodiments of the present application.
Fig. 6 is a block diagram of a gray scale distribution device according to an embodiment of the present application, as shown in fig. 6, the device includes: injection module, settlement module and control module, wherein:
the system comprises an injection module, a load equalizer and a gray level distribution module, wherein the injection module is used for injecting a service grid in a container cloud and adding a target workload for gray level distribution, and a gateway inlet of the service grid and a gateway inlet of the container cloud are controlled by the load equalizer;
the setting module is used for setting the gray rule of the service grid to point to the target workload;
and the control module is used for controlling the load balancer to guide the flow into the gateway entrance of the service grid when receiving the gray release request so as to access the target workload in the container cloud through the service grid and further realize gray release.
Optionally, as an embodiment, the method further includes:
and the importing module is used for controlling the load balancer to import the flow into the gateway inlet of the container cloud when receiving the request for gray level release so as to directly access the original workload in the container cloud and further realize gray level release.
Optionally, as an embodiment, the setting module includes:
the first configuration unit is configured to configure an access form of the container cloud to obtain the container cloud with two access forms, wherein the two access forms comprise: accessing the container cloud through a NodePort, accessing the service grid through an IP, and accessing the container cloud through the service grid;
a second configuration unit, configured to configure an Istio-gateway component of the service grid, and make the traffic flow change from the Istio-gateway component to the gateway component;
the third configuration unit is used for configuring the gateway component to enable the gateway component to distribute the traffic to a virtual service component;
and the fourth configuration unit is used for configuring the virtual service component and the DestinationRule component, so that the flow flows to the target workload pointed by the DestinationRule component after reaching the DestinationRule component from the virtual service component.
Optionally, as an embodiment, the control module includes:
a control unit, configured to, when receiving the gray level issue request, control the load balancer to direct the traffic to the Istio-gateway component, so as to initiate an access request from the Sidecar of the service grid according to the gray level issue request, where the access request is used to access the target workload in the container cloud through the service grid;
after the controlling the load balancer to direct the traffic to a gateway portal of the container cloud, further comprising:
and the mapping module is used for importing the flow into the NodePort according to the NodePort mapped by the gateway inlet of the container cloud.
Optionally, as an embodiment, before the controlling the load balancer directs the traffic to a gateway portal of the container cloud, the method further includes:
the modification module is used for modifying the gray rule of the service grid to enable the service grid to point to the original workload;
a deleting module, configured to delete the target workload;
after the controlling the load balancer to direct the traffic to a gateway portal of the container cloud, further comprising:
the clearing module is used for clearing the configuration of each component in the Sidecar of the service grid, and each component in the Sidecar comprises: the Istio-gateway component, the VirtualService component and the DestinationRule component;
and the restarting module is used for restarting the Pod where the service grid is located in the container cloud.
Optionally, as an embodiment, the method further includes:
the adding module is used for adding another workload in a service naming space where the service grid is located when a gray release request aiming at the other workload is received;
and the rule modification module is used for modifying the gray rule of the service grid to lead the gray rule of the service grid to point to the other target workload.
It should be noted that, the system embodiment is similar to the method embodiment, so the description is simpler, and the relevant places refer to the method embodiment.
In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described by differences from other embodiments, and identical and similar parts between the embodiments are all enough to be referred to each other.
It will be apparent to those skilled in the art that embodiments of the present application may be provided as a method, apparatus, or computer program product. Accordingly, the present embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus, electronic devices, and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing terminal device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal device, create a system for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present embodiments have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following claims be interpreted as including the preferred embodiments and all such alterations and modifications as fall within the scope of the embodiments of the present application.
Finally, it is further noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or terminal device comprising the element.
The gray level publishing method, device, electronic equipment and storage medium provided by the application are described in detail, and specific examples are applied to illustrate the principle and implementation of the application, and the description of the above examples is only used for helping to understand the method and core ideas of the application; meanwhile, as those skilled in the art will have modifications in the specific embodiments and application scope in accordance with the ideas of the present application, the present description should not be construed as limiting the present application in view of the above.
Claims (10)
1. A gradation release method, characterized by comprising:
injecting a service grid into a container cloud, and adding a target workload for gray scale release, wherein a gateway inlet of the service grid and a gateway inlet of the container cloud are controlled by a load equalizer;
setting a gray scale rule of the service grid to point to the target workload;
when a gray level release request is received, controlling the load balancer to guide flow into a gateway inlet of the service grid so as to access the target workload in the container cloud through the service grid, and further realizing gray level release.
2. The method as recited in claim 1, further comprising:
when a request for gray level release is received, the load balancer is controlled to guide the flow into a gateway inlet of the container cloud so as to directly access an original workload in the container cloud, and gray level release is further achieved.
3. The method of claim 1, wherein the setting the gray scale rule of the service grid to point to the target workload comprises:
configuring access forms of the container cloud to obtain the container cloud with two access forms, wherein the two access forms comprise: accessing the container cloud through a NodePort, accessing the service grid through an IP, and accessing the container cloud through the service grid;
configuring an Istio-gateway component of the service grid, and enabling the traffic to be diverted from the Istio-gateway component to the gateway component;
the gateway component is configured to distribute the traffic to a virtual service component;
and configuring the virtual service component and the DestinationRule component, so that the flow flows to the target workload pointed by the DestinationRule component after reaching the DestinationRule component from the virtual service component.
4. A method according to claim 3, wherein said controlling said load balancer to direct traffic into a gateway portal of said service grid to access said target workload in said container cloud through said service grid upon receipt of a gray scale publication request comprises:
when the gray level release request is received, controlling the load balancer to guide the flow into the Istio-gateway component so as to initiate an access request from the Sidecar of the service grid according to the gray level release request, wherein the access request is used for accessing the target workload in the container cloud through the service grid;
after the controlling the load balancer to direct the traffic to a gateway portal of the container cloud, further comprising:
and importing the flow into the NodePort according to the NodePort mapped by the gateway inlet of the container cloud.
5. The method of claim 3, further comprising, prior to said controlling said load balancer to direct said traffic to a gateway portal of said container cloud:
modifying the gray scale rule of the service grid to enable the service grid to point to the original workload;
deleting the target workload;
after the controlling the load balancer to direct the traffic to a gateway portal of the container cloud, further comprising:
clearing the configuration of each component in the Sidecar of the service grid, wherein each component in the Sidecar comprises: the Istio-gateway component, the VirtualService component and the DestinationRule component;
restarting the Pod of the container cloud where the service grid is located.
6. The method of any one of claims 1-5, further comprising:
when a gray level release request for another workload is received, adding the other workload in a service naming space where the service grid is located;
and modifying the gray scale rule of the service grid to lead the gray scale rule of the service grid to point to the other target workload.
7. A gradation issuing apparatus characterized by comprising:
the system comprises an injection module, a load equalizer and a gray level distribution module, wherein the injection module is used for injecting a service grid in a container cloud and adding a target workload for gray level distribution, and a gateway inlet of the service grid and a gateway inlet of the container cloud are controlled by the load equalizer;
the setting module is used for setting the gray rule of the service grid to point to the target workload;
and the control module is used for controlling the load balancer to guide the flow into the gateway entrance of the service grid when receiving the gray release request so as to access the target workload in the container cloud through the service grid and further realize gray release.
8. An electronic device, comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the gray scale distribution method of any of claims 1 to 6.
9. A computer readable storage medium, characterized in that instructions in the computer readable storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the gray scale distribution method according to any of claims 1 to 6.
10. A computer program product comprising a computer program which, when executed by a processor, implements the gray scale distribution method according to any of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211114866.6A CN117749799A (en) | 2022-09-14 | 2022-09-14 | Gray release method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211114866.6A CN117749799A (en) | 2022-09-14 | 2022-09-14 | Gray release method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117749799A true CN117749799A (en) | 2024-03-22 |
Family
ID=90276246
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211114866.6A Pending CN117749799A (en) | 2022-09-14 | 2022-09-14 | Gray release method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117749799A (en) |
-
2022
- 2022-09-14 CN CN202211114866.6A patent/CN117749799A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11621998B2 (en) | Dynamic creation and execution of containerized applications in cloud computing | |
| US9992166B2 (en) | Hierarchical rule development and binding for web application server firewall | |
| US11119654B2 (en) | Determining an optimal storage environment for data sets and for migrating data sets | |
| US9262478B2 (en) | Compile-time grouping of tuples in a streaming application | |
| US11675774B2 (en) | Remote policy validation for managing distributed system resources | |
| CN107766126A (en) | Construction method, system, device and the storage medium of container mirror image | |
| CN110392999A (en) | Virtual filter platform in distributed computing system | |
| US20150242531A1 (en) | Database access control for multi-tier processing | |
| CN104603762A (en) | Supporting coordinated access to file system's shared storage using automatic alignment of parallel file access protocol and metadata management | |
| US20130110752A1 (en) | On Demand Multi-Objective Network Optimization | |
| US10397051B1 (en) | Configuration and testing of network-based service platform resources using a service platform specific language | |
| US20220043822A1 (en) | Shadow experiments for serverless multi-tenant cloud services | |
| US11494202B2 (en) | Database replication plugins as a service | |
| US20190034464A1 (en) | Methods and systems that collect data from computing facilities and export a specified portion of the collected data for remote processing and analysis | |
| US20180046550A1 (en) | Pre-filtering of join execution over multi-column range summaries and other synopses | |
| US20170316222A1 (en) | Method and System for Temporarily Implementing Storage Access Policies on Behalf of External Client Agents | |
| US9087083B2 (en) | Processing control in a streaming application | |
| JP6857196B2 (en) | How to optimize applications for computing systems with multiple different memory locations interconnected by one or more communication channels, non-temporary computer-readable storage media, including computer-readable programs, and systems. | |
| US20210208902A1 (en) | Cascading Data Configuration | |
| US8856338B2 (en) | Efficiently relating adjacent management applications managing a shared infrastructure | |
| CN117749799A (en) | Gray release method and device, electronic equipment and storage medium | |
| US20150154038A1 (en) | Scriptable hierarchical emulation engine | |
| US11650954B2 (en) | Replication continued enhancement method | |
| US10320890B1 (en) | Generating client applications from service model descriptions | |
| US20160048582A1 (en) | Dynamic alternate keys for use in file systems utilizing a keyed index |
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 |