Rune for Mac, iPhone, and iPad
Kubernetes troubleshooting without losing cluster context.
Rune keeps K8s cluster health, workload details, pod logs, YAML manifests, port forwarding, Auth Doctor checks, RBAC Can I, and command navigation in one native workflow for practical cluster work.
Why Rune
Debug Kubernetes without losing context.
Keep pods, deployments, services, events, RBAC, manifests, and logs in one native workspace. Inspect state and take action without rebuilding terminal context for every command.
Fast resource scanning
Move through workloads, networking, config, storage, RBAC, Helm, and events while context and namespace remain visible.
Operational details close by
Open logs, describe output, YAML, rollout controls, Auth Doctor, and service actions from the selected resource.
Safe demo before install
Try the workflow against sample resources before connecting Rune to a cluster.
Feature screenshots
K8s troubleshooting workflows in screenshots.
These screenshots use a simulated sample cluster and show the main workflows Rune exposes in the Mac app.
Overview
Cluster health without hunting through kubectl commands.
See resource counts, cluster signals, pod health, recent events, context, namespace, CPU, memory, and read/write mode in one place.
Auth and RBAC
Debug RBAC forbidden errors before you chase the wrong problem.
Auth Doctor checks kubeconfig, context, namespace access, API transport, pod logs, exec, port-forward permissions, and RBAC preflight. The RBAC view also includes a read-only Can I check backed by SelfSubjectAccessReview for kubectl can-i style checks.
YAML validation
Edit Kubernetes manifests with syntax feedback before apply.
Inspect Kubernetes YAML manifests with syntax highlighting, validation warnings, managed-field hiding, quick edit, server dry-run, diff preview, and a copyable kubectl command before a write.
Describe output
Keep describe, events, and YAML in the same inspection flow.
Use describe output when troubleshooting CrashLoopBackOff, ImagePullBackOff, rollout issues, readiness problems, and event-heavy incidents. Rune keeps describe, YAML, logs, and export actions next to the selected resource.
Networking
Port-forward from the service you are already viewing.
Select a service, choose ports, start forwarding, and jump into a terminal-oriented workflow when you need to keep investigating.
Terminal and logs
Save, open, search, and export pod logs without rebuilding context.
Open terminal workflows from selected pods, read recent logs, search output, save logs as .log, save pod log ZIPs, open saved exports from the default folder, and copy generated commands when you need to continue in another shell.
Command palette
Jump straight to resources, namespaces, RBAC, and actions.
Search pods, deployments, services, config maps, RBAC resources, contexts, namespaces, saved workspaces, reload, read-only mode, and k9s-style commands from the command palette.
Complete feature list · 1 of 3
Everything available in Rune.
Start with the cluster and resource workspace. Each page links to a safe sample workflow that uses simulated data and no credentials.
Cluster and resource workspace
Context and namespace switching, cluster overview, resource counts, health signals, search, filters, favorites, and browsing for Pods, Deployments, StatefulSets, DaemonSets, Jobs, CronJobs, ReplicaSets, HPAs, Services, Ingresses, NetworkPolicies, PVCs, PVs, StorageClasses, Nodes, ConfigMaps, Secret metadata, Roles, bindings, cluster roles, events, and Helm releases. Includes command-palette navigation, section shortcuts, context and resource favorites, and desktop, iPhone, and iPad layouts. Try resource browsing.
Complete feature list · 2 of 3
Inspect and change YAML safely.
Review live resources, prepare edits, and verify the result before applying a change.
Inspection, YAML, and safe changes
Resource summaries, related objects, events, describe output, manifests, syntax feedback, validation warnings, managed-field hiding, local drafts, quick edit, undo, revert, import, export, server dry-run, diff preview, generated kubectl commands, apply, rollout controls, scaling, and read-only protection. Try the YAML editor.
Complete feature list · 3 of 3
Use logs, terminal, and network tools.
Keep operational evidence and the relevant action beside the selected resource.
Logs, terminal, and networking tools
Per-resource and related logs, container and time-window selection, text filtering, tail and pause, reload, save as .log, visible or full ZIP export, pod-log bundles, saved-export handoff, pod exec, editable shell commands, reusable command shortcuts, copy, session output, service port selection, and port-forward start and stop. Auth Doctor checks kubeconfig, context, namespace, API transport, logs, exec, port-forward, and RBAC; Can I checks, read-only mode, support bundles, hardware shortcuts, and terminal paste safety are included too. Try log tools or run Auth Doctor.
Workflow
Move from problem to evidence without rebuilding context.
1. Debug inside Rune
Pick the right kubeconfig context and namespace, then move through resources, pod logs, events, YAML manifests, describe output, Auth Doctor, and RBAC checks without rebuilding terminal state.
2. Save the evidence you need
Export logs, pod log ZIPs, YAML manifests, describe output, Auth Doctor bundles, and generated kubectl commands when you need to keep or share troubleshooting context.
3. Open exports where you work best
Open saved logs and manifests in your preferred editor, inspect text in Inkline, or browse ZIP exports in QuikZip.
Rune Mobile
Check a cluster from iPhone or iPad.
Switch contexts and namespaces, inspect resources, read logs, review YAML and events, run Auth Doctor, check RBAC, and use read-only mode from the mobile app.
Kubernetes troubleshooting
Find the cause of RBAC and pod failures.
Keep the context, evidence, and relevant actions together while you work through the failure.
How do I troubleshoot Kubernetes RBAC forbidden errors?
Confirm the context and namespace, run Auth Doctor, then use RBAC Can I to check the verb, resource, API group, subresource, and scope.
How do I troubleshoot a failing Kubernetes pod?
Compare status, restarts, events, logs, describe output, and the manifest in one place for CrashLoopBackOff, pending pods, ImagePullBackOff, and failed readiness checks.
Kubernetes troubleshooting
Debug services, YAML, and logs.
How do I debug Kubernetes service and port-forward issues?
Confirm the namespace, service, selected workload, target port, and related events. Rune exposes service details, port-forward controls, logs, and terminal-oriented actions from the selected resource.
How do I inspect Kubernetes YAML safely?
Review live YAML with syntax highlighting and validation, hide managed fields, use server dry-run and diff preview, then copy the kubectl command or apply the change.
How do I save and open Kubernetes logs quickly?
Search output, save a .log file, export visible or full logs as ZIP, and open the result from the default export folder.
FAQ
What Rune does.
What is Rune?
Rune is a Kubernetes troubleshooting client for Mac, iPhone, and iPad with resource browsing, logs, YAML validation, Auth Doctor, RBAC checks, port forwarding, and command navigation.
Does Rune validate YAML?
Yes. Rune shows Kubernetes YAML with syntax highlighting, validation feedback, quick edit, server dry-run, diff preview, and managed-field hiding.
Can Rune help with RBAC?
Yes. Rune includes RBAC resource browsing, command palette jumps, Auth Doctor RBAC preflight checks, and read-only Can I checks.
Demo and download
Try Rune before connecting a cluster.
Is the web demo connected to a real cluster?
No. The demo uses simulated Kubernetes resources, so it is safe to explore without credentials, production data, or a kubeconfig.
Where do I get Rune?
Try the browser demo first, install Rune from the App Store, or review the GitHub README for technical details.
Try Rune
Explore the workflow before installing.
Start with the sample-cluster browser demo, then move to the native app when you are ready to use Rune with your own Kubernetes contexts.