Repository navigation
Troubleshooting
Danilo Carolino edited this page Oct 9, 2026
·
1 revision
KubeScope turns common kubectl failures into a short message with a hint. The
original text is always available: hover the message, or press Show details in
an error dialog.
| Message | What it means | What to do |
|---|---|---|
| Login tool not found | The kubeconfig runs a program (usually aws) that is not installed or not on the PATH
|
Install it, make sure it is on the PATH, then Refresh |
| Authentication failed | The credentials are missing or expired | Sign in again (for example aws sso login) and Refresh |
| Access denied | Your user cannot read that resource | Ask for a read-only role; see Connecting to clusters |
| Cluster unreachable | The API server did not answer | Check the network or VPN and that the cluster is running |
| Context not found | The context is not in your kubeconfig | Check ~/.kube/config or KUBECONFIG
|
| kubectl is missing | The bundled kubectl was not found |
Reinstall the app |
The cluster has no metrics-server, or your role cannot read metrics.k8s.io.
The other columns are unaffected.
The numbers add up only the Pods that have metrics. Pods that just started may not have reported yet.
The Flatpak only has the AWS CLI. If your kubeconfig uses another login tool, use
the .deb or the AppImage.
- Linux:
~/.config/kubescope/settings.json - Windows:
%APPDATA%\kubescope\settings.json - macOS:
~/Library/Application Support/kubescope/settings.json
Set KUBESCOPE_CONFIG_DIR to use another folder. Delete the file to reset
everything.
Open an issue with your version, platform and the error text. Remove cluster names, account IDs and tokens first. For security problems, follow the security policy instead.