Default gray release method and device based on Kubernetes platform and load balancing component

Abstract

The invention relates to a default gray release method and device based on a Kubernetes platform and a load balancing component. The default gray release method comprises gray release configuration parameter information. In the implementation process, gray release configuration parameter information is issued to a micro-service gateway, when a user request passes through the gateway, the gateway carries out initial gray marking on the user request in combination with the gray release configuration parameter information, and the control right of flow switching and execution in the gray release process is placed in the micro-service gateway. According to the method, a service grid technology is not used, an online operation service and a gray scale test service are isolated by using Namespace, service communication in the two Namespaces is broken through at the same time, the limitation that the resource utilization rate is only 50% in a traditional blue-green publishing scheme is avoided, the utilization rate of hardware resources is maximized, the traffic borne by different versions of services can be switched by adjusting the gray release parameters, and fast rollback is realized when the gray test fails.

Description

technical field [0001] The present invention relates to the field of computer technology, in particular to a default gray-scale publishing method and device based on a Kubernetes platform and a load balancing component. Background technique [0002] In recent years, with the rapid growth of the number of Internet users, the requirements for Internet products have become higher and higher. On the one hand, it is required to provide users with stable services, and on the other hand, it is required to respond to user needs in a timely manner and to rapidly iterate products. Therefore, based on the comprehensive consideration of system stability and rapid business iteration, grayscale release is generally used to release new versions. [0003] After the traditional centralized service registration discovery mechanism such as Nacos’ microservice cluster is migrated to the Kubernetes platform, due to the use of the Kubernetes service discovery mechanism, most of the traditional gr...

AI Technical Summary

Problems solved by technology

[0003] After the traditional centralized service registration discovery mechanism such as Nacos’ microservice cluster is migrated to the Kubernetes platform, due to the use of the Kubernetes service discovery mechanism, most of the traditional grayscale release components migrated to the K8S environment fail; in the Kubernetes management platform Currently, it is a common practice to use cloud-native technologies such as Service Mesh to implement service grayscale release.

However, for most small and medium-sized enterprises, cloud-native technologies such as Service Mesh have a steep learning curve, require a certain amount of time and cost, and are difficult to maintain.

Images