Frequently asked questions

No. Credentials stay on your device. The app talks directly to your Kubernetes API and cloud providers. There is no KubeSpade backend that receives your cluster secrets or API traffic. See the Privacy Policy and the Network section for what the app may contact (update check on GitHub — not your cluster).

Your clusters — Kubernetes API and cloud APIs you configure (EKS / GKE / AKS / kubeconfig). That traffic goes straight from your machine to those APIs. It does not go through a KubeSpade proxy.

Optional, not your cluster: Desktop can check api.github.com for newer releases. When you download builds, files come from GitHub Releases CDN. iPad purchases go through Apple StoreKit. Full list: Privacy · Network.

Every release ships SHA256SUMS.txt. On the Download → Verify your download section you get copy-paste commands for macOS (shasum + notarized builds), Windows (SHA256 + Authenticode), and Linux (sha256sum). Compare the hash to the matching line in the sums file before you install — especially for a tool that will hold cluster credentials.

macOS, Windows, Linux, and iPadOS. Desktop builds are on the Download page. The iPadOS app ships via the App Store — see the iPadOS page.

Desktop (macOS, Windows, Linux) is an Electron UI with a local Go backend that talks to your Kubernetes API. Credentials stay on your device — there is no KubeSpade cloud proxy for cluster traffic. The iPad app is a separate native iPadOS client.

Desktop — yes. Source is on github.com/kubespade/kubespade under Apache-2.0 (same repo as Releases and Issues). Tags through v1.5.0 published installers; source in the repo aligns with tags from the next Desktop release onward. The iPad app is a separate product and is not open source.

Amazon EKS, Google GKE, Azure AKS, minikube, kind, and any cluster you can reach with a standard kubeconfig. On desktop, exec plugins such as aws-vault are supported where configured.

Yes on Desktop (macOS, Windows, Linux). KubeSpade launches Claude Code, Gemini CLI, Codex CLI, GitHub Copilot, or Cursor Agent if they’re installed, with MCP tools for clusters you’ve already connected. Reads are free; apply and delete need Approve in the UI. The AI shell does not get a live kubeconfig. Details on the AI page.

It is a visual Kubernetes GUI for day-to-day cluster work — the same kind of tasks you’d do with kubectl, without living in the terminal. That includes Helm install, upgrade, history, and rollback on Desktop, a pod Files browser with pull/push, and Policy Map for NetworkPolicy allow rules. Keep kubectl for scripting and automation; use KubeSpade for browsing, debugging, and ops.

Yes on Desktop (macOS, Windows, Linux). Open Files from a pod to browse the container filesystem, search by name (including very large folders), then Pull or Push — or drag-and-drop into the current folder. Same idea as kubectl cp, without the terminal dance. On iPad this is not available yet.

Yes on Desktop (macOS, Windows, Linux): pick a local Helm repo or paste a chart URL, set values, install or upgrade, then use history and rollback. On iPad, Helm is read-oriented for now (list releases and inspect values); write lands later with Pro.

On Desktop, open Network → Policy Map to see NetworkPolicy ingress and egress allow rules as a graph between workloads. Click a node to pin its allowed peers. It shows policy intent, not live traffic. Not on iPad yet.

No cloud backend for your cluster data. Metrics and logs you view are fetched from your cluster (or local history on device) — not uploaded to KubeSpade servers.

Open an issue on GitHub. Include platform, OS version, app version, and cluster type (EKS / GKE / AKS / kubeconfig). Do not paste kubeconfigs, tokens, or secrets.

From the Download page or GitHub Releases. Latest desktop builds are v1.5.0 (macOS, Windows, Linux). After download, verify the checksum with SHA256SUMS.txt. The iPadOS App Store listing is still coming soon.