Local Kubernetes dashboard for kind and minikube

For a local Kubernetes dashboard, first decide whether you want a desktop client using kubeconfig or a web UI running alongside the cluster. Both can be useful. This guide starts from an existing development cluster; it does not install or change one for you.

Confirm the cluster works before adding a UI

Follow the kind quick start or your cluster tool’s documentation first. Confirm that the cluster is running and that its context appears in your kubeconfig. A desktop app cannot repair a stopped container runtime or expired credentials.

If you already use minikube and want its web dashboard, the minikube dashboard documentation describes the add-on and proxy workflow. That is a different deployment choice from connecting a desktop client.

Connect a development context in Aster

  1. Download a current build for your platform from the download section.
  2. Open Aster and select the kubeconfig source and development context you intend to inspect.
  3. Choose a namespace and resource kind. Confirm the resource names against something you recognize in that cluster.
  4. Open a workload, inspect its details and follow a short section of pod logs.
  5. Switch away and back, checking the context name before every further action.

Aster uses your existing access. It does not need you to create a ServiceAccount or ClusterRole as a convenience setup step. Use a development cluster while learning the interface.

If the expected resources do not appear

The context is missing

Check the kubeconfig source you selected and whether the cluster tool wrote the context where you expect. A context name in an old file is not proof that its API endpoint still exists.

The connection fails

Confirm the development cluster and its container runtime are running. If the kubeconfig depends on an external authentication tool, verify that tool’s setup before assuming the GUI is at fault.

The list is empty or forbidden

Check namespace and resource kind first. A forbidden response is different from an empty list and should be resolved through the access policy, not by granting blanket administrator permissions.

Keep local convenience separate from cluster safety

A local cluster still has meaningful state. Inspect first, then review any supported change before applying it. Aster’s bounded one-shot terminal and reviewed mutations are not a general-purpose persistent shell or an unrestricted cluster administration layer.

For more context, see the Kubernetes GUI overview. If your next step is diagnosing a workload, continue with the log viewer guide.