-
How To Gateway With Ingress - 140 Days InGate - Marco Ebert & James Strong
-
The ingress-nginx controller is provided by the Kubernetes team officially.
On the other hand, F5, the company behind NGINX, provides the NGINX Ingress controller. And, if you want to use Gateway API, then it provides a Gateway API implementation as well : the NGINX Gateway Fabric.
Now, InGate is to ingress-nginx, as NGINX Gateway Fabric is to NGINX Ingress.
REFER : How does Ingate plan to differentiate itself from other NGINX-based Gateway API implementations?.
-
Other than being a Kubernetes SIG backed NGINX based Gateway API implementation, there is another proposal : InGate as a generic Gateway API controller.
Currently, each Gateway API implementation needs to implement a Gateway API controller.
With this proposal implemented, InGate will be the common Gateway Controller. And there will NGINX / Traefik / Cilium etc. based backends will be responsible for only maintaining the proxy configuration.
InGate, conceptually, will be similar to the core Cluster API controller.
You can view the full Enhancement Proposal here.
-
The ingress-nginx controller is split into the control-plane and the data-plane.
The control-plane watches for Kubernetes resources like Ingresses and Services. It then sends corresponding NGINX configuration updates to the data-plane.
The data-plane runs the actual NGINX proxy, listen at the NodePort.
REFER : Control plane and Data plane split.
-
You can learn about how to run them, here.
-
kubvernor : A Kubernetes Gateway API implementation in Rust!
ChatGPT thread : https://chatgpt.com/share/68b6084e-fc54-8000-b591-2a84a6cc5e29.