Announcing F5 NGINX Ingress Controller v4.0.0
Today, we are announcing the release of F5 NGINX Ingress Controller v4.0.0!
To see the full list of changes, look here to our release notes on Github!
Support for F5 NGINX R33
This release of NGINX Ingress Controller brings with it support for the latest version of F5 NGINX Plus, NGINX R33.
If you aren’t yet familiar with the changes that NGINX R33 brings, and what that means for you, check out the announcement blog from Prabhat.
To see how to install NGINX Ingress Controller v4.0.0, check out this guided video from Akash Ananthanarayanan, where he shows exactly what to do to make sure you can get up and running with the latest version of NGINX Ingress Controller!
https://www.youtube.com/watch?v=amqnA5aeujY
Host Based Routing for Layer 4 Applications
One way many of our users save on infrastructure costs is by hosting multiple applications on the same node and identifying those applications through their hostname.
An example of this is hosting both a Reddis database and a Mongo database on the same node.
Prior to this release, this use case was not possible. If you needed access to multiple Layer 4 applications, they needed to be deployed on their own node.
With the release of NGINX Ingress Controller v4.0.0, and with the use of the TransportServer resource, this use case is now possible!
If this is a use case that you have, and you’re curious how to set this up, we have a set of example configurations here that you can deploy to get up and running quickly.
Updates to our logging format
In this release, we made an update to our logging library. For a while, NGINX Ingress Controller has been using the golang/glog. For this release, we have moved to the native golang library log/slog. This change was made for these reasons:
- By using a standard library, we ensure that updates are more consistent, and any known vulnerabilities are more likely to be addressed in a timely manner.
- By moving to log/slog, we enable support for a wider range of logging formats, as well as allowing log outputs to be displayed in a Structured format, and for faster log parsing.
For more details, look to our Configure Structure Logging section in our Upgrade to v4.0.0 docs
Resources
For the complete changelog for NGINX Ingress Controller v4.0.0, see the Release Notes. For more details on upgrading to NGINX Ingress Controller v4.0.0, see our upgrade guide here.
To try NGINX Ingress Controller for Kubernetes with NGINX Plus, start your free 30-day trial today or contact us to discuss your use cases.
If you would like to get involved, see what is coming next, or see the source code for NGINX Ingress Controller, check out our repository on GitHub!
We have weekly community meetings on Monday at 8:00AM Pacific/11:00PM Eastern/4:00PM GMT. The meeting link, updates, agenda, and notes are on the NGINX Ingress Controller Meeting Calendar. Links are also always available from our GitHub README.