SuperBo opened a new issue, #10836:
URL: https://github.com/apache/apisix/issues/10836

   ### Current Behavior
   
   I have issue with ApisixRoute when defining more labels.
   
   Apisix controller error
   `│ 2024/01/17 07:15:48 [error] 53#53: *4 stream [lua] config_etcd.lua:520: 
load_full_data(): failed to check item data of [/apisix/stream_routes] 
err:additional properties forbidden, found labels ,val: 
{"upstream_id":"ee8deae1","update │`
   
   Apisix Ingress error
   
   `2024-01-17T15:11:58+08:00   error   apisix/apisix_route.go:379      failed 
to sync ApisixRoute to apisix    {"error": "1 error occurred:\n\t* unexpected 
status code 400; error message: {\"error_msg\":\"invalid configuration: 
additional properties forbidden, found labels\"}\n\n\n"}`
   
   <img width="800" alt="Screenshot 2024-01-17 at 2 18 39 PM" 
src="https://github.com/apache/apisix/assets/2666479/cb3481c1-4d60-4917-8c9d-d5a9b8b435b9";>
   
   
   ### Expected Behavior
   
   Labels are used for management and not related to the config. So it 
shouldn't affect config and routing.
   
   ### Error Logs
   
   │ 2024/01/17 07:15:48 [error] 53#53: *4 stream [lua] config_etcd.lua:520: 
load_full_data(): failed to check item data of [/apisix/stream_routes] 
err:additional properties forbidden, found labels ,val: 
{"upstream_id":"ee8deae1","update │
   
   ### Steps to Reproduce
   
   Define ApiSixRoute with additional labels in metadata
   
   ### Environment
   
   - APISIX version (run `apisix version`): 3.7.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`):
   - 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