Skip to content

Conversation

@jichenjc
Copy link
Contributor

What this PR does / why we need it:

add --metrics-bind-addr=127.0.0.1:8080 so that capo can report metrics info
this previously exist and removed somehow..

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 #

Special notes for your reviewer:

  1. Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:


@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jan 22, 2021
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jichenjc

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jan 22, 2021
@theopenlab-ci
Copy link

theopenlab-ci bot commented Jan 22, 2021

Build failed.

@hidekazuna
Copy link
Contributor

Default is 127.0.0.1:10249. Do we have any reason --metrics-bind-addr should not to be default?

@jichenjc
Copy link
Contributor Author

  • containerPort: 8080
    name: metrics
    protocol: TCP

is in same file ...previously it's also 8080
I am ok to change to 10249 but seems capi also default to 8080

@jichenjc
Copy link
Contributor Author

recheck

@hidekazuna
Copy link
Contributor

  • containerPort: 8080
    name: metrics
    protocol: TCP

is in same file ...previously it's also 8080
I am ok to change to 10249 but seems capi also default to 8080

I understand. I wondered after checking capa source which is not have --metrics-bind-addr. So we have to delete containerPort to be default.

@jichenjc
Copy link
Contributor Author

  • containerPort: 8080
    name: metrics
    protocol: TCP

is in same file ...previously it's also 8080
I am ok to change to 10249 but seems capi also default to 8080

I understand. I wondered after checking capa source which is not have --metrics-bind-addr. So we have to delete containerPort to be default.

Sorry, I mean https://github.com/kubernetes-sigs/cluster-api-provider-openstack/blob/master/config/manager/manager_auth_proxy_patch.yaml#L24

@hidekazuna
Copy link
Contributor

capi seems not to be 8080
https://github.com/kubernetes-sigs/cluster-api/blob/master/config/manager/manager.yaml

  • containerPort: 8080
    name: metrics
    protocol: TCP

is in same file ...previously it's also 8080
I am ok to change to 10249 but seems capi also default to 8080

I understand. I wondered after checking capa source which is not have --metrics-bind-addr. So we have to delete containerPort to be default.

Sorry, I mean https://github.com/kubernetes-sigs/cluster-api-provider-openstack/blob/master/config/manager/manager_auth_proxy_patch.yaml#L24

CAPI is also.
https://github.com/kubernetes-sigs/cluster-api/blob/master/config/manager/manager_auth_proxy_patch.yaml#L24

So,
Both CAPI and CAPO has --metrics-bind-addr in manager_auth_proxy_patch.yaml. That is fine.
Only CAPO has containerPort: 8080 in manager.yaml. This should to be fixed.

@hidekazuna
Copy link
Contributor

Thanks for you, I found another issue and raised #728 😃

@theopenlab-ci
Copy link

theopenlab-ci bot commented Jan 22, 2021

Build failed.

@jichenjc
Copy link
Contributor Author

recheck

@jichenjc
Copy link
Contributor Author

@hidekazuna So I think you are saying this good PR and only wait for CI? or any changes need to be made?

@theopenlab-ci
Copy link

theopenlab-ci bot commented Jan 22, 2021

Build failed.

@hidekazuna

This comment has been minimized.

@jichenjc
Copy link
Contributor Author

recheck

@theopenlab-ci
Copy link

theopenlab-ci bot commented Jan 25, 2021

Build failed.

@jichenjc
Copy link
Contributor Author

recheck

@theopenlab-ci
Copy link

theopenlab-ci bot commented Jan 25, 2021

Build failed.

@scruplelesswizard
Copy link
Contributor

recheck

@scruplelesswizard
Copy link
Contributor

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 27, 2021
@scruplelesswizard
Copy link
Contributor

Thanks for the patch @jichenjc

@scruplelesswizard scruplelesswizard changed the title Add metrics serive ip and addr Specify --metrics-bind-addr for CAPO manager Jan 27, 2021
@k8s-ci-robot k8s-ci-robot merged commit 8f51aa2 into kubernetes-sigs:master Jan 27, 2021
@hidekazuna
Copy link
Contributor

@jichenjc --metrics-bind-addr=127.0.0.1:8080 is added by patches:

We do not need this PR. Actually we can get the same result using kustomize build under config directory.

@jichenjc
Copy link
Contributor Author

@jichenjc --metrics-bind-addr=127.0.0.1:8080 is added by patches:

We do not need this PR. Actually we can get the same result using kustomize build under config directory.

are those for proxy and webhook? the PR is for the manager ..

@hidekazuna
Copy link
Contributor

Patches are for manager.

- name: manager
        args:
        - "--metrics-bind-addr=127.0.0.1:8080"
        - "--leader-elect"

hidekazuna added a commit to hidekazuna/cluster-api-provider-openstack that referenced this pull request Feb 3, 2021
…ics_service"

This reverts commit 8f51aa2, reversing
changes made to 0163b5e.
k8s-ci-robot added a commit that referenced this pull request Feb 3, 2021
pierreprinetti pushed a commit to shiftstack/cluster-api-provider-openstack that referenced this pull request Apr 22, 2024
…ics_service"

This reverts commit 8f51aa2, reversing
changes made to 0163b5e.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants