Security and privacy
What Kubebay can reach, how the engine is protected on your machine, how it handles Secrets, and what it sends anywhere.
Your credentials
Kubebay uses your kubeconfig as kubectl does. It doesn’t copy your credentials, and never syncs them anywhere. Exec plugins such as aws eks get-token and gke-gcloud-auth-plugin run as they would in your terminal.
The desktop app is started by your OS, not a shell, so it reads a short list of variables from your login shell: PATH, KUBECONFIG, the AWS and Google Cloud profile and config variables, and proxy and CA settings. That way an exec plugin signs in as the same identity your terminal uses. Without AWS_PROFILE, for example, it would quietly fall back to the default profile. Nothing else from your environment is passed on.
The engine on your machine
- It listens on
127.0.0.1by default, and rejects requests whoseHostisn’t a loopback address. A web page you visit can’t reach it through DNS rebinding. - Every request needs this session’s token. The token is written to a file only you can read (mode 0600) and is never logged. It changes each time the engine starts. The desktop app passes it to its own window, so you never see it.
In a cluster
With the Helm chart and OIDC, users sign in with your identity provider. The engine then acts as that user, through Kubernetes impersonation, so the cluster’s own RBAC decides what each person can see and do. Kubebay never grants more than RBAC does.
Features that only make sense on your own machine are off in a cluster: the local terminal, extensions, AI assistants (MCP), AI triage and usage history.
Secrets
- Secret values aren’t loaded into tables. A Secret table shows names and metadata only.
- An environment variable from a Secret stays masked until you click to show it, and every reveal is recorded in the Audit Log.
- A Secret opened in its drawer shows its keys with the values hidden, and so does its
last-applied-configurationannotation, which would otherwise hold a second copy. Reveal values on the YAML tab loads them, and that is recorded in the Audit Log too. Until you reveal them, you can edit the Secret’s labels and other fields, but not its values. - The security checks that look for unused Secrets read only their names and metadata.
- AI features never see Secrets. MCP doesn’t list them, and triage masks credentials in the evidence before you send it.
What Kubebay sends, and where
| What | Where | When |
|---|---|---|
| Kubernetes API calls | Your clusters | While you use them |
| An update check | GitHub releases | Desktop app only: 30 s after launch, then daily. Turn it off in Settings |
| Image signature lookups | Each image’s registry, and Sigstore | Only when you run a signature check |
| Prometheus queries | Your Prometheus | When you set a URL |
| Triage evidence | The endpoint you set | Only when you click Send |
| Cloud cluster listings | Your aws, gcloud or az CLI |
Only when you click Find |
There’s no telemetry, no account and no licence server.
Releases
Every release asset is signed with cosign, keylessly, and has a GitHub build-provenance attestation. See Verify a download. Desktop updates install only after their signature checks out against the key built into the app.
Reporting a vulnerability
Use GitHub’s private Report a vulnerability. Please don’t open a public issue.