After migrating to the F5 NGINX Ingress Controller following the instructions outlined in the Broadcom TechDocs users may experience a "Bad Request" error when attempting to access the Restmon Swagger UI endpoint:
https://restmon.###/restmon/api/swagger-ui/index.html
DXO2 on-prem 25.1, 26.1.
DE666310 - issue occurs because the existing Helm chart lacks the specific ingress annotations required by the F5 NGINX Ingress Controller to properly route and handle the Restmon traffic.
Download attached fix (dx-restmon-nginx-f5-fix.zip) and perform the following:
1. Uninstall the existing dx-restmon using helm uninstall command.
2. Copy the attached ingress.yaml into dx-restmon/templates folder.
3. Add the following annotations under ingress for NGINX F5.
annotations: # F5 NGINX-specific annotations (nginx.org/*) nginx.org/proxy-connect-timeout: "30s" nginx.org/proxy-read-timeout: "60s" nginx.org/proxy-send-timeout: "60s" nginx.org/proxy-buffering: "true" nginx.org/proxy-buffer-size: "8k" nginx.org/proxy-buffers: "4 8k" nginx.org/server-snippets: | proxy_ssl_verify off; nginx.org/location-snippets: | proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; nginx.org/redirect-to-https: "true"
Attached the sample values.yaml for your reference.
5. Install dx-restmon using helm install command.helm install <release-name> ./dx-restmon -f values.yaml -n <namespace>
6. Allow a few minutes for the pods to initialize, then navigate to the Restmon Swagger UI (https://restmon.###/restmon/api/swagger-ui/index.html) to confirm the "Bad Request" error is resolved.