-
Notifications
You must be signed in to change notification settings - Fork 83
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
Getting panic for metrics cadvisor
command
#34
Comments
It should work, but even if not, it shouldn't throw panic. To troubleshoot I have a number of questions.
Do you receive any results? Another question,
Does it work? |
I think you can't auth to kubelet from the local:
You should pass the necessary certs: (on remote host)
|
Thank you for providing that information. In your example, you wrote the command like that:
You didn't specify any certificates so the result should also be We will test this API again and update it here. |
Small update.
To restore:
In my case, on Ubuntu 22.04 LTS the command worked:
I received all the information. The question is if the problem is because of using it on macOs or your metrics\cadvisor data cause it. |
@Dentrax What CPU you have? Intel\M1\M2 ?
I want to know if it happens on M1 or M2. |
Hey, sorry missed your comment. @g3rzi
|
Can you try to build the code with |
It should be OK now. If after building darwin/arm64 it doesn't work, let us know. |
Thanks @g3rzi, are you going to cut a new version soon? It seems almost a year passed since last tag. |
Yes, published now version 1.12: |
Summary
Provide brief overview and context for the discovered bug.
Steps to Reproduce
curl -LO https://github.com/cyberark/kubeletctl/releases/download/v1.11/kubeletctl_darwin_amd64 && chmod a+x ./kubeletctl_darwin_amd64 && mv ./kubeletctl_darwin_amd64 /usr/local/bin/kubeletctl
kubeletctl -s 10.11.12.13 metrics cadvisor
Expected Results
It should work?
Actual Results
Throws panic.
Reproducible
Version/Tag number
1.11
K8s: v1.23.7
Environment setup
macOS
Additional Information
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: