4 ms·
I don't know much of the history or politics. I've mostly been a "let's just use (open source, if it needs to be said out loud) nginx" fire-and-forget kind of
by philsnow 4y ago
I don't know much of the history or politics. I've mostly been a "let's just use (open source, if it needs to be said out loud) nginx" fire-and-forget kind of dude for a while now because I mostly don't care about this layer...
> We realize it complicated matters when we created [...] an open source Ingress controller for Kubernetes, [...] different from the community Ingress solution (also built on NGINX).
> It’s pretty clear that the Gateway API is going to take the place of the Ingress controller in the Kubernetes architecture. So we [...] will make the NGINX Kubernetes Gateway – which will be offered only as an open source product[...]
... but these two bits very much give me a feeling like they're planting their flag here and offering an open source version so that there's no "need" to go making another one that they don't control.
- thinkmassive 4y agoI think you hit the nail on the head! Here’s a summary (from F5 Nginx) of the key difference between nginxinc/kubernetes-ingress and kubernetes/ingress-nginx: https://github.com/nginxinc/kubernetes-ingress/blob/main/docs/content/intro/nginx-ingress-controllers.md https://github.com/nginxinc/kubernetes-ingress/blob/main/doc...