We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently describe prints the below details when querying a node. But the real-time utilization is missing in that picture.
Non-terminated Pods: (12 in total) Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits AGE --------- ---- ------------ ---------- --------------- ------------- --- kube-system coredns-6955765f44-gcntl 100m (5%) 0 (0%) 70Mi (3%) 170Mi (9%) 3h56m kube-system coredns-6955765f44-knpzb 100m (5%) 0 (0%) 70Mi (3%) 170Mi (9%) 18d kube-system etcd-minikube 0 (0%) 0 (0%) 0 (0%) 0 (0%) 18d kube-system kube-apiserver-minikube 250m (12%) 0 (0%) 0 (0%) 0 (0%) 18d kube-system kube-controller-manager-minikube 200m (10%) 0 (0%) 0 (0%) 0 (0%) 18d kube-system kube-proxy-8n656 0 (0%) 0 (0%) 0 (0%) 0 (0%) 18d kube-system kube-scheduler-minikube 100m (5%) 0 (0%) 0 (0%) 0 (0%) 18d kube-system metrics-server-6754dbc9df-frtfb 0 (0%) 0 (0%) 0 (0%) 0 (0%) 13d kube-system storage-provisioner 0 (0%) 0 (0%) 0 (0%) 0 (0%) 18d test1 web-0 0 (0%) 0 (0%) 0 (0%) 0 (0%) 12d test1 web-1 0 (0%) 0 (0%) 0 (0%) 0 (0%) 12d test1 web-2 0 (0%) 0 (0%) 0 (0%) 0 (0%) 12d
But operators would like to find the answer for "Which pod is 'actually' using most resources?"
(This may be a bit stretch goal for this plugin)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently describe prints the below details when querying a node. But the real-time utilization is missing in that picture.
But operators would like to find the answer for "Which pod is 'actually' using most resources?"
(This may be a bit stretch goal for this plugin)
The text was updated successfully, but these errors were encountered: