glab-cluster

# glab cluster > Capture key `4dd0d32d1`: checksum-verified official macOS arm64 binary, source commit `4dd0d32d18361db6c1c668eb4ac691c0d6edf255`, archive SHA-256 `11980310aaad2bd9c4e75b5635a60e984da5d0e6245187f2cd6e8db0ec4c5a92`. Only adjacent marked help fences use this provenance; complete renderer output is preserved except trailing spaces/tabs. Other fences retain their stated prior provenance. ## Overview <!-- help-capture: 4dd0d32d1:ed5b0c665871 --> ```text Agents connect your cluster to GitLab, enabling pull-based deployments and secure access to the Kubernetes API. USAGE glab cluster <command> [command] [--flags] COMMANDS agent <command> [command] [--flags] Manage GitLab Agents for Kubernetes. graph [--flags] Query the Kubernetes object graph using the GitLab Agent for Kubernetes. (EXPERIMENTAL) FLAGS -h --help Show help for this command. -R --repo Select another repository. You can use either OWNER/REPO or GROUP/NAMESPACE/REPO. The full URL or Git URL is also accepted. ``` ## Quick start ```bash glab cluster --help ``` ## Structured output `glab cluster agent list` and `glab cluster agent token list` support `--output json` / `-F json` for structured output, which is useful for agent automation. ```bash # List cluster agents with JSON output glab cluster agent list --output json glab cluster agent list -F json # List agent tokens with JSON output glab cluster agent token list <agent-id> --output json glab cluster agent token list <agent-id> -F json ``` `glab cluster agent list` uses the API-reported total in its text header when available, separately from the current page's row count. JSON remains the requested page of agents. Traverse `--page` / `--per-page` explicitly; neither a page's JSON length nor missing total metadata proves there are no further results. This total change applies to the agent list, not the agent-token list. ## Subcommands See [references/commands.md](references/commands.md) for full `--help` output. ## Snap kubeconfig access The snap uses the manual-connect `dot-kube-config` plug, scoped to `~/.kube/config` and `~/.kube/config.lock`, rather than the whole `.kube` directory. A different kubeconfig path can remain inaccessible under confinement. Connecting the plug or updating kubeconfig changes local permissions/configuration and requires approval; do not treat CLI help as permission to connect it or modify a cluster.