Skip to main content
radar (or kubectl radar when installed via Krew) starts the local server by default. Defaults come from ~/.radar/config.json when present - see Configuration files.

Commands

radar diagnose

radar cloud

cloud install supports --context, --namespace, --release, --chart-version, --name, --hub-url, --dry-run, --no-browser, and --browser. When adopting an existing installation, non-interactive runs require --adopt-existing; interactive runs can ask for consent. For an adopted installation, --enable-cloud-features adds optional Cloud feature RBAC. On any install, --no-self-upgrade omits the self-upgrade Role and RoleBinding. -y / --yes skips current-context confirmation but never grants adoption consent. cloud status accepts --context. Pass --namespace and --release together to inspect one exact installation instead of discovering visible installations.

General

Cluster connection

Timeline storage

Metrics & traffic

Feature toggles

Tuning for slow or large clusters

Clusters reached over high-latency tunnels, or with thousands of namespaces, can trip Radar’s default deadlines. Each flag also reads from the matching RADAR_* env var.

Authentication

See Authentication for the full setup. Common flags: Proxy mode (oauth2-proxy / Pomerium / etc.): OIDC mode (Google / Okta / Keycloak / etc.):

Radar Cloud

These flags wire an in-cluster Radar to a hosted Radar Cloud. Each is also readable from the matching RADAR_CLOUD_* env var (so secrets stay out of ps). Setting RADAR_CLOUD_MODE=true additionally forces --auth-mode=proxy and pins X-Forwarded-User / X-Forwarded-Groups so the in-cluster Radar impersonates the Cloud-authenticated user against the K8s API. Don’t set this for local installs.

Internal / development