Hi: I thought about it, there is also `service` in Kong, and here we are almost the same.
So I prefer to continue using `service`. On Tue, Oct 29, 2019 at 10:45 AM zhoujingk_49 <[email protected]> wrote: > Hi folks! > > > As we know Apisix is one of an Cloud Native APIGateway, and one of the > most important about Cloud Native is > Does our Apisix is friendly enough with Kubernetes？ > > > We all know “ service" is an important concept in Kubernetes, it's an > abstraction of pods. It's truly about describing a service things, provider > something ability to others. But the “Service” in Apisix, I wandering more > of > A router set than a Service. And a Apisix “service” would make someone > confused when using Apisix in Kubernetes environment. > > > So, what’s your opinion? > > > | | > idevz > | > | > [email protected] > | > > Idevz.org > > github.com/idevz > > > > > > -- *MembPhis* My github: https://github.com/membphis Our Book: OpenResty Best Practices <https://www.gitbook.com/book/moonbingbing/openresty-best-practices>
