Owlpane / Solutions / Kubernetes operations

Use cases · built on OpenTelemetry

See what is happening inside the cluster — and act on it safely.

One Helm install for nodes, workloads, pods, network dependencies and security posture, correlated with the traces and logs your apps already send. Restart or scale through an in-cluster runner, attributed to a person.

Owlpane console
Owlpane Kubernetes overview: node and pod health tiles and a grid with one square per pod on each node.

The problem

Why this is hard today

kubectl archaeology

Finding why a pod restarts means stitching events, logs and metrics by hand.

Who talks to whom?

Service dependencies and denied traffic are invisible until something breaks.

Risky fixes

Restarting or scaling from a laptop leaves no record of who did what.

What you use

Built from features that ship today

Pods and workloadsKubernetes
Network mapKubernetes
Security postureKubernetes
Safe operationsKubernetes

Pods and workloads

CPU and memory against requests and limits, restarts and reasons, with a jump from any pod to its traces.

Kubernetes →

Network map

Workload dependencies from observed flows merged with APM traffic, including denied traffic.

Kubernetes →

Security posture

A CIS-aligned score with findings you can suppress with a reason and export as JSON, CSV or SARIF.

Kubernetes →

Safe operations

Restart, scale, expand a PVC or apply a NetworkPolicy through a runner in your cluster; every operation is queued and attributed.

Kubernetes →

How it works

Three steps

01

Install

One Helm chart deploys a cluster collector and node agent with a read-only ClusterRole.

02

Correlate

Spans and logs are stamped with Kubernetes attributes, so every pod links to its requests.

03

Act

Optionally enable the ops runner to restart, scale or expand storage from the console, with an audit trail.

Questions

Does it need write access to my cluster?
No. The chart’s ClusterRole is read-only (get / list / watch). Restart, scale and storage operations need the optional ops runner, which you choose to enable.
Is this a cost tool?
No. You get usage metering and request-versus-use views, not a cost-optimisation engine.

Where Owlpane is narrower

  • The Kubernetes agent is in beta.
  • Network flows need flow data from the bundled collector or forwarded from Cilium/Hubble.
  • Security posture is a Kubernetes check set, not a full CNAPP or SIEM.

Send a copy of your telemetry. Change nothing else.

Standard OpenTelemetry in, so you can try Owlpane beside what you run today.

Every new workspace starts with a 14-day Team trial: 50 GB of ingest a month and 30-day retention. No card to start. Documentation · Pricing · Pricing questions