Skip to content

2.20.0: Nodes screen

Choose a tag to compare

@vurulkan vurulkan released this 26 Oct 19:14
· 8 commits to main since this release

What's new

Nodes (admins only, read only; left rail under Overview, g n, command palette)

  • Every node of the selected cluster: status (Ready / NotReady / MemoryPressure / DiskPressure / PIDPressure, cordoned shown apart), roles, kubelet version, OS / architecture, age, pods against capacity.
  • CPU and memory used as % of allocatable (amber from 70 %, red from 90 %), with requests and limits as % of allocatable, the way the scheduler counts them (init containers, sidecars, pod overhead).
  • Sort by any column (CPU / memory % included), search by name, role or label (key=value, key= for any value), j / k / Enter. Refreshes every 15 s on its own.
  • Live Events in the header, for the whole cluster, on Warnings.

Node drawer (click a node, or open /nodes?node=<name>)

  • Summary: OS image, kernel, container runtime, internal / external IP, scheduling (cordoned or not).
  • Capacity, allocatable, requests, limits and usage for CPU, memory, pods and ephemeral storage.
  • Usage history over 1 h / 6 h / 24 h against allocatable (7 d with Prometheus): the node's containers from Prometheus by the node or instance label, else its pods summed; without Prometheus, the in-memory samples.
  • Top 10 pods by CPU or memory, and every pod on the node (all, or only those needing attention); a pod opens in its drawer on the Dashboard.
  • Conditions, taints, labels, annotations and events (Warnings first).

Ways in: a node in the Overview's node strip opens its drawer, "All nodes" opens the list; in a pod's drawer the node name is a link (admins).

Measured on a 4-node, ~700-pod AKS cluster: the list answers in under 3 ms from its 15 s cache (about 130 ms when it is rebuilt), a node's detail in under 10 ms.

Upgrading

  1. Re-apply deploy/rbac.yaml (or rbac-readonly.yaml): nodes now also has watch, so nodes stay in the informer cache. Without it the Nodes screen still works; nodes are listed from the API server on each request instead (cached 15 s).
  2. Admin only: there is no new permission to grant. A non-admin gets 403 and an audit event with outcome denied.
  3. New audit actions node.list and node.get (existing verbs, ECS event.type: access); the page's own refreshes are not audited.
  4. New endpoints: GET /api/admin/nodes, GET /api/admin/nodes/{name}, GET /api/admin/nodes/{name}/metrics/history?range=.

Image

ghcr.io/vurulkan/kubernetes-openconsole:2.20.0 (= :latest, same digest; amd64 + arm64), with signed provenance and SBOM:
gh attestation verify oci://ghcr.io/vurulkan/kubernetes-openconsole:2.20.0 --repo vurulkan/kubernetes-openconsole

🤖 Generated with Claude Code