Re: [DISCUSS] Draft of Podling Maturity Assessment for APISIX

2020-04-04 Thread Ming Wen
The latest pointing to master now, I will change it to the last apache release version. Thanks. Justin Mclean 于2020年4月5日 周日上午11:03写道: > HI, > > > both of them[3]. I've added instructions for the apache release, as well > as > > a developer-only tip for master. > > please take a look. thanks. > >

Re: [DISCUSS] Draft of Podling Maturity Assessment for APISIX

2020-04-04 Thread Justin Mclean
HI, > both of them[3]. I've added instructions for the apache release, as well as > a developer-only tip for master. > please take a look. thanks. What version is latest pointing to there? it a little unclear to me. By default a user should get the last released version not what is in master. T

Re: [DISCUSS] Draft of Podling Maturity Assessment for APISIX

2020-04-04 Thread Ming Wen
Hi, Justin, > Which is fine but what about your users? Users can find Installation and Quickstart in the GitHub's README.md for more information. I updated the full answer in the maturity assessment[1]. >Github is not an official release or archive area, you might want to mention the official one

Re: [DISCUSS] how about the design of APISIX eureka integration?

2020-04-04 Thread Ming Wen
> First, select nodes that the registry considers to be healthy. Then, from these nodes, select one that APISIX considers healthy. Which means there are two health checks here? One is Apache APISIX and one is Eureka. > From a usage scenario, dynamic DNS service should not be used. That loses the m

Re: [DISCUSS] how about the design of APISIX eureka integration?

2020-04-04 Thread ~Jarvis.Qiu
Hi, Ming Wen, >> Common registries: Eureka, Etcd, Consul, Zookeeper, Nacos etc. > Apache APISIX uses them for service discovery, so do you trust their health > check results? Usually there is no problem. > What if their health check results conflict with Apache APISIX's own > upstream health che