0prodigy opened a new issue, #8880:
URL: https://github.com/apache/apisix/issues/8880

   ### Current Behavior
   
   ```
   {
     "uri": "/s9xu90sq/*",
     "name": "s",
     "plugins": {
       "key-auth": {
         "header": "nbx-key",
         "hide_credentials": false,
         "query": "nbx-key"
       },
       "proxy-rewrite": {
         "regex_uri": [
           "^(/[^/]+)([/:].*)",
           "$2"
         ],
         "use_real_request_uri_unsafe": false
       },
       "traffic-split": {
         "rules": [
           {
             "weighted_upstreams": [
               {
                 "upstream_id": "3sdsshxf",
                 "weight": 5
               },
               {
                 "weight": 1
               }
             ]
           }
         ]
       }
     },
     "upstream_id": "2kkhtea5",
     "labels": {
       "serving_id": "s9xu90sq",
       "traffic_strategy": "custom_weights"
     },
     "status": 1
   }
   ```
   
   Above configuration doesn't route traffic based on weight every call is 
forward to upstream set on route no effect of traffic-split plugin 
   
   ### Expected Behavior
   
   API call should be distributed based on weight set in traffic-split which 
5:1 
   
   ### Error Logs
   
   _No response_
   
   ### Steps to Reproduce
   
   1. Create upstreams
   2. Create route using upstream id 
   
   
   ### Environment
   
   - APISIX version (run apisix version): 3.0.0
   - Operating system (run uname -a): Linux (x86_64 GNU/Linux)
   - OpenResty / Nginx version (run openresty -V or nginx -V): 
openresty/1.21.4.1
   - etcd version, if relevant (run curl http://127.0.0.1:9090/v1/server_info):
   - APISIX Dashboard version, if relevant:
   - Plugin runner version, for issues related to plugin runners:
   - LuaRocks version, for installation issues (run luarocks --version):


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to