NGINX Controller Releases
NGINX Controller Version 2.5.0
These release notes provide general information and describe known issues for NGINX Controller version 2.5.0, in the following categories:
Known Issues
- Clients deploying controller-agent on CentOS 6 need to manually modify the logging level of controller-agent to ERROR level from INFO and restart controller-agent.
- Administrators who delete a JWT policy will still see that policy in the environment select list. They should not select/configure a deleted policy.
- NGINX Plus instances managed by the API Management module must be associated with a single Entry Point
- Amazon Linux 2. Docker installation issues: Controller install script cannot handle the setup of docker. Please install docker before running the controller install script.
NGINX Controller Version 2.4.0
These release notes provide general information and describe known issues for NGINX Controller version 2.4.0, in the following categories:
Updates
Load Balancer
- The Instances page is now read-only, displaying the configuration that is currently running on each instance. This will help ensure nobody accidentally overwrites expected policy. To edit instance configurations, you must use Configuration Templates (Load Balancing > Configurations).
- If an instance is associated to a Load Balancing Configuration Template or an API Management Entry Point, that information is reflected at the bottom of the page.
- Instances that are not associated with a module can be promoted to Configuration Templates at the bottom of the Instances page for load balancing purposes, or associated with an Entry Point for API Management purposes.
- Configuration Templates > Instances
- You can now associate instances to a Configuration using tags.
- Last Modified timestamp now shows the last time the configuration was changed, whether manually or through Controller.
Known Issues
- Amazon Linux 2. Docker installation issues: Controller install script cannot handle the setup of docker. Please install docker before running the controller install script.
- NGINX Plus instances managed by the API Management module must be associated with a single Entry Point.
NGINX Controller Version 2.3.0
These release notes provide general information and describe known issues for NGINX Controller version 2.3.0, in the following categories:
Updates
Platform
- Configure dashboard graph sets using one or more tags
- Support spaces in upstream group name, route alias, system alias
Load Balancer
- Configuration Templates
- Ability to preview config file
- Additional feedback around in-progress config push
API Management
- Ability to edit environment policies
- Usability improvements to API Definitions page
- Entry point hostname color-coding:
- Grey - config not pushed to the entry point
- Green - config pushed, all associated instances are online
- Yellow - config pushed, one or more instances offline & one or more instances online
- Red - config pushed, all instances offline
- Number of unrouted resources is displayed for each environment
- Entry point hostname color-coding:
Known Issues
- Amazon Linux 2. Docker installation issues: Controller install script cannot handle the setup of docker. Please install docker before running the controller install script.
NGINX Controller Version 2.2.0
These release notes provide general information and describe known issues for NGINX Controller version 2.2.0, in the following categories:
Updates
NGINX Controller Version 2.1.0
These release notes provide general information and describe known issues for NGINX Controller version 2.1.0, in the following categories:
NGINX Controller Version 2.0.0
These release notes provide general information and describe known issues for NGINX Controller version 2.0.0, in the following categories:
Updates
Load Balancer
- Configuration Templates
- Config
- Associated Instances
- Version History
- Version Differencing
- Arbitrary Reverting
- Multi-push from Load Balancing → Instances
- Notifications for multi-push status
- ServiceNow alerting integration
- Ability to enable error_log and access_log in virtual server
- Renamed Amplify metrics
- Rename tab from “Configure” → “Load Balancing”
- Ability to tag instances from the ‘Load Balancing → Instances’ tab
- Config-push deferral - ability to change a config and save it without pushing
- Promote session persistence to its own section (Upstream Group config)
- Offline installer / updater
- Various bug-fixes
Known Issues
- If upgrading from a previous version of Controller, password needs to be updated/reset.
- Load Balancing - Instances page hangs when there are no hosts registered in Controller.
- Load Balancing - Orange indicators will appear when you have unsaved changes, and may take several minutes to accurately reflect the correct status.
- API Management - When configuring multiple rate limit policies for an Environment, each must use the same status code.
NGINX Controller Version 1.0.1
These release notes provide general information and describe known issues for NGINX Controller version 1.0.1, in the following categories:
Updates
- Alerts - fix issue where editing an alert with threshold could result in an error
- Analyzer - fix issue where old SSL cert could still be evident in the report alongside the new cert that replaced it
- Analyzer - show appropriate message when port is missing for the listen directive
- Configure - provide better error descriptions in the UI
- Configure - fix issue where error notifications disappeared too quickly before they could be fully read
- Configure - fix issue where user would see “undefined” error when loading a config that included a stream block
- Configure - fix issue where virtual server SSL block is inactive after a page reload
- Configure - fix issue where empty directives were not copied to the generated config file
- Configure - fix issue where proxy is not allowed in regex location
- Configure - fix issue where the validation for healthcheck URI does not allow for query params
- Configure - fix issue of no validation for duplicate upstreams
- Configure - fix the wrong visualisation of healthcheck config after a push config action fails
- Configure - fix error about server name being too long in the generated config