gubarba commented on issue #7470: URL: https://github.com/apache/apisix/issues/7470#issuecomment-1285558166
Indeed, IMHO standalone mode cuts out the flexibility that the default mode carries when managing multiple sources of routes configuration ( multiple teams mantaining multiple CRDs defined routes ) without the need of an external tool. I'm trying to undersand whether i should try to use standalone mode, but managing a single configmap to configure many websites and projects routes doesn't seem a nice way to go . Since i'm not willing to operate the ETCD Cluster that the control plane depends on ( I'm on EKS and can't use the cluster's ETCD, so I have to manage my own ), this would enable scaling the configuration managent on multiple teams scenarios, without the operational overhead of managing the ETCD cluster or other configuration centers ( Consul, etc) and sticking to kubernetes core features, such as configmaps and volumeMounts. -- 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]
