Skip to content

Getting started ​

Wiring's main view is a live graph of a namespace: Ingress → Service → Deployment → Pod, plus the ConfigMaps, Secrets, PersistentVolumeClaims, ServiceAccounts and HorizontalPodAutoscalers each workload uses. Select an object to highlight what it is connected to. From the same window you can read and edit its YAML, check its events, stream its logs, open a shell in it and forward a port to it.

It is built with Tauri 2, React and Rust (kube-rs), and runs on macOS and Windows.

Install ​

Download the latest installer from Releases.

PlatformFileFirst launch
macOS (Apple Silicon and Intel)Wiring_<version>_universal.dmgThe build is unsigned, so macOS asks you to confirm it the first time. See macOS asks you to confirm the app.
Windows 10/11Wiring_<version>_x64_en-US.msi or Wiring_<version>_x64-setup.exeThe build is unsigned. When SmartScreen appears, choose More info → Run anyway.

The Windows installer wears Wiring's own dark theme.

macOS asks you to confirm the app ​

Wiring for macOS is not signed with a Developer ID yet, so Gatekeeper stops the app the first time you open it and says that the file could not be verified, that Apple could not check it for malicious software. That is the expected message for an unsigned build, not a damaged download. Three ways past it, easiest first:

  • Right-click, then Open. In the Finder, right-click Wiring.app in Applications and choose Open. The follow-up dialog has an Open button too, and the app opens without asking again.

  • Clear the quarantine flag. The browser marks the download; this clears the mark:

    bash
    xattr -dr com.apple.quarantine /Applications/Wiring.app
  • Download it from a terminal. The quarantine mark is set by the browser, not by the download itself, so fetching the .dmg with curl leaves it off and the app opens without any prompt:

    bash
    curl -L -O https://github.com/skensell201/wiring/releases/download/v<version>/Wiring_<version>_universal.dmg
    hdiutil attach Wiring_<version>_universal.dmg
    cp -R /Volumes/Wiring*/Wiring.app /Applications/
    hdiutil detach /Volumes/Wiring*

Your kubeconfig ​

Wiring reads your kubeconfig from ~/.kube/config, or from KUBECONFIG when it is set. You can also add a kubeconfig file from inside the app with Add kubeconfig…. A file without contexts is refused. If Wiring finds no contexts at all, it opens on a welcome screen. That screen lists each file it looked at and what it found there (not found, can't be read, no contexts), with Add kubeconfig… and Rescan. On Linux, where no system installer carries the brand, that first screen opens with the mark and one line of what Wiring is.

Login helpers ​

Clusters that sign in through a helper program, such as gke-gcloud-auth-plugin, aws or kubelogin, need it installed. On macOS and Linux, Wiring uses your login shell's PATH, so it finds a helper installed with Homebrew or a cloud SDK even when you start Wiring from the Dock or a launcher. (When you start Wiring from a terminal, it already has your PATH.) Restart Wiring after installing one.

Try it on a demo cluster ​

examples/demo/setup.sh works against any local cluster (Docker Desktop, kind, minikube). It deploys:

  • two namespaces, shop and blog, including deliberately broken workloads (an image that cannot be pulled, a container that crashes on start);
  • the wiring-viewer and wiring-auditor RBAC identities, with matching restricted kubeconfig contexts, so you can see how Wiring handles kinds a role cannot read.
bash
examples/demo/setup.sh                 # uses the docker-desktop context
examples/demo/setup.sh kind-kind       # or name another context
examples/demo/setup.sh --with-metrics  # also install metrics-server (flag and context can be combined, in any order)

--with-metrics applies the official metrics-server manifest and adds --kubelet-insecure-tls (once; re-running is safe), which local clusters need. It makes the CPU and Memory columns and the Overview usage rows show data; without metrics-server they stay empty.

The manifests are in examples/demo/: shop.yaml, blog.yaml and rbac.yaml.

Next: the graph and the navigator.