Cloud provider

Kubernetes

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.

Connect

Connect Kubernetes from the terminal. Pass --help for the flags Kubernetes accepts, plus --no-browser for headless environments.

Terminal

polylane cloud connect --provider kubernetes

Read-only ServiceAccount credentials, via kubeconfig or manual entry.

Kubernetes connects with read-only ServiceAccount credentials. Polylane only makes read-only Kubernetes API calls. Your credentials are encrypted before they are stored, and the agent never sees the token.

You can connect in two ways.

Option 1: Kubeconfig

Paste a kubeconfig YAML. Polylane reads the API server URL, CA certificate, and token from the current context. The token must be a ServiceAccount bearer token (not a client certificate or exec plugin).

Option 2: Manual

Create a read-only ServiceAccount with a ClusterRole granting get, list, and watch.
Generate a token: kubectl create token <serviceaccount>.
Enter the API server URL and the ServiceAccount token.
Optionally provide a CA certificate, cluster name, and a namespace to restrict discovery and monitoring to. Leave the namespace blank to include all namespaces.

Polylane validates the credentials and starts syncing your workloads, services, and other cluster resources.

Disconnecting

Disconnect the cluster in Polylane, then delete the ServiceAccount (or its token) in your cluster.

Tools

Operations agents can perform in threads and automations.

kubectl

Read and operate on Kubernetes resources on a connected cluster (get/list/describe/logs/events/top/rollout, plus scale, restart, patch, delete, apply)

Supported resources

Resource types that show up in your infrastructure graph.

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

Automation triggers

Events from Kubernetes that can start an automation.

Cloud Account Connected

Fires once when a user connects a new cloud account to the workspace.

Cloud Account Synced

Fires each time a cloud account finishes a full or incremental sync.

Infra Node Created

Fires once per new infrastructure resource discovered during a cloud sync.

Automation templates

Pre-built automations that use Kubernetes. Open one to see its trigger, instructions, and actions.

Daily Kubernetes infrastructure audit

Run a daily audit of your Kubernetes observability setup and flag gaps in monitoring

Back to integrations