Changelog (original) (raw)

Stay up-to-date with what’s new and improved in the F5 NGINX One Console.

The Config Sync Group detail page now includes a dashboard containing traffic metrics which mirror those on the Instance detail dashboard. The reported numbers are aggregated from the data reported by the Instances belonging to the Config Sync Group.

Previously the network IO metrics presented on the Instance detail dashboard represented system-level network traffic, but will now only represent traffic served by NGINX directly. This applies to the new Config Sync Group detail dashboard as well.

An issue has been fixed with the disk usage data presented on the Instance detail dashboard, and disk usage should now be correctly broken up by mount point in all cases.

For each Instance, you can now review system traffic, in and out, in bits per second. NGINX One Console no longer uses a cumulative value.

You can now graph any two metrics simultaneously on one chart within the Metrics tab for each Instance in the NGINX One Console UI.

You can now configure the following for F5 WAF policies directly in the NGINX One Console:

• Signature Sets
• Signature Exceptions
• Parameters
• URLs
• Cookies

For more details, see the F5 WAF Integration Guide .

• Start with how you can Author templates
• Automate with our experimental endpoints for NGINX One Console templates

Your instances which run in dual-stack or IPv6-only environments can now communicate with NGINX One Console APIs through IPv6 addresses. See the Getting Started Guide for the IP address ranges you need to allow in your firewalls.

You can now incorporate F5 WAF for NGINX in NGINX One Console UI. For details, see Secure with F5 WAF for NGINX.

In NGINX One Console, you can:

• Toggle between Default policy bundles
• Set blocking or transparent Policy enforcement mode

You can now monitor your NGINX Ingress Controller deployments. For details, see how you can Connect to NGINX One Console.

Unlike other NGINX instances, when you connect NGINX Ingress Controller to NGINX One Console, access is read-only. Refer to our NGINX Ingress Controller for details on how to modify these instances.

We have added support for NGINX Agent 3.x in NGINX One Console. You can now:

• Manage data plane instances with NGINX Agent version 3.

You can now import and export your Staged Configs from the UI and with our APIs. This can help you deploy Staged Configs on the systems of your choice.

We have added support for namespaces in N1C. You can now:

• Manage resources in isolation in different namespaces.
• Configure granular user permission controls base on namespace.

We now include an alert in the F5 Distributed Cloud when affected by one or more CVEs.

We now include an alert in the F5 Distributed Cloud when new instances are registered in the F5 NGINX One Console.

We have added API groups that align with the features and functionality in the NGINX One Console. You can now:

• Use our narrowly scoped API groups.
• Tailor access policies with custom roles.

• Custom role assignments: You can set up custom roles for users or service accounts.
• Namespace-based permissions: With namespaces, you can configure API group permissions to support least privilege.

For more information, read Custom roles and API groups.

It allows you to:

• Save Your Progress: Staged Configurations allow you to work on configuration changes without the need for a fully functional setup. You can create these drafts from scratch, an existing Instance, another Staged Configuration, or a Config Sync Group.
• No Immediate Validation Required: You don’t have to immediately address syntax or configuration issues. Your Staged Configuration doesn’t have to be valid until you publish it to an Instance or a Config Sync Group.
• Manage through our API: You can easily manage your Staged Configurations programmatically through our API.

With the NGINX One Console, you can now manage certificate deployment in Config Sync Groups.

You can:

• Add a certificate to a Config Sync Group
• Remove a deployed certificate from a Config Sync Group

For more information, including warnings about risks, see our documentation on how you can:

• Add a file
• Manage certificates

Using the NGINX One Console you can now:

• See a history of changes to the configuration on an instance or a Config Sync Group, as well as the content of the previous five configs published to that object
• Review the differences between the current and other saved configurations
• Revert to older configurations as needed

In the F5 NGINX One Console, you can now select lines from your configuration files, and then select Explain with AI. The F5 AI Assistant explains those lines based on the official NGINX documentation.

From the NGINX One Console you can now:

• Monitor all certificates configured for use by your connected NGINX Instances.
• Ensure that your certificates are current and correct.
• Manage your certificates from a central location. This can help you simplify operations and remotely update, rotate, and deploy those certificates.

For more information, see the full documentation on how you can Manage Certificates.

Config Sync Groups are now available in the F5 NGINX One Console. This feature allows you to manage and synchronize NGINX configurations across multiple instances as a single entity, ensuring consistency and simplifying the management of your NGINX environment.

For more information, see the full documentation on Managing Config Sync Groups.

NGINX Instance objects that have been unavailable for a set period will be automatically cleaned up (deleted). By default, this period is 24 hours from the time the NGINX Instance object was last updated. An administrator can change or disable the cleanup process in the "Instance Settings" under Settings. Events will be generated for NGINX Instances that have been automatically cleaned up. See "Events" for a list of NGINX Instances that have been deleted automatically.

You can now view NGINX CVEs on the Security page. The listed CVEs affect official releases of NGINX Open Source and NGINX Plus.

Select the link for each CVE to see the details, including the CVE’s publish date, severity, description, and the affected NGINX products and instances.

You can now make configuration changes to your NGINX instances. For more details, see View and edit NGINX configurations.

We’ve updated the Instance Details and Data Plane Keys pages to make it easier to go between keys and registered instances.

• On the Instance Details page, you can now find a link to the instance’s data plane key. Select the "Data Plane Key" link to view important details like status, expiration, and other registered instances.
• The Data Plane Keys page now includes links to more information about each data plane key.

• API responses now use "object_id" instead of "uuid". For example, key_1mp6W5pqRxSZJugJN-yA8g. We’ve introduced specific prefixes for different types of objects:
  • Use key_ for data-plane keys.
  • Use inst_ for NGINX instances.
  • Use nc_ for NGINX configurations.
• Likewise, we’ve updated the JSON key from uuid to object_id in response objects.

We’re thrilled to introduce NGINX One, an exciting addition to our suite of NGINX products. Designed with efficiency and ease of use in mind, NGINX One offers an innovative approach to managing your NGINX instances.

To help you get started, take a look at the Getting Started Guide. This guide will walk you through the initial setup and key features so you can start using NGINX One right away.