help request: apisix uses ingress for configuration. If I want to configure routing using the traffic plugin, how can I avoid having route information be synchronously overwritten by ingress information?

[zydxxxxx]

Description

Hello, I am currently researching the use of apisix's traffic-split plugin for grayscale release. However, our company uses ingress to configure apisix's routing data.

How can I safely do this so that the ingress configuration does not overwrite the routing data of the traffic-split plugin?

Environment

• APISIX version (run apisix version):
• Operating system (run uname -a):
• 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):

[kayx23]

... ingress configuration does not overwrite the routing data of the traffic-split plugin

What do you mean by overwriting the routing data of the traffic-split plugin? Can you provide a scenario (that you don't want)?

[zydxxxxx]

... ingress configuration does not overwrite the routing data of the traffic-split plugin

What do you mean by overwriting the routing data of the traffic-split plugin? Can you provide a scenario (that you don't want)?

As you can see this is my ingress configuration。

Here are my routes and upstream I modified my route to look like 1 below, but the route eventually changed back to 2 Figure 1 Figure 2