Skip to content

2.18.0: pod health and restart reasons, usage and Prometheus, workload drawers

Choose a tag to compare

@vurulkan vurulkan released this 26 Oct 13:23
· 11 commits to main since this release

What's new

Why did it restart?

  • Pod status as kubectl get pods prints it (CrashLoopBackOff, OOMKilled, ImagePullBackOff, Init:Error, Unschedulable …), red / amber / green / gray.
  • The restart count shows the last exit code on hover, e.g. 137 (OOMKilled), with a plain-language explanation.
  • Logs: Before the last restart reads the previous container instance (kubectl logs --previous), audited with previous: true.
  • Restart history kept for 30 days (RESTART_HISTORY_RETENTION_DAYS), also for pods that no longer exist; a crash loop is one row.

Detail drawers for pods, Deployments, StatefulSets and DaemonSets: containers, requests / limits, probes, last exit, rollout, the workload's pods, Deployment revisions (read only, no rollback), conditions, events. Workload lists flag workloads whose pods are failing.

CPU / memory

  • Usage against the limit in lists, cards and drawers; CPU / Memory columns sort by share of the limit.
  • 1h / 6h / 24h charts from a 30 s in-memory sampler (needs metrics-server), or up to 7 days from the cluster's Prometheus (Admin → Clusters → Prometheus): in the cluster through the API server proxy, or any Prometheus-compatible URL with basic / bearer / Azure AD / mTLS, extra headers and a multi-cluster label. Test connection explains what is wrong, step by step.

Also

  • Logs: switching streams no longer shows the old stream's close / error lines; multi-container pods open on the default container.
  • The dashboard opens in list view; every cluster is connected at startup.
  • Accessibility: 0 axe violations on the new screens in a real browser, light and dark.

Upgrading

  1. Re-apply deploy/rbac.yaml (or rbac-readonly.yaml): new rules for replicasets (revisions) and metrics.k8s.io pods (usage). Without them those parts are hidden, nothing breaks.
  2. Optional: for Prometheus "in the cluster" mode, uncomment the services/proxy rule and name your Prometheus Service.
  3. New env var RESTART_HISTORY_RETENTION_DAYS (default 30).

Image

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

🤖 Generated with Claude Code