-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Metrics are just available for nodes and kube-system namespace #1018
Comments
Hi @Al4DIN, you can try to use
to get raw data. |
You can check if it exists #976 (comment) mentioned in the case. |
Thank you for your reponse, here's my command result, and since I'm using minikube on Windows
We can clearly see that for pods I'm not geting any ressource. I've also tried many solution on stackoverflow and github issues but still can't figure out the cause. |
Yeah, Your analysis is correct. |
/kind support |
Okay, thank you. |
Actually It was relate to Minikube Environnement where you need to add an argument while launching your minikube |
Nice, looks like something we could document as a known issue. |
The problem is that an old issue that It's still not pushed in the release version of Minikube. |
I mean yes, it would be ideal for owners of K8s distribution to fix/document their distro. From Metrics Server side we only can ask Minikube nicely and document it ourselves. |
Yeah, we should document it as a known issue and I'll update the known issue. |
Is there an equivalent setting for docker desktop? Having the same issue. |
How to solve this problem |
Hello @serathius , @yangjunmyfm192085
I've the same issue on kubectl
v1.22.5
client &v1.22.1
for the server, I can only retrieve metrics from node and some pods from mykube-system
since I installed my metrics-server on this namespace but can't get other pods metrics.I'm using
k8s.gcr.io/metrics-server/metrics-server:v0.4.1
This is the result of my
kubectl get --raw /api/v1/nodes/minikube2/proxy/metrics/resource
Originally posted by @Al4DIN in #976 (comment)
The text was updated successfully, but these errors were encountered: