You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In some IC deployments the hard-coded ports for the NGINX+ API conflict with other services already running on those containers, and the NGINX open source stub_status isn't exposed at all.
We'll add 2 CLI options:
nginx-status-port the port to listen on
nginx-status which enables/disables the api or stub_status. If disabled, we'll listen on a unix socket instead, so the IC can still use api features.
The stub_status location will be added in a separate server directive in the nginx config, similar to the existing NGINX Plus API location.
Is above changes are present in this docker image version nginx/nginx-ingress:1.3.0.
I am not able to use the above two options. if provided as arguments, ic is failing to start by printing the help.
but ideally it should export the metrics on port 8080. even that configurations is not present and not working.
In some IC deployments the hard-coded ports for the NGINX+ API conflict with other services already running on those containers, and the NGINX open source stub_status isn't exposed at all.
We'll add 2 CLI options:
nginx-status-port
the port to listen onnginx-status
which enables/disables the api or stub_status. If disabled, we'll listen on a unix socket instead, so the IC can still use api features.The stub_status location will be added in a separate server directive in the nginx config, similar to the existing NGINX Plus API location.
We'll need to extend the NGINX Plus go sdk to handle linux sockets.
The text was updated successfully, but these errors were encountered: