How to Use KubeNav: Manage Your Kubernetes Cluster From Your Phone
CodexFuse Team · 2026-11-02T00:44:09.186Z · 12 min read min read
How to Use KubeNav: Manage Your Kubernetes Cluster From Your Phone
Learning how to use KubeNav is the fastest way to stop running back to your laptop every time a pod goes sideways. KubeNav is a free, open-source mobile Kubernetes dashboard for iOS and Android — pronounced "koo-buh-nav" — that puts your kubeconfig in your pocket: same clusters, same Kubernetes API, a phone-sized screen. This beginner kubenav tutorial walks you from install to first cluster import, the namespace lesson, your first pod check, and the on-call habit that makes KubeNav worth keeping on your home screen. It assumes you have a working cluster somewhere reachable; if you are still learning containers from zero, start with our Docker beginner guide first.
What Is KubeNav, Exactly?
KubeNav is a mobile app that speaks to your Kubernetes API server the way kubectl does, except the controls are built for touch. You point it at one or more clusters — cloud-managed or self-hosted — and you get the full resource browser: pods, deployments, services, logs, a terminal, port-forwarding, even Helm releases. As a kubernetes mobile app, it is built for triage and quick fixes rather than deep configuration sessions. Version 5.6.0 is the current release (September 2026), the app is MIT-licensed, and both store listings are free with no paywalled features.
One lane line before anything else: K9s is the terminal dashboard for your laptop; KubeNav is the mobile app for your phone. K9s is a TUI you drive with a keyboard; KubeNav is a touch UI you drive with a thumb. Different screens, different moments — they never rival each other.
How Do You Install KubeNav?
Install KubeNav from your phone's app store in under a minute. On Android, search for "kubenav" on Google Play (the kubernetes dashboard android listing — package io.kubenav.kubenav, current version 5.6.0, updated September 13, 2026, free, developer Rico Berger). On iOS, search the App Store for "kubenav — Kubernetes Dashboard" (version 5.6.0, dated September 2026, free, requires iOS 15.0 or newer). The iOS listing shows optional "Sponsor" in-app purchases — those are donations, not features.
That is the whole install. KubeNav ships with no clusters configured and no sign-up, so the app opens on an empty Clusters page and your very first real task is importing a cluster.
What Do You Need Before Your First Import?
You need one thing: a kubeconfig for a cluster your phone can actually reach. Your phone talks directly to the cluster's API server, usually on TCP port 6443. If that API server address is not reachable from your phone — not your laptop, your phone — nothing else in this guide works.
The classic beginner trap is the local cluster. minikube and kind bind their API server to localhost (127.0.0.1) on your laptop, and a phone cannot reach your laptop's loopback address. So your first run works with a cloud cluster (GKE, EKS, AKS, DigitalOcean) or a cluster on your LAN with a reachable address — our K3s beginner guide covers setting one up on your own hardware. Most clusters worth monitoring live on a VPS hosting box or a managed service, which is exactly what KubeNav was built to watch.
How Do You Import Your First Cluster?
Importing a cluster is the single most important step in KubeNav, so learn it properly. Tap the Clusters icon, hit the plus, and KubeNav offers four routes. Pick the one that matches how you authenticate.
Route 1: the kubeconfig provider
Choose this when you have a normal kubeconfig file from kubectl. You either select the file in a file dialog or paste its contents. Two rules decide whether this works. First, the filename must end in .yaml, .yml, .txt, or .conf. Second, the certificates must be embedded as base64 data in the file — if your kubeconfig references certificate files by path (certificate-authority: /path/to/ca.crt), the phone has no such files and the import will fail. Embed them or pick a different route.
One more hard rule: kubeconfigs that rely on cloud-provider or OIDC exec authentication will fail this import. KubeNav cannot run the helper binary your kubeconfig points at. If your kubeconfig has an exec section, skip to the provider flows below.
Route 2: provider flows
Choose this when your cluster lives on a managed platform. KubeNav ships native sign-in flows for Google/GKE (OAuth Client ID and Secret), AWS/EKS (Access Key ID, Secret Access Key, Region, optional session token and role ARN), AWS SSO (Start URL, Account ID, Role Name, SSO Region), Azure/AKS (Subscription ID, Tenant ID, Client ID, Client Secret, plus an admin flag), OIDC providers (discovery URL, client ID and secret, PKCE, scopes, CA, refresh token), DigitalOcean (Personal Access Token), and Rancher (server address plus username/password or token). These flows exist precisely to replace the exec-auth kubeconfigs that Route 1 rejects in your kubenav kubernetes setup.
Route 3: manual entry
Choose this when you built the cluster yourself and want tight control. You enter the server URL, certificate-authority data, client certificate and key, a token, or username and password, plus a default namespace. If you do not have a ServiceAccount token yet, KubeNav's in-app help ships the exact ClusterRole, ClusterRoleBinding, and token-creation commands to bootstrap one.
What if the phone cannot reach the API server?
This is the reachability lesson, stated once and clearly: your phone must be able to open a TCP connection to the API server address in your kubeconfig. For a laptop-local cluster, rewrite the kubeconfig's server: field from 127.0.0.1 to your machine's LAN IP and open 6443. For a cluster behind your home network, the same rule applies to the router. If you refuse to expose the port, run the connection through a VPN — a Tailscale beginner guide gets your phone and your cluster on the same private network in minutes, and KubeNav works over it like any other connection.
After a successful import, the cluster appears in your list with a green status. Tap it, and you land on the resource browser. Nothing useful happens until the next lesson.
Why Does Everything Look Empty? Set Your Namespace First
Here is the namespace lesson, and it is the one that confuses every KubeNav beginner: almost everything in Kubernetes lives inside a namespace, and KubeNav shows you only the namespace you selected. If you import a cluster and your pods list is empty, you are almost certainly looking at the default namespace while your workloads run somewhere else.
Tap the Namespaces icon on any resource list page to switch. Better: open Settings, then Namespaces, and keep a starred, sorted list of the namespaces you actually care about — production, staging, monitoring. The five seconds you spend starring namespaces here save you fifty taps a week later.
How Do You Check a Pod on Your Phone?
A first pod check takes about thirty seconds and follows one path: Pods → select the pod → Logs → Terminal. Open the Pods list in your workload's namespace, tap the pod, and the detail page shows status, restarts, and the container list. Tap a container to stream its logs with a selectable time range; hit the Terminal tab to exec a shell into that container (pick the container and the shell first, long-press the tab to close it).
This is the entire debugging loop on mobile: confirm the pod is the broken one, read the logs to see why, drop into the container to poke around. The 2026 releases fixed long-standing list bugs (the 5.6.0 release notes call out the Helm release list and AWS SSO token fixes specifically), so lists you once could not trust now update properly.
What Can You Actually See and Do in KubeNav?
KubeNav's resource browser covers more Kubernetes than most beginners expect. Here is the tour, grouped the way the app groups it.
| Group | What you get | Beginner note |
|---|---|---|
| Workloads | Pods, Deployments, StatefulSets, DaemonSets, Jobs, CronJobs, ReplicaSets | Day-to-day debugging lives here |
| Networking | Services, Ingresses and IngressClasses, NetworkPolicies, Endpoints | Check Services when the app is reachable but pods look fine |
| Scaling | HorizontalPodAutoscalers | Autoscaling questions start here |
| Configuration | ConfigMaps, Secrets, ServiceAccounts, Custom Resource Definitions plus their custom resources | Secrets are viewable — guard them like passwords |
| Access control | Roles, ClusterRoles, and their bindings | Why-can't-this-pod-read-that answers |
| Infrastructure | Namespaces, Nodes, PersistentVolumes and Claims, StorageClasses, LimitRanges, ResourceQuotas, PodDisruptionBudgets | Nodes and PVCs answer the "where is it running" questions |
| Events | A dedicated Events view across resources | Check Events first when a pod keeps restarting for no logged reason |
You can view, edit, and delete resources, and scale Deployments, StatefulSets, and DaemonSets — so treat the app with the same respect as kubectl: you have real power in your pocket. Port-forwarding is built in too: open a pod, find the port in its Configuration section, and a global Port-Forwarding Sessions icon manages the tunnel — open it in your phone's browser, copy the address, or delete the session when done.
How Do You Build the On-Call Habit?
On-call work in KubeNav is a triage habit, not a notification system. The app does not send you push alerts about cluster problems — plan around that honestly, and keep your existing alerting (PagerDuty, Slack bots, whatever your team runs) as the thing that wakes you. KubeNav is what you open after the alert, and learning to manage kubernetes from phone is what turns that 2 a.m. wake-up into a five-minute job instead of a laptop boot.
The habit has three parts. First, add every cluster you are on-call for — the cluster switcher handles multiples and the list is sortable. Second, bookmark everything you check repeatedly: the bookmark icon sits on resource lists and detail pages, and long-pressing a bookmark deletes it. Third, rehearse the triage path until it is muscle memory: switch cluster → set namespace → Events view for the blast radius → broken pod's logs → terminal if needed. The whole pass takes a minute on a phone, and it is the difference between "I need my laptop" and "handled" at 2 a.m.
Do You Need the Plugins?
KubeNav ships optional plugins for the ecosystem around your cluster. Helm shows and manages your releases (the 5.6.0 release fixed the release list showing only deployed releases, and viewing releases needs view-secrets permission). Prometheus brings workload metrics: the default metrics need kubelet plus kube-state-metrics, custom metrics come from the kubenav.io/prometheus annotation, and custom dashboards arrive as ConfigMaps labeled kubenav.io/prometheus=dashboard. There are also plugins for Argo, cert-manager, and Flux. Install the ones your cluster actually runs; skip the rest until you need them.
What Does KubeNav Cost, and Is It Safe?
KubeNav is free and open source under the MIT license — the GitHub project (kubenav/kubenav, Dart with a Go backend via gomobile, created January 2020) carries over two thousand stars. Both store listings show a zero price; the iOS "Sponsor" purchases are voluntary donations. Credentials are stored in the phone's secure storage and protected by biometric authentication, so a lost phone does not mean a leaked cluster.
7 Mistakes KubeNav Beginners Make
| Mistake | Why it hurts | Do this instead |
|---|---|---|
| Importing a kubeconfig with exec auth | Import silently fails — the phone cannot run your cloud CLI helper | Use the matching provider flow (GKE/EKS/AKS/OIDC) |
| Referencing certificate files by path | Those paths exist on your laptop, not your phone | Embed certificates as base64 data in the kubeconfig |
| Pointing at 127.0.0.1 | A phone cannot reach your laptop's loopback | Use a LAN/VPN-reachable address in the server field |
| Staring at an empty pod list | You are in the wrong namespace | Switch namespaces; star your real ones in Settings |
| Expecting push alerts | KubeNav has no notification feature | Keep your real alerting; use KubeNav for triage |
| Editing resources casually | You have kubectl-level power on a small screen | Read first, edit deliberately, use read-only accounts for juniors |
| Skipping the Events view | Logs explain code failures; events explain platform failures | Check Events before assuming the app is broken |
Sources
- KubeNav GitHub repository — kubenav/kubenav — release v5.6.0 notes (published September 14, 2026), license, language, star and fork counts, fetched November 2, 2026 via the GitHub API
- KubeNav repository README (main branch) — feature list, resource views, logs, terminal, port-forwarding, plugins, fetched November 2, 2026
- KubeNav in-app help source — lib/models/help.dart (main branch) — cluster import routes, ServiceAccount bootstrap commands, secure storage and biometric authentication notes, fetched November 2, 2026
- KubeNav cluster provider source — lib/models/cluster_provider.dart (main branch) — provider enum confirming the available import routes and no QR import, fetched November 2, 2026
- KubeNav resources source — lib/widgets/resources/resources/resources.dart (main branch) — resource view list, fetched November 2, 2026
- Google Play listing — KubeNav by Rico Berger, version 5.6.0, updated September 13, 2026, free, fetched November 2, 2026 (version data via AppBrain, listing updated September 28, 2026)
- Apple App Store listing — "kubenav — Kubernetes Dashboard", version 5.6.0, dated September 2026, free, iOS 15.0+, 4.9 rating, fetched November 2, 2026
- Headworq — "3 ways to connect to your K3s Kubernetes Cluster" — KubeNav kubeconfig import subsection and the TCP/6443 reachability rule, fetched November 2, 2026
- Palark — "kubenav as a tool for managing Kubernetes clusters from your smartphone" (February 17, 2022) — independent review, not a walkthrough, fetched November 2, 2026
Frequently Asked Questions
Is KubeNav free?
Yes. KubeNav is free and open source under the MIT license on both the Google Play Store and the Apple App Store. The optional Sponsor in-app purchases on iOS are donations to the developer — no features are paywalled.
Can KubeNav manage multiple clusters?
Yes. You can add any number of clusters through any of the import routes, switch between them from the Clusters icon, and sort the list. Namespaces are managed per cluster.
Why does KubeNav reject my kubeconfig?
The two common causes are exec-based authentication (cloud CLI helpers like aws-iam-authenticator, which the phone cannot run — use a provider flow instead) and certificate references by file path (which do not exist on the phone — embed the certificates as base64 data).
Can I use KubeNav with a minikube or kind cluster on my laptop?
Not out of the box. minikube and kind bind their API server to localhost, which your phone cannot reach. Point the kubeconfig's server field at a reachable address (your laptop's LAN IP with port 6443 open) or connect the phone through a VPN to reach the cluster.
KubeNav vs K9s — which should I use?
Both, for different moments. K9s is the terminal dashboard for your laptop keyboard; KubeNav is the mobile app for your phone. KubeNav wins when you are away from your desk; K9s wins when you are at it.
