The services within the NGINX Controller namespace are using cleartext protocols inside the cluster. Intra-cluster communication does not use TLS. Intra-cluster communication does not use TLS (5347) For information about a vulnerability fix, including the recommended action to take, see the linked AskF5 Solution Article for details. Vulnerability issues are disclosed only when a fix is available. Adds support for NGINX Plus R23 p1 and R24 p1. Improvements to the Data Explorer make it easier to see your data’s dimensions and preview the discrete values.NGINX Controller v3.18.0 includes the following new features, improvements, known issues, and bug fixes: Enabling WAF when creating or updating a component using the web interface might fail for non-admin users (26579).The peer count alert needs to be configured with a multiplier of the reporting period (26507).Search by the issue ID – the number in parentheses – to locate the details for an issue. This release includes the following fixes. These release notes provide general information and describe known issues for NGINX Controller v3.18.1, in the following categories: This is to avoid duplicating health checks. If a backend workload is shared with multiple components, and monitoring is the same for two or more of those components, then only one health check is generated now. Resolves an issue that created duplicate health checks for app componentsĪ health check is generated for each component that has monitoring enabled. JNGINX Controller v3.18.2 Resolved Issues NGINX Controller works with the following NGINX Plus versions: Fixes a rare timeout issue that affected some customers.NGINX Controller Technical Specifications Guide.For related installation documentation, refer to the following publications:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |