Skip to content
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

`kubectl top pod` does not show any utilization % #75350

Open
khteh opened this Issue Mar 14, 2019 · 4 comments

Comments

Projects
None yet
5 participants
@khteh
Copy link

khteh commented Mar 14, 2019

What happened:
kubectl top pod does not show any utilization %
What you expected to happen:
kubectl top pod shows utilization %
How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:
kubectl top node shows utilization % but not kubectl top pod
Environment:

  • Kubernetes version (use kubectl version): v1.13.4
  • Cloud provider or hardware configuration: AWS EKS
  • OS (e.g: cat /etc/os-release): Ubuntu 18.10
  • Kernel (e.g. uname -a): 4.18.0-16-generic
  • Install tools: kubectl
  • Others:

@khteh khteh added the kind/bug label Mar 14, 2019

@neolit123

This comment has been minimized.

Copy link
Member

neolit123 commented Mar 15, 2019

/remove-kind bug
/kind feature
/sig cli

@shiywang

This comment has been minimized.

Copy link
Member

shiywang commented Mar 19, 2019

I don't think it's a bug of cli

when you use kubectl top pods the Available v1.ResourceList from server seems missing.

(*metricsutil.ResourceMetricsInfo)(0xc0006c7980)({
 Name: (string) (len=37) "metrics-server-v0.2.1-fd596d746-gqjnx",
 Metrics: (v1.ResourceList) (len=2) {
  (v1.ResourceName) (len=3) cpu: (resource.Quantity) 1m,
  (v1.ResourceName) (len=6) memory: (resource.Quantity) 21096Ki
 },
 Available: (v1.ResourceList) {
 }
})
(v1.ResourceList) {
}

@DirectXMan12 @kubernetes/sig-cli-misc
/sig sig-autoscaling-bugs

@DirectXMan12

This comment has been minimized.

Copy link
Contributor

DirectXMan12 commented Mar 19, 2019

it's not an autoscaling or metrics bug -- I think this is purely in the SIG CLI realm -- that Available field doesn't come from the metrics API (plus, metrics is SIG Instrumentation)

@shiywang

This comment has been minimized.

Copy link
Member

shiywang commented Mar 20, 2019

okay, I'll take a look

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.