No clusters found: no contexts in your kubeconfig

• The context chip says No context and No cluster.
• The Dashboard says No cluster selected.
• The cluster switcher says No clusters found.

The switcher also says No clusters found when your search matches nothing. Clear the search box first.

Glauco shows no clusters when it finds no contexts. Check these in turn:

1. Run kubectl config get-contexts in a terminal. If it lists nothing, your kubeconfig has no contexts. Add one with your cloud's CLI, for example gcloud container clusters get-credentials, aws eks update-kubeconfig or az aks get-credentials.
2. Check where the file is. Without KUBECONFIG, Glauco reads ~/.kube/config, or %USERPROFILE%\.kube\config on Windows.
3. If you set KUBECONFIG in your shell profile, Glauco does not see it when you open it from the Dock, Finder or an app menu. Add the files with Add configuration… instead. See Add a kubeconfig file.
4. Check that the file is valid YAML. Glauco treats a file it cannot read as empty. Run kubectl config view to see the error.

When you fix the main kubeconfig file, Glauco reloads it. You do not need to restart.