Kubernetes Operational View provides a read-only system dashboard for multiple K8s clusters. Provides a common operational picture for multiple Kubernetes clusters.


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


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.

Tell us about a new Kubernetes application


Never miss a thing! Sign up for our newsletter to stay updated.


Discover and learn about everything Kubernetes