NGINX Ingress Controller now supports single sign-on with OpenID Connect. Release 1.10.0 also introduces new configuration queue metrics, annotations on log entries, better validation of annotations and secrets, support for NGINX App Protect user-defined signatures, and more.
Since our last update, the NGINX Unit team has released three versions, 1.19.0 through 1.21.0. New features include support for ASGI with Python, multi-threading with several languages (Java, Perl, Python, Ruby), regular expressions in routing conditions, and more.
NGINX Controller 3.7 introduces some major enhancements. The API definition workflow is redesigned to extend Controller’s app‑centric model to the API Management Module. The Developer Portal is generally available. And there are new features for easier API management and more security.
NGINX Unit 1.18.0 introduces filesystem isolation, the 'target' option to reduce redundancy in PHP app configuration, and URL encoding. It also includes features introduced in NGINX Unit 1.17.0: redirects, and fractional server weights for traffic distribution in upstream groups.
We announce the latest branches of NGINX Open Source, the stable 1.18 branch and the mainline 1.19 branch. New to the stable branch are dry-run mode for request rate and connection limiting; protection against timing attacks; more support for variable parameters, and more.
Release 1.7.0 of the NGINX Ingress Controller for Kubernetes includes certification of the Red Hat OpenShift Operator, support for TCP, UDP, and TCP Passthrough load balancing, a circuit breaker implementation, and improved validation and reporting for NGINX Ingress resources.
NGINX Unit 1.16.0 introduces two new features that are already familiar to NGINX users. First, it can load balance across a group of upstream servers using the round-robin method. Second, you can define what happens when a requested file can't be served, similar to the NGINX 'try_files' directive.