The "Standard" Web UI
The Kubernetes Dashboard is the official, open-source web-based UI maintained by the Kubernetes project itself. It runs as a regular Pod inside your cluster, meaning you access it through a browser rather than installing anything locally. Think of it as the "factory default" option — it works everywhere, but it's not the most powerful tool available.
How it works: The Dashboard Pod runs inside the cluster and communicates with the Kubernetes API server directly. You access it by running kubectl proxy on your local machine, which creates a secure tunnel from localhost:8001 to the cluster's API server. The Dashboard is then reachable at a URL like http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard:/proxy/. Authentication is handled via a ServiceAccount token or kubeconfig file.
What it provides:
- Overview of workloads (Deployments, StatefulSets, DaemonSets, Jobs) with status indicators
- Basic YAML editing directly in the browser
- Log streaming for individual containers
- Basic CPU and memory graphs (requires the Metrics Server add-on to be installed separately)
- Namespace filtering to scope the view
Pros:
- Official and free — no third-party dependency
- Runs in the browser, so it works from any machine with cluster access
- Good for shared team visibility without requiring local tool installation
Cons:
- Security configuration is non-trivial. The Dashboard has historically been a target for attackers when accidentally exposed to the internet. Proper setup requires creating a ServiceAccount with appropriate RBAC permissions and handling token-based authentication carefully.
- Less responsive than local desktop applications — every action is a round-trip to the cluster API
- Metrics require a separate Metrics Server installation; it does not integrate with Prometheus out of the box
Typical Use Case: A shared read-only view for a team, or for quick access from a machine where you cannot install custom software. In production environments, access is typically restricted to VPN users or specific IP ranges.
Interviewers sometimes ask: "Is the Kubernetes Dashboard safe to expose publicly?" The correct answer is no — not without significant additional security controls. The Dashboard has been exploited in real-world attacks (notably the Tesla cryptomining incident in 2018) when left exposed without authentication. The safe pattern is to access it exclusively via kubectl proxy (which uses your kubeconfig credentials) or through an authenticated reverse proxy. Never expose the Dashboard Service as a LoadBalancer or NodePort without authentication middleware in front of it.