Hi, For now, the APISIX Ingress controller is a control plane component that does not handle static configuration of APISIX.
I think the most initial support is: * Allow some Upstreams that are not part of Kubernetes We need to make some changes to the processing logic of Upstream Chao Zhang <zchao1...@gmail.com> 于2022年5月17日周二 09:52写道： > Hi, > > That’s a good idea but I still have two questions. > > 1. The configuration of service regisry on APISIX side is in the > config.yaml and it’s static. How will you handle this case? > 2. How can users configure a service in a non-kuberentes registry (consul, > nacos and so on)? > > Chao Zhang > https://github.com/tokers > > On May 16, 2022 at 11:50:45, T.t.T!Ck. (ttt...@163.com) wrote: > > Hi, everyone. > > > Currently, Apisix-Ingress-Controller only supports Kubernetes services as > service discovery. However, Apisix supports multiple service discovery > registry, such as Eureka and Nacos . Therefore, Apisix-Ingress-Controller > is proposed to support more service discovery integration. > This will help users resolve legacy infrastructure issues and expand > Apisix-Ingress-Controller usage scenarios. ref #948 *[0] > <https://github.com/apache/apisix-ingress-controller/issues/948>* > > > > > I have a few simple thoughts about this proposal. I have created a proposal > for this, you can check this issue *[1] > <https://github.com/apache/apisix-ingress-controller/issues/1019>* > > > Best regards! > > > Gallardot >
