allow custom nginx_status config for nginx_status endpoint #2040
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
Currently, the nginx_status endpoint is only accessible from within the pod, making it difficult to monitor externally. With this change, users can supply custom nginx_status directives (e.g., allow/deny rules, custom locations) to expose and manage the status endpoint as needed. As per source
ISSUE TYPE
ADDITIONAL INFORMATION
This example of how to allow any ip but can be restricted to k8s CIDR