Kubernetes. Pods, Deployments, Nodes, Services, and more.
Install the Polylane agent in any Kubernetes cluster 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
The in-cluster agent runs with read-only RBAC, and Polylane only makes read-only Kubernetes API calls.
How it works.
Connect
Install the Polylane agent in your cluster with one Helm command. It registers itself over an outbound tunnel, and your cluster credentials never leave the cluster.
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.
Namespace Node Deployment StatefulSet DaemonSet ReplicaSet Job CronJob Pod Service Ingress ConfigMap Secret Service Account Role Role Binding Cluster Role Cluster Role Binding Persistent Volume Persistent Volume Claim Storage Class Network Policy Horizontal Pod Autoscaler Pod Disruption Budget 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)
Questions.
Is Polylane an AI SRE for Kubernetes?
It's what most people mean by the term: agents that keep your Kubernetes resources in one context graph, watch them, investigate issues and fix what they can, with a human approving anything that changes production. We call it self-operating software rather than an AI SRE: the point is that your software looks after itself, not that a bot joins the on-call rotation.
Can Polylane change anything in Kubernetes?
Only if you let it. Connected read-only, agents investigate and explain, and changes only ever land as pull requests for you to review. With write access, every write pauses for your approval first, with the method, path and reason on screen. Rollbacks are off by default: you enable them per automation and can turn them off at any time.