flylan opened a new issue, #10786: URL: https://github.com/apache/apisix/issues/10786
### Description I have a question about apisix configuration，Is there a deployment method that allows some of the configuration of Apisix to be stored in YAML (such as domain name resolution configuration) and some configuration to be stored in ETCD (such as IP pool in IP blocking plugin) From the perspective of operation and maintenance personnel, most configurations are not frequently changed. These configurations should be stored in yaml files, which make people more confident and convenient for version tracking in git. Moreover, yaml configurations can be like code, distinguishing different environments and following the devops process. From the perspective of developers, some configurations need to be changed in real time, such as the IP pool in the IP blocking plugin. Programs can dynamically block certain abnormal IPs based on business conditions, such as crawler IPs or IPs with abnormal traffic. I noticed that Apisix 3. x version provides the decoupled mode, which separates the data plane from the control plane. I'm not sure if this mode can solve my problem https://apisix.apache.org/docs/apisix/deployment-modes/ ### 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`): -- 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]
