2.13.0 release notes

August 28, 2023

NGINX Instance Manager 2.13.0 release notes

Upgrade Paths

NGINX Instance Manager 2.13.0 supports upgrades from these previous versions:

• 2.10.0 - 2.12.0

If your NGINX Instance Manager version is older, you may need to upgrade to an intermediate version before upgrading to the target version.

What’s new

This release includes the following updates:

• Easily manage access to specific objects with Resource Groups

  With NGINX Instance Manager, you can now combine Instances, Instance Groups, and Certificates into a Resource Group. This grouping can be used when defining roles to grant access to those specific objects. When objects are added to or removed from the Resource Group, the changes are automatically reflected in any roles that use the Resource Group. For more details, refer to Working with Resource Groups.

• Get version controlled NGINX configurations with an external commit hash

  The Instance Manager REST API supports setting and retrieving instances, instance groups, and staged NGINX configurations using a version control commit hash.

  To learn how to use a commit hash with NGINX configurations, refer to these topics:

  • Add Hash Versioning to Staged Configs
  • Publish Configs with Hash Versioning to Instances
  • Publish Configs with Hash Versioning to Instance Groups

• Configure analytics data retention with the nms.conf file

  You can set the data retention policy for analytics data, which includes metrics, events, and security events, in the nms.conf file. By default, metrics and security events are stored for 32 days, while events are stored for 120 days. To keep data for a longer period, update the retention durations in the nms.conf file.

• RBAC for security policies

  You can now use Role-Based Access Control (RBAC) to allow or restrict the level of access to security policies according to your security governance model.

• RBAC for log profiles

  You can now use Role-Based Access Control (RBAC) to allow or restrict access to log profiles according to your security governance model.

• Use NGINX Plus Health Checks to easily track NGINX Plus Usage with NGINX Instance Manager

  The NGINX Plus Health Check feature now allows you to monitor the count of both NGINX Plus and NGINX App Protect instances that you’ve deployed. You can view this information in the "NGINX Plus" area of the "Instance Manager" web interface, or through the /inventory API. For guidance on how to set this up, refer to the following documentation: View Count of NGINX Plus Instances.

• Improved log output for better JSON parsing

  In the log output, extra whitespace has been removed, and brackets have been removed from the log level field. This results in clean, parsable log output, particularly when using JSON log encoding.

Resolved issues

This release fixes the following issues. Use your browser’s search function to find the issue ID in the page.

• Staged configs fail to publish after upgrading NGINX Management Suite (37479)
• Error: "Failed to create secret" when reinstalling or upgrading NGINX Management Suite in Kubernetes (42967)
• An "unregistered clickhouse-adapter" failure is logged every few seconds if logging is set to debug. (43438)

Known issues

You can find information about known issues in the Known Issues topic.