Skip to content
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

node-exporter pending status #8646

Closed
skyguard1 opened this issue Jul 16, 2020 · 3 comments
Closed

node-exporter pending status #8646

skyguard1 opened this issue Jul 16, 2020 · 3 comments
Labels
kind/question Further information is requested lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@skyguard1
Copy link

skyguard1 commented Jul 16, 2020

Hello, I deployed the metrics component according to the official documentation of knative(https://knative.dev/docs/serving/installing-logging-metrics-traces/), but I found that node-exporter has been in the pending state, I have not changed the configuration, so it is not clear why this problem occurs.

image

image

os
Linux tv1-dsf-perftest-01 4.11.1-1.el7.elrepo.x86_64 #1 SMP Sun May 14 11:54:29 EDT 2017 x86_64 x86_64 x86_64 GNU/Linux
kubernetes
v1.18.2
knative
v0.15.0

Hope to get your answer, thank you.

@skyguard1 skyguard1 added the kind/question Further information is requested label Jul 16, 2020
@skyguard1 skyguard1 reopened this Jul 24, 2020
@ZhiminXiang
Copy link

ZhiminXiang commented Aug 24, 2020

I noticed the warning nodes did not have free ports for the requested pod ports which seems like a k8s issue, not Knative one.

Could you please print out the result of kubectl describe pod <node-exporter-pod> and see if there is any detailed information about port collision?

@skyguard1
Copy link
Author

I noticed the warning nodes did not have free ports for the requested pod ports which seems like a k8s issue, not Knative one.

Could you please print out the result of kubectl describe pod <node-exporter-pod> and see if there is any detailed information about port collision?

Yes, i have solved this problem, thank

@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/question Further information is requested lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

2 participants