Skip to content

Conversation

Alja9
Copy link
Contributor

@Alja9 Alja9 commented Aug 8, 2025

What this PR does / why we need it

Is it possible allow users to set custom port on $servicePort when using kube rbac proxy instead of hardcode it.

Which issue this PR fixes

When the kube-state-metrics using hostNetwork: true , I encounter issue like this :

E0808 01:38:06.824987       1 wrapper.go:40] "Failed to run kube-state-metrics" err="run server group error: listen tcp 127.0.0.1:9090: bind: address already in use"

(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

  • fixes #

Special notes for your reviewer

Checklist

  • DCO signed
  • Chart Version bumped
  • Title of the PR starts with chart name (e.g. [prometheus-couchdb-exporter])

@Alja9 Alja9 requested review from dotdc, mrueg and tariq1890 as code owners August 8, 2025 08:36
@Alja9 Alja9 changed the title Service port [kube-state-metrics] Allow to configure upstream port for KubeRBACProxy Aug 8, 2025
@Alja9
Copy link
Contributor Author

Alja9 commented Aug 8, 2025

if it is possible for this PR to be approved, I will make one for the telemetryPort in a different PR too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant