mlasevich opened a new issue, #1990: URL: https://github.com/apache/apisix-ingress-controller/issues/1990
### Description As I user I would like to reduce complexity of APISIX and IngressController configuration by running APISIX in (["standalone mode"](https://apisix.apache.org/docs/apisix/deployment-modes/#standalone)). In that mode APISIX is running of the YAML based static configuration, monitoring it and auto-reloading it as necessary. Ingress-Controller would, in this case, be simply responsible for updating that config file in ConfigMap as necessary based on CRDs/Ingress items There was already a request for this here https://github.com/apache/apisix-ingress-controller/issues/610 but it resulted in a much more complicated (if I understand it correctly) setup ([described here](https://github.com/apache/apisix-ingress-controller/blob/master/docs/en/latest/composite.md)) where ingress controller tries to emulate etcd and is intertwined with ingress-controller. This _seems_ to be a bit more complicated and fragile than I would like it to be. Is there any interest in simplifying it to actually use the "standalone" mode? Thanks -- 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]
