See how your Kubernetes resources are wired together.
A desktop Kubernetes IDE with a live graph of your workloads, Services, config and storage, plus the tables, YAML editing, logs and terminal you reach for every day.
Also for Windows · build from source on Linux · all releases
Overview
Get started in three steps
No server, no agent in your cluster. Wiring talks to the API server with your own kubeconfig.
Download
Install the .dmg on macOS or the installer on Windows. On Linux, build from source.
Point it at your kubeconfig
Wiring reads
~/.kube/configorKUBECONFIG, or add a file with Add kubeconfig…Pick a cluster and namespace
The graph appears and keeps itself up to date.
Everything a namespace needs, in one window
Wiring watches your cluster and redraws as things change. Click any node or row to inspect, edit or act on it.
Live graph
Owners, selectors, mounts and routes drawn as edges. Problems show their reason and the path that caused them.
Tables and YAML
kubectl-style tables for every kind. Edit YAML with a diff before you apply, or create from a template.
Logs, terminal, port-forward
Stream logs across pods, open a shell in a container, and forward a port that follows rollouts.
Rollouts and scaling
Scale, restart and roll back workloads from the details panel or a right-click.
Metrics
CPU and memory from metrics-server in the tables, with badges when a pod nears its limits.
Namespaces and RBAC
Look at several namespaces at once. NetworkPolicies, Roles and Nodes in the graph. Kinds your role can't read are marked, not broken.
Custom resources and Helm
Browse and edit any CRD, and see Helm releases with their values, history and objects (read-only).
Automatic updates
Signed releases for macOS and Windows. Wiring tells you when a new one is out.
Tables and YAML
The kubectl view you know, sortable and searchable. Edit a row's YAML and see the diff before it is applied.
Contacts
Questions, bug reports or ideas for Wiring: write to me, I usually reply within a day.
- Emailskensel.software@gmail.comWrite an email →
- Telegram@skenselOpen in Telegram →
- GitHubgithub.com/skensell201See the code →
- LinkedInlinkedin.com/in/skenselConnect →
Your cluster, finally readable.
Free and open source under the MIT license.