nginx_status block configuration

[Tidslmao]

At the moment the nginx_status location configuration is being automatically enabled when deploying ingress-nginx via helm chart.
This is not an issue in itself but when using ssl-passthrough for mtls communication, we are able to access the block from outside.
I would like to be able to change that configuration directly from the helm chart instead of from the container. Even just an extra arg for disabling it will suffice for now imo, until this can be addressed fully.
Thanks for taking this into account! Best wishes!

Im not aware of any.

No

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[longwuyuan]

/retitle nginx_status block configuration

[longwuyuan]

I wanted to comment that your issue description is very terse.

I think its acceptable to write succint terse issue descriptions in closed groups or chat forums. But here its required that the questions that are asked in the new bug report template be answered or detailed data be provided for feature requests, as output of kubectl commands, curl and so on. It helps a reader to actually get a action item.

For example your issue description requires another person to guess and speculate on environment and other aspects and do a lot of preliminary triaging, which may or may not even be correct.

Please edit the description of the feature and add your data from tests on a kind or minikube cluster and include the kubectl command outputs for all resources and states with logs and curl -v etc etc.. It will help a lot