New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to start kube-proxy with --metrics-bind-address flags #68669

Open
Chenditang opened this Issue Sep 14, 2018 · 1 comment

Comments

Projects
None yet
3 participants
@Chenditang

Chenditang commented Sep 14, 2018

Is this a BUG REPORT or FEATURE REQUEST?:

/kind bug

What happened:

Start kube-proxy with "--metrics-bind-address=0.0.0.0:10249" return:
Error: invalid argument "0.0.0.0:10249" for "--metrics-bind-address" flag: "0.0.0.0:10249" is not a valid IP address
and with "--metrics-bind-address=0.0.0.0" return:
server.go:358] failed validate: KubeProxyConfiguration.MetricsBindAddress: Invalid value: "0.0.0.0": must be IP:port

What you expected to happen:

The default metrics-bind-address is "127.0.0.1:10249", I expected to change it with "--metrics-bind-address=0.0.0.0:10249"

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • Kubernetes version (use kubectl version):
  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release):
  • Kernel (e.g. uname -a):
  • Install tools:
  • Others:

Chenditang added a commit to Chenditang/kubernetes that referenced this issue Sep 14, 2018

**What this PR does / why we need it**:
Parsing "--metrics-bind-address" should use IPPortVar.

**Which issue(s) this PR fixes** *(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged)*:

Fixes #68669

**Special notes for your reviewer**:

**Release note**:
```
NONE
```

Chenditang added a commit to Chenditang/kubernetes that referenced this issue Sep 14, 2018

Parsing "--metrics-bind-address" should use IPPortVar.
**What this PR does / why we need it**:
Parsing "--metrics-bind-address" should use IPPortVar.

**Which issue(s) this PR fixes** *(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged)*:

Fixes #68669

**Special notes for your reviewer**:

**Release note**:
```
NONE
```

Signed-off-by: chendt.fnst <chendt.fnst@cn.fujitsu.com>

@Chenditang Chenditang referenced a pull request that will close this issue Sep 14, 2018

Open

Parsing "--metrics-bind-address" should use IPPortVar. #68670

@shubheksha

This comment has been minimized.

Show comment
Hide comment
@shubheksha

shubheksha Sep 14, 2018

Contributor

/sig network

Contributor

shubheksha commented Sep 14, 2018

/sig network

@k8s-ci-robot k8s-ci-robot added sig/network and removed needs-sig labels Sep 14, 2018

Chenditang added a commit to Chenditang/kubernetes that referenced this issue Sep 14, 2018

Parsing "--metrics-bind-address" should use IPPortVar.
**What this PR does / why we need it**:
Parsing "--metrics-bind-address" should use IPPortVar.

**Which issue(s) this PR fixes** *(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged)*:

Fixes #68669

**Special notes for your reviewer**:

**Release note**:
```
NONE
```

Signed-off-by: chendt.fnst <chendt.fnst@cn.fujitsu.com>

Chenditang added a commit to Chenditang/kubernetes that referenced this issue Sep 14, 2018

Parsing "--metrics-bind-address" should use IPPortVar.
**What this PR does / why we need it**:
Parsing "--metrics-bind-address" should use IPPortVar.

**Which issue(s) this PR fixes** *(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged)*:

Fixes #68669

**Special notes for your reviewer**:

**Release note**:
```
NONE
```

Signed-off-by: chendt.fnst <chendt.fnst@cn.fujitsu.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment