yes, I think APISIX does not need to make any changes to achieve the purpose of service discovery too. I will make some test with this later.
On Sat, May 30, 2020 at 11:06 AM agile6v <agil...@apache.org> wrote: > Hi Ming, > > As far as my understand at the moment, APISIX does not need to make any > changes to achieve the purpose of service discovery. APISIX points the dns > address to the consul and the application register it to the consul based > on the specific identifier like foo.com. Not sure what i missed. > > Thanks, > agile6v > > > > On 2020/05/29 09:29:20, Ming Wen <wenm...@apache.org> wrote: > > Hello, > > I am not sure do we using the `lua-resty-dns` to do dns_resolver work, > and > > is APISIX supports Consul DNS for service discovery? > > > > for example 127.0.0.1:8600 is the address to the Consul DNS resolver, > then > > we add configure like this in `config.yaml`: > > dns_resolver:127.0.0.1:8600 > > > > At this point any upstream hostname, for example `foo` in upstream_url= > > http://foo/index.html, will be resolved by Consul. > > > > Thanks, > > Ming Wen, Apache APISIX & Apache SkyWalking > > Twitter: _WenMing > > >
