Dashboard: Not showing Allocated Resources for Node

[naisanza]

Issue details

Pod Allocated resources are not updated in kubectl describe nodes, or in the Dashboard UI

Environment

Dashboard version: gcr.io/google_containers/kubernetes-dashboard-amd64:v1.5.1
Kubernetes Client Version: version.Info{Major:"1", Minor:"5", GitVersion:"v1.5.1", GitCommit:"82450d03cb057bab0950214ef122b67c83fb11df", GitTreeState:"clean", BuildDate:"2016-12-14T00:57:05Z", GoVersion:"go1.7.4", Compiler:"gc", Platform:"linux/amd64"}
Kubernetes Server Version: version.Info{Major:"1", Minor:"5", GitVersion:"v1.5.1", GitCommit:"82450d03cb057bab0950214ef122b67c83fb11df", GitTreeState:"clean", BuildDate:"2016-12-14T00:52:01Z", GoVersion:"go1.7.4", Compiler:"gc", Platform:"linux/amd64"}
Operating system: Linux k8s-master01 4.8.0-22-generic #24-Ubuntu SMP Sat Oct 8 09:15:00 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Node.js version:
Go version: 1.7.4

Steps to reproduce

Only the Pods count and % are displayed. None of the other resource requests are updated.

Comments

kubectl describe nodes output:

Name:                   kubernetes01-node01
Role:
Labels:                 beta.kubernetes.io/arch=amd64
                        beta.kubernetes.io/os=linux
                        kubernetes.io/hostname=kubernetes01-node01
Taints:                 <none>
CreationTimestamp:      Fri, 03 Feb 2017 02:33:05 -0500
Phase:
Conditions:
  Type                  Status  LastHeartbeatTime                       LastTransitionTime                      Reason                          Message
  ----                  ------  -----------------                       ------------------                      ------                          -------
  OutOfDisk             False   Thu, 09 Feb 2017 06:41:21 -0500         Tue, 07 Feb 2017 20:29:26 -0500         KubeletHasSufficientDisk        kubelet has sufficient disk space available
  MemoryPressure        False   Thu, 09 Feb 2017 06:41:21 -0500         Fri, 03 Feb 2017 02:33:05 -0500         KubeletHasSufficientMemory      kubelet has sufficient memory available
  DiskPressure          False   Thu, 09 Feb 2017 06:41:21 -0500         Fri, 03 Feb 2017 02:33:05 -0500         KubeletHasNoDiskPressure        kubelet has no disk pressure
  Ready                 True    Thu, 09 Feb 2017 06:41:21 -0500         Tue, 07 Feb 2017 20:29:26 -0500         KubeletReady                    kubelet is posting ready status. AppArmor enabled
Addresses:              10.100.0.135,10.100.0.135,kubernetes01-node01
Capacity:
 alpha.kubernetes.io/nvidia-gpu:        0
 cpu:                                   12
 memory:                                6971200Ki
 pods:                                  110
Allocatable:
 alpha.kubernetes.io/nvidia-gpu:        0
 cpu:                                   12
 memory:                                6971200Ki
 pods:                                  110
System Info:
 Machine ID:                    e447bf7baee94e89b151ca79130aa5e8
 System UUID:                   CFC7FB7C-B37E-44EB-8BEF-4A6FE85ED429
 Boot ID:                       89dd76a5-2221-42e1-954e-2dc0b091f67b
 Kernel Version:                4.8.0-37-generic
 OS Image:                      Ubuntu 16.10
 Operating System:              linux
 Architecture:                  amd64
 Container Runtime Version:     docker://1.12.3
 Kubelet Version:               v1.5.2
 Kube-Proxy Version:            v1.5.2
PodCIDR:                        10.244.1.0/24
ExternalID:                     kubernetes01-node01
Non-terminated Pods:            (6 in total)
  Namespace                     Name                                    CPU Requests    CPU Limits      Memory Requests Memory Limits
  ---------                     ----                                    ------------    ----------      --------------- -------------
  default                       neo4j-01-513924406-xp756                0 (0%)          0 (0%)          0 (0%)          0 (0%)
  kube-system                   canal-node-jx9n5                        0 (0%)          0 (0%)          0 (0%)          0 (0%)
  kube-system                   kube-proxy-g4868                        0 (0%)          0 (0%)          0 (0%)          0 (0%)
  portal                        apache-portal-4153664915-nxdf6          0 (0%)          0 (0%)          0 (0%)          0 (0%)
  portal                        heketi-pv-1670767574-nzp0f              0 (0%)          0 (0%)          0 (0%)          0 (0%)
  portal                        neo4j-portal-311092169-sxdr6            0 (0%)          0 (0%)          0 (0%)          0 (0%)
Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.
  CPU Requests  CPU Limits      Memory Requests Memory Limits
  ------------  ----------      --------------- -------------
  0 (0%)        0 (0%)          0 (0%)          0 (0%)
No events.

[olekzabl]

Can you reproduce this and/or provide more details on how to reach such state?
Please also note that kubectl is a separate project, managed here. If both apps show the same, it suggests that this might be the desired behavior. (See e.g. this thread).

[naisanza]

@olekzabl I have created this in two separate environments, but with identical setups.

Apart from hardware, the setups are as follows:

1. Proxmox 4.4 hypervisor
2. Kubernetes master installed in Ubuntu 16.10 running in kvm
3. Kubernetes node installed in Ubuntu 16.10 running in kvm

Kubernetes was installed following this guide: https://kubernetes.io/docs/getting-started-guides/kubeadm/

In both environment, neither dashboards show resource usage of the node, and kubectl doesn't show resource usage either

https://github.com/kubernetes/kubernetes/pull/12005 seems to have been merged in 2015, and looks to be an older version of kubernetes/pkg/kubectl/describe.go, which is very different from the master now

[olekzabl]

I can see this working in Kubernetes 1.5.2 & Dashboard 1.5.1, as here:

"kubectl describe node" also shows non-zero values for me.

Do you observe the error for all your nodes, or do you take some more specific steps to produce it? If yes, what are these steps?

[olekzabl]

I consulted this with @bryk. We both suspect that having the same output from the Dashboard and kubectl signalizes that the problem lives at some deeper layer. @bryk suggests that most likely this can be an issue with your installation of Kubernetes, and that you may want to contact the kubeadm team.

[naisanza]

@olekzabl I just rebuilt them from scratch

I'm running this installer here: https://github.com/TheShellLand/krazy88s/blob/master/scripts/kube-install.sh

[maciaszczykm]

Closing as it's cluster-related issue, not Dashboard's.

[ammyverm007]

I am also facing this issue
please tell me how to resolve this

Pod Allocated resources are not updated in kubectl describe nodes, or in the Dashboard UI