How to handle east-west traffic with APISIX in Kubernetes?

[vb3328998]

Description

Problem Description

I'm trying to use APISIX to handle east-west (service-to-service) traffic in Kubernetes for gray release. Currently, I have:

1. Three deployments with different versions (base, v2, v3)
2. One service that selects all these deployments
3. Need to route traffic based on header 'deploy_version'

Environment

• APISIX version (run apisix version): 3.11.0
• Operating system (run uname -a): k8s
• OpenResty / Nginx version (run openresty -V or nginx -V):
• etcd version, if relevant (run curl http://127.0.0.1:9090/v1/server_info): 3.5
• APISIX Dashboard version, if relevant: 3.0.0
• Plugin runner version, for issues related to plugin runners:
• LuaRocks version, for installation issues (run luarocks --version):

[wklken]

if you have separate services like svc-v2/svc-v3

• use route.vars, two routes, same uri, but with different vars like: http_version==v2 and http_version==v3, to different upstream [easy to add or remove route]
• or you can use the traffic-split to split via the header to different upstream