Repository navigation
v2.19.0 — Admin overview, a log viewer that keeps up, WebSocket tickets
What's new
Admin → Overview (admins only; admins land here after sign-in, g o)
- The selected cluster at a glance: pods running, pods needing attention (red / amber), restarts in 24 h, ready Deployments, CPU and memory as % of allocatable, each with a 24 h trend.
- Cluster usage over 24 h against allocatable (Prometheus when configured, else the in-memory samples), pods needing attention (click opens the pod's drawer), workloads restarting most with their usual exit code (
5× 137 (OOMKilled)), restarts per hour, busiest namespaces with pods near their limits, Warning events of the last 15 minutes, node strip. - Opens in well under a second on a 700-pod cluster: the page doesn't wait for Prometheus, whose 24 h history is kept 5 minutes and refreshed in the background.
- Live Events opens right on the page, for the whole cluster, on Warnings.
Log viewer (pods, Deployments, Jobs)
- Status (following, reconnecting, ended, why) is shown apart from the log; a kubelet message such as "unable to retrieve container logs" no longer appears as a log line.
- Container picker, init containers included; a pod whose sidecar comes first (e.g.
[filebeat, app]) opens on the main container. - Live | Before last restart.
- A dropped connection (network, proxy timeout) or a container restart resumes from the last line's timestamp without losing or repeating lines; a restarted container is followed into its new instance.
- Keeps the last 10,000 lines with a virtual list; find (⌘F / Ctrl+F), pause, wrap, copy, download.
Shell: for a pod with several containers, a small menu under the Shell button: the main container first (Enter), containers that aren't running greyed out.
Live Events
- Now filtered by the user's grants: a user sees an object's changes and Kubernetes Events about it only where they may list that kind; node and other cluster-scoped events are for admins. Before, any signed-in user could follow any namespace.
- Repeats of a recurring event (a failing probe) are shown, not only its first occurrence.
- Opened from a button in the header (or
e) instead of the floating button that covered row actions.
Upgrading
- WebSocket clients: browsers need nothing. A script that opens
/ws/…?token=<JWT>must firstPOST /api/ws-ticket{"path": "/ws/…"}and use?ticket=<t>(single use, 30 s, that path only). The JWT no longer appears in any URL. - Re-apply
deploy/rbac.yaml(orrbac-readonly.yaml): new rulesnodesandmetrics.k8s.ionodesget / list, used by the Overview (node count, % of allocatable, node strip). Without them the Overview shows absolute CPU / memory and no node strip; nothing breaks. - Log streams per user: 10 at once, then one per second (was 2, then one every 5 s).
- New audit verb
view_overview(cluster.view_overview, ECSevent.type: access).
Image
ghcr.io/vurulkan/kubernetes-openconsole:2.19.0 (= :latest, same digest; amd64 + arm64), with signed provenance and SBOM:
gh attestation verify oci://ghcr.io/vurulkan/kubernetes-openconsole:2.19.0 --repo vurulkan/kubernetes-openconsole
🤖 Generated with Claude Code