No KubeSpade account
Install and connect with GCP credentials or a kubeconfig. No vendor signup to browse your own GKE clusters.
Google Kubernetes Engine · macOS, Windows, Linux
A local Kubernetes GUI for Google Kubernetes Engine — connect once, then browse, debug, and operate without living in the Cloud console or a stack of kubectl windows.
Same jobs as kubectl against your cluster — in a desktop interface.
If you searched for a GKE desktop client, these are usually the deal-breakers elsewhere.
Install and connect with GCP credentials or a kubeconfig. No vendor signup to browse your own GKE clusters.
The app talks to the GKE Kubernetes API from your machine — the same path kubectl uses. We do not sit in the middle of your traffic.
GCP tokens, kubeconfig, and context stay local. There is no KubeSpade backend holding your cluster secrets.
Real UI from the Desktop app — click to enlarge.
CPU, memory, pods, and warnings on one screen — then drill into any resource on your GKE cluster.
Google GKE, Amazon EKS, Azure AKS, or paste a kubeconfig — multiple clusters, grouped your way.
The Google Cloud console is the right place for IAM, node pools, add-ons, and project-level GKE ops. A GKE desktop client is for the Kubernetes layer after the cluster exists — browsing pods, following logs, exec, YAML, Helm — without bouncing through the browser for every debug loop.
KubeSpade is built for that day-to-day layer. Keep the console for GCP; use the GUI when you want eyes on the cluster API.
A GUI does not replace kubectl for scripts, CI, or one-liners you already trust. It replaces the part where you live in the terminal to browse, debug, and operate. Keep kubectl for automation; use KubeSpade when you want a visual path into the same GKE API.
Stay on Lens if a Lens plugin or Pro workspace is load-bearing for your team. Stay in the Google Cloud console when the job is IAM, networking, or cluster lifecycle — not pod-level ops. Related: EKS desktop client, KubeSpade vs Lens, Kubernetes GUI.
Short answers for GKE desktop client searches.
Yes. Connect with GCP credentials or a kubeconfig from the desktop app. No KubeSpade account and no cloud proxy for API traffic.
No. Console for IAM / node pools / add-ons. KubeSpade for day-to-day Kubernetes API work on your laptop.
No KubeSpade backend receives your kubeconfig or tokens. Traffic goes from your machine to GCP / the cluster API. See Privacy.
Yes — Add Cluster with GCP credentials, or paste a kubeconfig that already uses your usual gcloud get-credentials / exec plugin setup.
Free for macOS, Windows, and Linux. No account required.