We performance test NGINX Ingress Controller and the default Red Hat OpenShift Router in an OpenShift Cloud Platform cluster while scaling the number of backends up and down. The Router experiences significant latency and errors, but NGINX Ingress Controller almost none.
Do you need an Ingress controller to accept traffic into your Kubernetes environment? To help you decide, we offer a primer on the other services for getting external traffic into a cluster: kube-proxy, Cluster IP, NodePort, and LoadBalancer.
We recently jumped the NGINX Ingress Controller version number from 1.x to 2.x, to signal compatibility with version 1 of the Kubernetes API (released in Kubernetes 1.22). Find out why this matters and how to keep your Kubernetes apps running smoothly as versions change.
Explore six use cases where Kubernetes traffic‑management tools -- including F5 NGINX App Protect, Ingress Controller, and Service Mesh -- solve security problems. Help your SecOps teams collaborate with DevOps and NetOps to better protect your cloud‑native apps and APIs.
When you need an API gateway in Kubernetes, how do you choose among API gateway vs. Ingress controller vs. service mesh? We guide you through the decision, with sample scenarios for north-south and east-west API traffic, plus use cases where an API gateway is the right tool.
Many of our customers use BIG‑IP for load balancing to their Kubernetes clusters and NGINX Ingress Controller to handle cluster ingress‑egress traffic. For better interoperability, IngressLink tracks changes in the cluster so BIG-IP configuration can be updated faster.
We compare NGINX performance in bare-metal and virtualized (hypervisor) environments, finding a small but measurable performance cost for hypervisors. We also find that performance in Kubernetes environments is worse for network-bound but not CPU-bound operations.
Learn which NGINX Ingress controller is best for you, based on authorship, development philosophy, production readiness, security, and support.
The Ingress controller is an ideal location for centralized authentication and authorization in Kubernetes. We show how to implement single sign-on with NGINX Ingress Controller as the relaying party and Okta as the identity provider in the OIDC Authorization Code Flow.