expose metrics-bind-address configuration for kube-proxy

[vivekgarg20]

1. Describe IN DETAIL the feature/behavior/change you would like to see.
We are trying to scrape kube-proxy metrics but unable to do same with KOPS built cluster.
We figured out it is because of default metrics bind address is 127.0.0.1.
As per K8S documentation it is possible to change default bind address to 0.0.0.0.
https://kubernetes.io/docs/reference/command-line-tools-reference/kube-proxy/

It seems KOPS does not expose this configuration.
2. Feel free to provide a design supporting your feature request.
It is straightforward as we need to expose metrics-bind-address configuration. I can submit a PR if required.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[vivekgarg20]

Thanks @gambol99

[demisx]

Can you guys please tell me how I can edit or create a new kops cluster with metrics-bind-address=0.0.0.0? Where do I set this? I tried passing the --metrics-bind-address=0.0.0.0 flag to kops create cluster, but it does not understand it. Thank you!

[ivnilv]

Can you guys please tell me how I can edit or create a new kops cluster with metrics-bind-address=0.0.0.0? Where do I set this? I tried passing the --metrics-bind-address=0.0.0.0 flag to kops create cluster, but it does not understand it. Thank you!

For those who still need it, I managed to change the metrics bind address from 127.0.0.1 to 0.0.0.0 by putting the following in my cluster spec:

...
  kubeProxy:
    metricsBindAddress: 0.0.0.0
...

Then, did a kops update cluster followed by a rolling-update and and finally Prometheus was able to scrape the kube-proxy metrics 🎉

[demisx]

@ivnilv Thank you! This worked.