Kube Ops View gives operators a visual picture of where Kubernetes workloads are running and how machines are being used. Its read-only display shows nodes, Pod placement and resource information, making it useful for understanding cluster layout without examining every object individually. Reserved resources and actual usage are different views of capacity, so interpret them separately. The project's move from GitHub to Codeberg also means the archived old repository is not itself proof of retirement.
Current guidance
The original hjacobs/kube-ops-view GitHub repository now contains a relocation notice pointing to Codeberg. The GitHub archive state therefore does not by itself mean the operational dashboard was retired. Use the maintainer-declared destination when checking current releases, while keeping the old URL as historical provenance.
The recovered tool is a read-only visualization of Kubernetes nodes, pod placement and resource usage. Distinguish resource requests from actual utilization when interpreting its display: reserved CPU or memory and observed consumption answer different capacity questions. A visual gap or stale value can also reflect unavailable metrics or API access.
Protect access even for a read-only dashboard, since names, topology and workload metadata can reveal sensitive operational information. Scope its Kubernetes credentials to the clusters and namespaces it must inspect, and verify authentication at the exposed endpoint. Compare displayed values with authoritative API and metrics responses during a controlled change. The relocation is verified, but this review does not certify the current Codeberg release’s compatibility, authentication defaults or maintenance policy.
Historical upstream link check · 2026-10-09
The recorded upstream address responded successfully (HTTP 200) on 2026-10-09. GitHub marks hjacobs/kube-ops-view as archived. This confirms the repository's read-only archive state; any successor or supported distribution needs separate evidence. Link availability does not certify the historical installation instructions or current security support.
Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.
Historical Kubedex content
Preserved for context. Commands, versions, prices and results below reflect the original research.
Kubernetes Operational View provides a read-only system dashboard for multiple K8s clusters. Provides a common operational picture for multiple Kubernetes clusters.
Goal:
provide a common operational picture for multiple Kubernetes clusters.
- Render nodes and indicate their overall status (“Ready”)
- Show node capacity and resource usage (CPU, memory)
- Render one “box” per CPU and fill up to sum of pod CPU requests/usage
- Render vertical bar for total memory and fill up to sum of pod memory requests/usage
- Render individual pods
- Indicate pod status by border line color (green: ready/running, yellow: pending, red: error etc)
- Show current CPU/memory usage (gathered from Heapster) by small vertical bars
- System pods (“kube-system” namespace) will be grouped together at the bottom
- Provide tooltip information for nodes and pods
- Animate pod creation and termination
What it is not:
- It’s not a replacement for the Kubernetes Dashboard. The Kubernetes Dashboard is a general purpose UI which allows managing applications.
- It’s not a monitoring solution. Use your preferred monitoring system to alert on production issues.
- It’s not a operation management tool. Kubernetes Operational View does not allow interacting with the actual cluster.
Pod Status
- Each pod indicates its status by color and animation:
- Running and all containers ready: constant green
- Running and not all containers ready: flashing green
- Pending or ContainerCreating: flashing yellow
- ImagePullBackoff or CrashLoopBackoff: flashing red
- Succeeded (for jobs): blue
Tooltips
Various UI elements provide additional tooltip information when hovering over them with the mouse:
- Hovering over the title bar of a node box reveals the node’s labels.
- Hovering over the vertical resource bars will show the node’s capacity, sum of all resource requests and current resource usage.
- Hovering over a pod will show the pod’s labels, container status and resources.
Filtering Pods
- Kubernetes Operational View allows you to quickly find your running application pods.
- Typing characters will run the filter, i.e. non-matching pods will be greyed out.
You can filter by:
- name
- labels – when query includes =, e.g. env=prod
The pod filter is persisted in the location bar (#q=.. query parameter) which allows to conveniently send the filtered view to other users (e.g. for troubleshooting).
Sorting Pods
Pods can be sorted by different properties:
- pod name (this is the default)
- age (start time)
- memory usage (metric collected from Heapster)
- CPU usage (metric collected from Heapster)
- Sorting by memory or CPU allows finding the most resource hungry pod (per node).
Filtering Clusters
Clicking on a cluster handle (the top bar of the cluster box) will toggle between showing the single cluster alone and all clusters.
Sources & further reading
Spotted something that needs another look?
Help improve this page →