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.
With Opsani you can optimize NGINX Ingress Controller performance in the cloud. Powered by machine learning, Opsani processes metrics collected by Prometheus to ensure that the right amount of resources is consumed for higher performance and lower cost.
As you evaluate Ingress controllers, you’ll notice they fall into three categories: open source, default, or commercial. Learn the pros and cons for each here.
Learn about risks you might introduce by selecting the wrong Ingress controller, and key areas where you can future-proof your selection.
An Ingress controller can be one of the most powerful tools in your Kubernetes stack. Learn how to determine your ingress requirements so you can select the best option.