Gallardot opened a new issue, #1019: URL: https://github.com/apache/apisix-ingress-controller/issues/1019
### Issue description 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 ### Environment One possible solution is to add `discovery_type` to `http[].backends` and `stream[].backend` of [`apisix_route_v2Beta3`](https://apisix.apache.org/zh/docs/ingress-controller/references/apisix_route_v2beta3). The default value is `kubernetes` and the behavior remains the same as now. Consul_kv, DNS, NacOS, Eureka are available based on [apisix's service integration configuration](https://apisix.apache.org/docs/apisix/discovery). If these are optional, these configurations will only be converted to apisix upstream configurations and will not be processed by parsing the endpoint through the kubernetes service. -- 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]
