Kubernetes. Pods, Deployments, Nodes, Services, and more.
Connect any Kubernetes cluster with a kubeconfig or a ServiceAccount token to give agents read-only visibility into your workloads. Agents can map your cluster topology, inspect pods, deployments and nodes, read logs and events, and help troubleshoot incidents.
Join the waitlistWhat Polylane does with Kubernetes.
The full cluster topology
Deployments, StatefulSets, pods, services, ingresses, CronJobs, and 24 resource types in all, alongside the clouds the cluster runs on.
The failures Kubernetes hides well
Crashloops, OOM kills, pods stuck pending, rollouts that never converge. The cluster knows; Polylane investigates and writes up what happened.
Direct inspection
Agents inspect pods, read logs and events, and map the topology on a cadence. No dashboards in the loop.
get, list, watch, and nothing else
Polylane only makes read-only Kubernetes API calls, and you can scope the ServiceAccount to a single namespace.
How it works.
Connect
Paste a kubeconfig or a read-only ServiceAccount token. Credentials are encrypted before they're stored, and the agent never sees them.
Map
The cluster topology lands in the graph, and every sync after records what changed.
Agents take the watch
Workloads are watched as they churn, failures get investigated as they happen, and manifest fixes arrive for your review.
In the graph.
The Kubernetes resource types Polylane syncs, with their edges, config, and history.
The tools agents get.
What an agent can do with Kubernetes mid-investigation. Every call lands in the thread transcript, cited.
kubectl Read and operate on Kubernetes resources on a connected cluster (get/list/describe/logs/events/top/rollout, plus scale, restart, patch, delete, apply)