Live data from Hacker News

Kong gateway reaches 1.0 GA, now supports service mesh

konghq.com

41–50 of 51 posts

Re: Kong gateway reaches 1.0 GA, now supports service mesh

#41

Hi all, I was the lead developer on the service mesh implementation. I've just pushed https://github.com/Kong/kubernetes-sidecar-injector public, which should make deploying kong a service mesh simple on kubernetes. Let me know if you have any questions, I'll try and check over the next few days.

I see that your Kong service mesh using nginx as the underlying proxy. Are there any plans to use Envoy proxy in future? Currently Istio and Linkerd2 are based on Envoy. Unlike nginx, envoy doesnt have an enterprise version where some enterprise features are held off. Also envoy has very good observability and traffic management features.

Re: Kong gateway reaches 1.0 GA, now supports service mesh

#42

Hi all, I was the lead developer on the service mesh implementation. I've just pushed https://github.com/Kong/kubernetes-sidecar-injector public, which should make deploying kong a service mesh simple on kubernetes. Let me know if you have any questions, I'll try and check over the next few days.

I see that your Kong service mesh using nginx as the underlying proxy. Are there any plans to use Envoy proxy in future? Currently Istio and Linkerd2 are based on Envoy. Unlike nginx, envoy doesnt have an enterprise version where some enterprise features are held off. Also envoy has very good observability and traffic management features.

linkerd2 is not based on Envoy :) It has its own proxy written in rust : https://github.com/linkerd/linkerd2-proxy

Re: Kong gateway reaches 1.0 GA, now supports service mesh

#43
post #38
post #18

Earlier quoted context omitted.

(Caveat: I’m the CEO of Tyk) Tyk offers a more “batteries included” approach to Kong, and so doesn’t rely on external plugin authors to extend the ecosystem. 100% of our dev team are constantly working on our open source components and we like to keep it that way. Because of that, Tyk isn’t “open core” like Kong is, there’s no lock-in or levers to get you to buy our value-adds like our Management Dashboard GUI or our…

Kong has an OpenID Connect plugin that comes with Enterprise, but there are at least three OpenID Connect plugins made by the community, one of them is from Nokia. I work for Kong and I am an author of that enterprise OpenID Connect plugin. Maybe that is a biggest exception to me, as otherwise I'd say that almost all of my code and related goes directly to OSS.

For the interested, that Nokia Open ID Connect plugin is here [0]. I had to hack around with it a bit to get some extra functionality and support ADFS [1].

[0] https://github.com/nokia/kong-oidc

[1] https://github.com/philbarr/kong-oidc-adfs

Re: Kong gateway reaches 1.0 GA, now supports service mesh

#44

Hi all, I was the lead developer on the service mesh implementation. I've just pushed https://github.com/Kong/kubernetes-sidecar-injector public, which should make deploying kong a service mesh simple on kubernetes. Let me know if you have any questions, I'll try and check over the next few days.

I see that your Kong service mesh using nginx as the underlying proxy. Are there any plans to use Envoy proxy in future? Currently Istio and Linkerd2 are based on Envoy. Unlike nginx, envoy doesnt have an enterprise version where some enterprise features are held off. Also envoy has very good observability and traffic management features.

Curious to see if Kong can do true hitless reloads without proxy restart. Envoy can do this but I thought only NGINX Plus has this capability?

Re: Kong gateway reaches 1.0 GA, now supports service mesh

#46
post #38

Earlier quoted context omitted.

Kong has an OpenID Connect plugin that comes with Enterprise, but there are at least three OpenID Connect plugins made by the community, one of them is from Nokia. I work for Kong and I am an author of that enterprise OpenID Connect plugin. Maybe that is a biggest exception to me, as otherwise I'd say that almost all of my code and related goes directly to OSS.

For the interested, that Nokia Open ID Connect plugin is here [0]. I had to hack around with it a bit to get some extra functionality and support ADFS [1]. [0] https://github.com/nokia/kong-oidc [1] https://github.com/philbarr/kong-oidc-adfs

[deleted]

Re: Kong gateway reaches 1.0 GA, now supports service mesh

#47
post #44

Earlier quoted context omitted.

I see that your Kong service mesh using nginx as the underlying proxy. Are there any plans to use Envoy proxy in future? Currently Istio and Linkerd2 are based on Envoy. Unlike nginx, envoy doesnt have an enterprise version where some enterprise features are held off. Also envoy has very good observability and traffic management features.

Curious to see if Kong can do true hitless reloads without proxy restart. Envoy can do this but I thought only NGINX Plus has this capability?

Yes, Kong's entity configuration (including upstream services) are managed via the runtime, not via reading a config file. This allows for updating proxy configuration without restarting the process itself, allowing for zero-downtime config changes.

Re: Kong gateway reaches 1.0 GA, now supports service mesh

#48

Earlier quoted context omitted.

I've used both, Kong is more "pluggable" and easier to extend in my experience. Also, the ecosystem and community around Kong is much stronger than Tyk's which is amazing.

I'd argue Tyk is easier to extend Tyk, as they include many plugins already baked-into their OS gateway. If you want to extend Kong with some custom plugins I think Lua is your only option. With Tyk you can use pretty much any programming language to write your middleware. Gets my vote

It was messy and bloated, we had many different plugins built in different languages and couldn't share patterns and code.

Single language simplified our architecture, less plugins created less bloat, and ultimately we moved faster with Kong.

Engineers also really enjoyed that they got to learn something new and also could get into C easily with Kong as well using LuaJIT.

Re: Kong gateway reaches 1.0 GA, now supports service mesh

#49
post #28
post #18

Earlier quoted context omitted.

(Caveat: I’m the CEO of Tyk) Tyk offers a more “batteries included” approach to Kong, and so doesn’t rely on external plugin authors to extend the ecosystem. 100% of our dev team are constantly working on our open source components and we like to keep it that way. Because of that, Tyk isn’t “open core” like Kong is, there’s no lock-in or levers to get you to buy our value-adds like our Management Dashboard GUI or our…

> you should be able to do all API Management without having to pay us a penny. I contacted Kong sales once about OpenID connect support, they basically dismissed us as too small. Needless to say we took Kong out of our stack and won't consider it again.

That's unfortunate, there is a good open source one that I have used and works well. The enterprise one is definitely more verbose but the open source one works well!

Re: Kong gateway reaches 1.0 GA, now supports service mesh

#50
post #32

Earlier quoted context omitted.

What about performance, did you use it so much you got a sense of that? To me there is nothing that beats haproxy so far.

They are different products. Nginx and haproxy are more comparable. If you like HAproxy as a load balancer, you can easily use it with Kong. A lot of people do just that.

But then what is Kong doing?
Post reply on HN