We look back over the most influential blog posts of 2018 on nginx.com, to remind you of what we’ve worked hard on improving to make your experience of NGINX even better. The year witnessed announcements and updates for many products in the NGINX Application Platform.
Release 1.4.0 of the NGINX Ingress Controller for Kubernetes includes support for TCP and UDP load balancing and a "power of two choices" load-balancing algorithm (Random with Two Choices), extended Prometheus support, and easy development of custom Annotations.
NGINX Plus R16 is a single, elastic ingress and egress tier for applications, consolidating the functionality of a load balancer, API gateway, and WAF with new features like cluster‑aware rate limiting, key‑value store, Random with Two Choices, enhanced UDP load balancing, and more.
NGINX has released version 1.3.0 of the NGINX Ingress Controller for Kubernetes. This release features Prometheus support, better Helm charts, mergeable Ingress resources, easier custom template management, health checks, and status reporting. Come to Github and get it.
NGINX Unit 1.3, available now, adds configuration parameters for various timeouts, configurable request body size, Ansible integration, and more. As in previous releases, all parameters can be defined dynamically, with no disruption to running services or loss of connectivity.
NGINX Controller R1, a new management tool for NGINX Plus instances, was released June 26th, 2018. It offers simplified configuration management; monitoring, alerting and troubleshooting; tagging; a configuration analyzer; instance inventory; and multi-cloud support.
NGINX Unit 1.2, available now, adds environment variables across application languages, versions, and sessions; php.ini configuration; and command-line configuration for Go executables. Parameters can still be defined dynamically, with no disruption to running services or loss of connectivity.
NGINX Unit 1.0, a multi-language applications server, launched today. Unit supports Python, PHP, Perl, Ruby, and Go, with more languages to come. Unit is dynamically configured using a REST API; there are no process reloads or service interruptions required for configuration changes to take effect.