kube-state-metrics: fix probes when RBAC proxy is enabled #6402
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.
What this PR does / why we need it
When installing the kube-state-metrics with RBAC proxy enabled, the pod never reaches a healthy state.
This is because the named ports are not created when rbac proxy is enabled. Additionally, having the host set to
127.0.0.1when rbac proxy is enabled breaks the health check because the check originates from Kubernetes (outside the container) and therefore the connection is refused.With this fix, the probes work as expected in all scenarios.
Special notes for your reviewer
Checklist
[prometheus-couchdb-exporter])