errordeveloper commented 8 years ago

For Kubernetes, having node labels and kubelet version in host details panel would probably be more relevant then kernel version that we display at the very top right now. Other fields from kubectl describe nodes would probably be quite useful also.

Here are my highlights (note: node name is not always the hostname, e.g. in EC2 it's the instance ID):

Name:           gke-kubeadm-continuous-integ-default-pool-a00db3b7-vrnn
Labels:         beta.kubernetes.io/arch=amd64
            beta.kubernetes.io/instance-type=n1-standard-4
            beta.kubernetes.io/os=linux
            cloud.google.com/gke-local-ssd=true
            cloud.google.com/gke-nodepool=default-pool
            failure-domain.beta.kubernetes.io/region=europe-west1
            failure-domain.beta.kubernetes.io/zone=europe-west1-d
            kubernetes.io/hostname=gke-kubeadm-continuous-integ-default-pool-a00db3b7-vrnn
Taints:         <none>
CreationTimestamp:  Mon, 10 Oct 2016 17:45:55 +0100
Phase:          
Conditions: (some kind of compact view of conditions would be great)
  Type          Status  LastHeartbeatTime           LastTransitionTime          Reason              Message
  ----          ------  -----------------           ------------------          ------              -------
  NetworkUnavailable    False   Mon, 10 Oct 2016 17:49:34 +0100     Mon, 10 Oct 2016 17:49:34 +0100     RouteCreated            RouteController created a route
  OutOfDisk         False   Mon, 10 Oct 2016 17:49:33 +0100     Mon, 10 Oct 2016 17:45:55 +0100     KubeletHasSufficientDisk    kubelet has sufficient disk space available
  MemoryPressure    False   Mon, 10 Oct 2016 17:49:33 +0100     Mon, 10 Oct 2016 17:45:55 +0100     KubeletHasSufficientMemory  kubelet has sufficient memory available
  DiskPressure      False   Mon, 10 Oct 2016 17:49:33 +0100     Mon, 10 Oct 2016 17:45:55 +0100     KubeletHasNoDiskPressure    kubelet has no disk pressure
  Ready         True    Mon, 10 Oct 2016 17:49:33 +0100     Mon, 10 Oct 2016 17:46:32 +0100     KubeletReady            kubelet is posting ready status. WARNING: CPU hardcapping unsupported
Addresses:      10.132.0.2,146.148.7.133
Capacity: (aslo compact view to be considered)
 alpha.kubernetes.io/nvidia-gpu:    0
 cpu:                   4
 memory:                15437428Ki
 pods:                  110
Allocatable: (aslo compact view to be considered)
 alpha.kubernetes.io/nvidia-gpu:    0
 cpu:                   4
 memory:                15437428Ki
 pods:                  110
System Info:
 Machine ID:            
 System UUID:           E2544721-AEB3-F1B0-AB7F-6531412ECD72
 Boot ID:           cd7fa68f-dd95-41b9-9a54-8ef48c332304
 Kernel Version:        3.16.0-4-amd64
 OS Image:          Debian GNU/Linux 7 (wheezy)
 Operating System:      linux
 Architecture:          amd64
 Container Runtime Version: docker://1.11.2
 Kubelet Version:       v1.4.0
 Kube-Proxy Version:        v1.4.0
PodCIDR:            10.0.0.0/24
ExternalID:         6488236495975381948
Non-terminated Pods:        (well, we have these in pods view already)
Allocated resources: (I think this is pretty important)
  (Total limits may be over 100 percent, i.e., overcommitted.
  CPU Requests  CPU Limits  Memory Requests Memory Limits
  ------------  ----------  --------------- -------------
  848m (21%)    298m (7%)   864656Ki (5%)   803216Ki (5%)
Events: (would be really awesome, but require a new kind of view)

For Docker, having some of the field from docker info would be quite useful also.

Here is a subset that I find important, but obviously we don't have to have all of these:

Server Version: 1.12.1
Storage Driver: aufs
Logging Driver: json-file
Plugins:
 Volume: local
 Network: host null bridge overlay
Swarm: active
 NodeID: atsu6n6n206mpw3kvvhziuf5k
 Is Manager: true
 ClusterID: bfcdqqfb6icr5qyzpk35idae9
 Managers: 1
 Nodes: 3
Runtimes: runc
Default Runtime: runc
Security Options: seccomp
Registry: https://index.docker.io/v1/
Labels:
 provider=vmwarefusion

rade commented 8 years ago

Is this a dup of #1143?

rade commented 7 years ago

@errordeveloper ping

rade commented 7 years ago

@errordeveloper @2opremio ping

2opremio commented 7 years ago

I would say it is, but I would leave it up for @errordeveloper since he reported it

rade commented 7 years ago

@errordeveloper ping again

bboreham commented 7 years ago

1143 is for pods and this one is for nodes.

errordeveloper commented 7 years ago

As @bboreham said.

bboreham commented 6 years ago

Annotations may also be of interest

ahmeed-dhon commented 4 years ago

it will be great to include pod count/max pod capacity in node detail panel too.

weaveworks / scope

k8s: host (node) details panel improvements #1914

1143 is for pods and this one is for nodes.