2.7.0 release notes

December 20, 2022

NGINX Instance Manager 2.7.0 release notes

Upgrade Paths

NGINX Instance Manager 2.7.0 supports upgrades from these previous versions:

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

This release has the following changes in default behavior:

F5 WAF for NGINX upgrades are supported

You can upgrade F5 WAF for NGINX on managed instances where Instance Manager publishes F5 WAF for NGINX policies and configurations. For example, upgrade from release 3.12.2 to release 4.0.
NGINX Management Suite Config file is now in YAML format

With the release of NGINX Instance Manager 2.7, the NGINX Management Suite configuration file is now in YAML format. Through the upgrade process, your existing configuration will automatically be updated. Any settings you have customized will be maintained in the new format. If you have existing automation tooling for the deployment of the NGINX Management Suite that makes changes to the configuration file, you will need to update it to account for the change.
Existing NGINX Agent configuration kept during upgrade to the latest version

When upgrading NGINX Agent, the existing NGINX Agent configuration is maintained during the upgrade. If the Agent configuration is not present in /etc/nginx-agent/nginx-agent.conf, a default configuration is provided after NGINX Agent installation.

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

Instance Manager reports old NGINX version after upgrade (31225)
Instance Manager returns a "Download failed" error when editing an NGINX config for instances compiled and installed from source (35851)
Null data count is not correctly represented in the NGINX Plus usage graph. (38206)
When upgrading a multi-node NMS deployment with helm charts the core, dpm, or integrations pods may fail to start (38589)
When upgrading Instance Manager from v2.4 to later versions of Instance Manager, certificate associations are no longer visible. (38641)
NGINX App Protect policy deployment status not reflecting removal of associated instance. (38700)
When upgrading a multi-node NMS deployment with helm charts the ingestion pod may report a "Mismatched migration version" error (38880)
After a version upgrade of NGINX Instance Manager, NMS Data Plane Manager crashes if you publish NGINX configuration with App Protect enablement directive (app_protect_enable) set to ON (38904)

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