This blog describes the performance you can achieve with the NGINX Ingress Controller for Kubernetes, in terms of three metrics: requests per second, SSL/TLS transactions per second, and throughput. The full NGINX and Kubernetes configurations we used are included.

There are always concerns when an enterprise acquires open source projects. NGINX CEO Gus Robertson explains why F5 is committed to maintaining and growing NGINX Open Source and other open source projects.

NGINX Unit 1.8.0 introduces internal routing of requests based on host, URL, and HTTP method, This sets the framework for full Layer 7 request processing, necessary for further development of Unit’s web server functionality.

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 Unit 1.5 adds support for Node.js applications, which extends the set of supported languages to six: Go, JavaScript (Node.js), Perl, PHP, Python, and Ruby. It also adds support for encrypting connections with SSL/TLS, and dynamic updating of security certificates.

In this companion post to our video “NGINX Unit: Live App Updates at 100% Uptime”, we provide all the background and details for each step so you can follow along as we update an application in a multilingual NGINX Unit environment without disruption or downtime.

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 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.

A newly discovered security threat exploits a configuration that allows remote users to specify the server for a request in the HTTP Host header, and thus access potentially sensitive information. In this post we explain how to prevent this “cloud metadata” attack.

NGINX Amplify now features MySQL support. Amplify monitors the entire LEMP stack, including variations: Linux, (E)NGINX, MySQL/MariaDB/Percona, PHP, and PHP frameworks such as WordPress. This blog post shows you how to configure the Amplify MySQL plug-in, metrics monitored, and troubleshooting.

NGINX Unit supports PHP, which is very widely used for web programming. NGINX Unit therefore supports WordPress, written in PHP, and which is a content management system and application used by more than 30% of the sites on the Web. Use this blog post to install Unit and NGINX together with WordPress.

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.

NGINX now proxies gRPC traffic, so you can terminate, inspect, and route gRPC method calls. Manage encryption and load balance gRPC traffic.

You can now download the Unit beta, version 0.6, with advanced process management, Perl support, an official Docker container, and more.

The Meltdown and Spectre vulnerabilities stem from commonly found security flaws in microprocessors. They require patches to most OSs.

How to tune your NGINX installation to meet, and beat, published performance benchmark – includes caching, SSL/TLS, and hardware settings.

Senior software engineer Anatoly Mikhaylov shows how to use Amplify as a visualization and reporting tool for fixing dodgy TCP connections.