First launch

Glauco reads the same kubeconfig files as kubectl. It needs no setup and no account.

• If the KUBECONFIG environment variable is set, Glauco reads every file in it. Separate the paths with : on macOS and Linux, and with ; on Windows. If two files define the same name, the first file wins.
• If KUBECONFIG is not set, Glauco reads ~/.kube/config. On Windows that is %USERPROFILE%\.kube\config.
• Files you add with Add configuration… come after these. See Connect to and switch clusters.

Glauco never writes to your kubeconfig. When you switch context in Glauco, the current-context in your file stays the same. When the file changes, Glauco reloads your contexts.

Many clusters sign in through a program in the kubeconfig, such as gke-gcloud-auth-plugin, aws, kubelogin or oidc-login. Glauco runs that program the same way kubectl does, so it must be on your PATH.

• On macOS and Linux, Glauco asks your login shell for its PATH when it starts. It runs $SHELL once as a login shell, takes the PATH, and puts it in front of its own. So Homebrew, the gcloud SDK, mise or asdf shims work when your shell profile adds them.
• If $SHELL is not set, Glauco uses /bin/zsh on macOS and /bin/bash on Linux. If the shell takes more than 5 seconds, Glauco keeps its own PATH.
• On Windows, Glauco uses the PATH from your Windows environment variables.
• If you change your PATH, quit and open Glauco again.

If a cluster does not connect, see Auth plugin not found.

1. Glauco connects to the current context of your kubeconfig.
2. The Dashboard opens. The context name is at the top of the sidebar.
3. A banner says when your trial ends, for example Your Glauco trial ends in 14 days.

The trial starts on the first launch and lasts 14 days. You need no key, account or card. Press ⌘K on macOS, or CtrlK on Windows and Linux to open the command palette and go anywhere.