We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
简介:将具有一定特征或者比例的流量分配到需要被验证的版本中,用来观察新的验证版本的线上运行状态。
The text was updated successfully, but these errors were encountered:
进展如何了
Sorry, something went wrong.
这个项目是不是又烂尾了
zilongTong
rottenmu
No branches or pull requests
基于泳道的全链路灰度
简介:将具有一定特征或者比例的流量分配到需要被验证的版本中,用来观察新的验证版本的线上运行状态。
将应用中需要进行灰度测试的实例版本划分进一条泳道,形成一个逻辑隔离环境,一个微服务实例版本可以属于多个泳道。
全链路灰度发布规则配置后,会在泳道的入口的版本实例上对请求规则进行校验,以此来判断请求是否应该进入某一个泳道中。通常情况下,泳道入口是一个网关。
1.配置灰度规则,当请求在入口命中规则之后,流量会进入对应的泳道中。
2.当某一个微服务下的部署组没有被加入任何泳道中,请求将在该微服务下所有部署组的所有实例中轮询。经过该微服务后,请求将继续按照规则配置流入对应泳道。
3.泳道是一个隔离环境。当泳道上所有规则关闭后,流量不会进入泳道中。如希望恢复建立泳道前的流量分配方式,请将泳道删除。
The text was updated successfully, but these errors were encountered: