You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by "Revolyssup (via GitHub)" <gi...@apache.org> on 2023/07/12 14:43:27 UTC
[GitHub] [apisix] Revolyssup commented on issue #9824: help request: traffic_split来做灰度发布时,nacos服务实例如何在请求头中获取到该请求是否是灰度流量
Revolyssup commented on issue #9824:
URL: https://github.com/apache/apisix/issues/9824#issuecomment-1632659702
Translation:
When using traffic_split for grayscale publishing, the current solution:
1. The microservice middleware used is: nacos, (the nacos used by production and grayscale is the same set), when registering the service, the corresponding nacos instance will be set as grayscale or production.
2. The same route is used for production and grayscale. The production environment and grayscale environment use different upstreams (the lua code and dashboard of the upstream part have been changed, and an attribute (production or grayscale) has been added to the upstream. According to this attribute, find the corresponding nacos instance. For example, the attribute value is grayscale, the specific logic: if the corresponding grayscale nacos instance cannot be found, it will find the production instance)
After making such changes: encountered a problem:
When the request reaches the specific nacos service, it is impossible to know whether the request comes from the production environment or the grayscale environment.
Expectation: The nacos service instance can obtain whether the request is grayscale traffic in the request header
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org