lpiob commented on issue #610: URL: https://github.com/apache/apisix-ingress-controller/issues/610#issuecomment-1744281933
I partially agree with @mlasevich - since Apisix can be controlled by a configmap, this configmap could be produced and updated by ingress-controller and we would not need a mock etcd. It does not rule out CRDs. However, I assume that you can't have everything at once and I am able to accept mock-etcd in a transitional state. I have a question, about the pod configuration. The composite.md documentation shows an example in which one pod has both apisix-ingress-controller and apisix-gateway. This certainly made testing easier, but I'm not sure whether it's intended to be used that way "in production". The same scheme was [duplicated within the actual ingress-controller chart](https://github.com/apache/apisix-helm-chart/pull/624), making the chart from apisix-gateway now unnecessary and causing the ingress-controller to be scaled simultaneously with apisix-gateway. Was this intended? If not then I am able to prepare a fix for chart. -- 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]
