The Kubernetes integration v1.21.0 brings several changes related to node allocatable resources.
Changes to the cluster explorer
We added support for allocatable resources to the Kubernetes cluster explorer:
The cluster explorer entity list now calculates CPU usage by summing the
K8sNodeSampleinstead of using
SystemSample. Similarly, memory usage is now calculated by summing
memoryTotalBytes. Pods' columns now refer to running pods vs. allocatable pods.
In addition to resource consumption, the node's tooltip in the cluster explorer now shows the amount of allocatable pods used by the node.
The node card, which appears when clicking a node in cluster explorer, now shows resource consumption (CPU, memory, and storage) against the allocatable resources.
- CPU usage aggregates
- Memory usage aggregates
- Storage usage relies on
- CPU usage aggregates
A new pods widget has been added to the node card that shows the amount of pods used against the total allocatable pods of the node.
If you run the unprivileged version of the Kubernetes integration, you can now see the node metrics. Previously, this was only possible with the privileged version.
The cluster explorer dashboard, which appears when clicking Kubernetes dashboard, has been updated to account for resource consumption against allocatable resources.
- CPU widgets displays
K8sNodeSample. As for Memory usage, it now shows
- Disk widgets use
- A new pods widget has been added that shows the amount of pods used against the total allocatable pods of the cluster.
Changes to Kubernetes metrics
- Node allocatable resources and capacity are retrieved from the API server and added to the
- The Kubernetes server version is now retrieved from the API server and cached with the
APIServerCacheK8SVersionTTL config option. The version is added to
clusterK8sVersion, and to the inventory.
- Add support for static pods status for Kubernetes server versions 1.15 or newer.
- In older versions of Kubernetes, the kubeletes wouldn’t sync the status of the static pods with the API server and would always return a
Pendingstatus. This behavior was fixed in v1.15 of Kubernetes. Our integration now detects what version of Kubernetes the cluster is running and, if it’s 1.15 or newer, it adds the status of the static pods in