-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
no metrics known for pod #1149
Comments
Duplicate of #1067 |
I also encountered the same problem. |
Anyone knows if there's any progress in finding the cause? or maybe a workaround? |
I just found out that the issue happens (to me at least) only when running in docker mode. Otherwise it works. The problem is, that I must use Docker mode... :( |
dot you fix this problem? |
did you fix the problem? |
For those looking through this may help: kubernetes-sigs/metrics-server#349 |
Finnally I solved this problem with new version 1.18_k3s.
NodeHosts must be configued as After modifying the above two points, the values of metrics can be displayed correctly
But this modification method does not work on version 1.17 and 0.09. |
k3s has a built-in controller that manages the NodeHosts ConfigMap entries for you. It will add an entry for each cluster member. What did you change? |
( I'm sorry, my English is not good ) I have a private docker-registry service in k8s for images downloads service.
I used this configmap, deployment and service merge into a coredns yaml file I wrote a bootstrap script like this for change ip and install customized allinone k3s
So I disabled coredns deploy and put my revised version coredns deploy. |
Version:
k3s version v1.0.0 (18bd921)
Describe the bug
pods metrics shows nothing.
metrics-server pod's logs showed:
To Reproduce
Expected behavior
Display pods' cpu and memory values.
Like:
Actual behavior
kubectl top pods -A
showed nothingAdditional context
environment
I started a virtualbox with vagrant
And start virtual machine with
vagrant up
Network route
Pods status
The text was updated successfully, but these errors were encountered: