kubeconfig contexts
The kubeconfig file is the source of truth (`KUBECONFIG` or ~/.kube/config). Click a catalog row to open that context. The radio only writes kubectl current-context for the CLI. Several contexts can stay connected. Cloud… adds Google, Azure, Amazon, Oracle, DigitalOcean, or IBM via that provider’s CLI.
Navigator
Cluster, nodes, applications, workloads, config, network, storage, namespaces, events, Helm, Dapr, access control, and custom resources. Longhorn and CloudNativePG appear when those APIs are installed.
Workloads and YAML
Watched tables per cluster, apply/create/delete, scale, restart, rollout undo, node cordon and drain, follow logs, an interactive shell, and an ephemeral debug container. Resource limits can patch container CPU and memory against node capacity. Port-forwards persist and open in the browser.
Helm, Dapr, and volumes
Helm releases and Dapr resources already in the cluster. Browse, edit, download, and upload files on PersistentVolumes and PVCs. Resize a claim and change reclaim policy. Longhorn S3 Browser opens backup targets already configured in the cluster.
Ollama chat
Optional chat on the overview or the selected resource. Read-only by default (issues, YAML, logs, events) against Ollama on this PC. With changes allowed, restart, pod delete, scale, and apply each wait for Approve. No cloud AI.
Platforms
Windows (Microsoft Store, portable zip, and setup), Linux Flatpak (user or system), macOS DMG (Apple Silicon and Intel). macOS builds are unsigned; first launch is Open from the context menu.