Glauco

Troubleshooting

gke-gcloud-auth-plugin ENOENT: plugin not found

Glauco cannot run gke-gcloud-auth-plugin, aws, kubelogin or another exec plugin.

What you see

The main pane says Can't connect to cluster. The message names the context and the error, for example:

Glauco shows

gke-prod is unreachable. spawn gke-gcloud-auth-plugin ENOENT

ENOENT means Glauco could not find the program. Your kubeconfig asks Glauco to run an auth plugin, such as gke-gcloud-auth-plugin, aws, kubelogin or kubectl-oidc_login, and it is not on the PATH that Glauco sees.

Check that the plugin works

  1. Open a terminal.
  2. Find the plugin. Use the name from the error.
macOS, Linux
command -v gke-gcloud-auth-plugin
Windows (PowerShell)
Get-Command gke-gcloud-auth-plugin

If nothing is found, install the plugin:

  • GKE: gcloud components install gke-gcloud-auth-plugin
  • EKS: install the AWS CLI version 2, which provides aws.
  • AKS: az aks install-cli, which installs kubelogin.

Then run kubectl get namespaces in the terminal. If this fails too, fix your kubeconfig or sign in again first, for example with gcloud auth login or aws sso login.

Fix it on macOS and Linux

When it starts, Glauco runs your login shell once and copies its PATH. So the plugin's folder must be on the PATH of a new login shell, not only in one open terminal.

  1. Add the plugin's folder to PATH in your shell profile, for example ~/.zshrc, ~/.zprofile, ~/.bashrc or ~/.config/fish/config.fish.
  2. Check it in a new terminal: $SHELL -ilc 'command -v gke-gcloud-auth-plugin'.
  3. Quit Glauco completely.
  4. Open Glauco again.
Some plugins run another program. gke-gcloud-auth-plugin runs gcloud, so both folders must be on the PATH. If your shell takes more than 5 seconds to start, Glauco does not wait for it. Then make the profile faster, or put the full path to the plugin in the command field of your kubeconfig.

Fix it on Windows

  1. Open Edit the system environment variables from the Start menu.
  2. Click Environment Variables….
  3. Add the plugin's folder to Path under your user variables.
  4. Quit Glauco completely.
  5. Open Glauco again.

Other connection errors

If Glauco gets no answer in 8 seconds, it says the context isn't responding. Check your VPN or credentials, or pick another cluster from the switcher. Check that your VPN is on and that kubectl works, then click Retry.

Still stuck? Contact us.