kubernetes-ingress

I wouldn't bet on that. :) F5 isn't the most visible corporation in terms of grassroots engagement, but NGINX itself has remained F/OSS all these years and newer projects like the Kubernetes Ingress Controller [0], Gateway Fabric [1], and NGINX Agent [2] are all Apache 2.0 licensed. Just like Unit. We do have commercial offerings, including the aforementioned NGINX Plus, but I think we've got a decent track record of keeping useful things open. [0]: https://github.com/nginxinc/kubernetes-ingress [1]: https://github.com/nginxinc/nginx-gateway-fabric [2]: https://github.com/nginx/agent

I 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/doc...

> the momentum in kubernetes is to leverage nginx as an ingress. There are many different groups, Nginx in fact has their own ingress controller [1] separate from K8S nginx ingress controller. HAProxy is older and harder to deal with for L7 ingress routing as compared to Nginx. The Istio project (using Envoy) [2] is gaining speed quickly though to become a much better ingress and internal proxy. 1. https://github.com/nginxinc/kubernetes-ingress 2. https://istio.io

NGINX also has their own ingress controller (in addition to the kubernetes community version): https://github.com/nginxinc/kubernetes-ingress

We've heard this quite a lot - there's actually a few ways to tackle this, one of the most common is to either use Ingress (which is a built in L7 load balancer) or run an nginx instance in a pod on the cluster (https://github.com/nginxinc/kubernetes-ingress), and, in either case, direct all traffic to your node port across your cluster. It's really one command to do either - if you have trouble, please ping me (aronchick (at) google)! Disclosure: I work at Google on Kubernetes