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
3.0 wont work - reststorage.go:101] unable to fetch node metrics for node "k8sdev01": no metrics known for node "k8sdev01" #143
Comments
metrics-server doesn't know how to trust the serving certificates on your kubelets. First, double check what happens with the |
Error: unknown flag: --insecure-kubelet tried with --kubelet-insecure-tls, and i have the same error
|
on version 0.2.1 works , even with the error
on version 0.2.1 i have the certificate but works
|
|
for the last message, something's wrong with your DNS setup (by default, metrics-server looks up node DNS names to connect to the kubelet, but this can be changed with one of the metrics-server flags) for the |
what is the parameter to change to ip ? is strange with version 0.2.1 works i have deploy all the files in deploy/1.8+/ |
tried --kubelet-preferred-address-types=ExternalIP but same problem |
did this:
tested on pod if can resolve the name
but i have the same error |
which error? The |
no, sorry
|
I am facing the same issue with metrics server. But metrics-server is looking by hostname only: |
I also encountered this problem. When the name of the node is the host name, metrics-server cannot resolve the host.
|
same problem |
If you want to prioritize certain address types, please use the |
As for the certificate errors, it's probably due to a different kubelet CA from the main cluster CA. We've got an issue open to add a flag for supporting a setup where trusting the main cluster CA doesn't automatically trust the kubelet CA. |
Having exactly the situation as @d-peng describes. edit nvm I recreated the cluster. |
I solved this by adding node ip to coredns: apiVersion: v1 |
works for me. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Same problem here. Pod log error message:
|
I have the same issue. However, I'm able to get metrics for 1 node. I can confirm that the only node reporting metrics has the metrics-server running on it.
From logs: |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
fix "no metrics known for node" error refs kubernetes-sigs/metrics-server#143 Signed-off-by: mritd <mritd@linux.com>
updated v0.2.1 to v0.3.0.
on 0.2.1 was working
on v0.3.0 gives this error:
The text was updated successfully, but these errors were encountered: