Hacker News Reader

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.

View on HN

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

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.

Kong indeed can, it's part of our API gateway for years :)

Reply on news.ycombinator.com