Skip to content
Back to search

radar

The missing open-source Kubernetes UI with a built-in MCP server for AI agents. See what's broken, why, and what changed. Issues, Topology, event timeline, Helm, GitOps, live service traffic, and cluster audits - all in one Go binary.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/skyhook-io/radar with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/skyhook-io/radar'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/skyhook-io--radar/badge.svg)](/listings/skyhook-io--radar)

HTML

<a href="/listings/skyhook-io--radar"><img src="/api/listings/skyhook-io--radar/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

These steps run a script from the network that findsafeskills does not scan.

**Quick Install:**

curl -fsSL https://get.radarhq.io | sh

**Homebrew:**

brew install kubectl-radar

Also available from our tap: `brew install skyhook-io/tap/radar`.

Then run: `kubectl radar`. Quick install, PowerShell, Homebrew, and Scoop also set up the `radar` shorthand. Krew and direct downloads use `kubectl radar` unless you add your own `radar` symlink.

<details> <summary><b>More install options</b> — Desktop App (macOS/Linux/Windows), Krew, Scoop, In-Cluster Helm</summary>

CLI

**Krew (kubectl plugin manager):**

kubectl krew install radar

**Scoop (Windows):**

scoop bucket add skyhook https://github.com/skyhook-io/scoop-bucket
scoop install radar

**PowerShell (Windows):**

irm https://get.radarhq.io/install.ps1 | iex

**Custom install location (macOS/Linux):**

curl -fsSL https://get.radarhq.io | INSTALL_DIR="$HOME/.local/bin" sh

Quick install writes to `/usr/local/bin` unless `INSTALL_DIR` says otherwise. The directory is created if missing, and needs to be on your `PATH` for `radar` and `kubectl radar` to resolve.

**Direct download** — [GitHub Releases](https://github.com/skyhook-io/radar/releases) for macOS, Linux, or Windows.

Desktop App

Native desktop app — no terminal needed.

**Homebrew (macOS):**

brew install --cask skyhook-io/tap/radar-desktop

**Debian/Ubuntu** — download the `.deb` from [GitHub Releases](https://github.com/skyhook-io/radar/releases), then:

sudo apt install ./radar-desktop_*.deb

**Fedora/RHEL** — download the `.rpm` from [GitHub Releases](https://github.com/skyhook-io/radar/releases), then:

sudo rpm -i radar-desktop_*.rpm

**Scoop (Windows):**

scoop bucket add skyhook https://github.com/skyhook-io/scoop-bucket
scoop install radar-desktop

**Windows (direct download)** — [GitHub Releases](https://github.com/skyhook-io/radar/releases).

In-Cluster Deployment

Deploy to your cluster for shared team access:

helm repo add skyhook https://skyhook-io.github.io/helm-charts
helm install radar skyhook/radar -n radar --create-namespace

See the [In-Cluster Deployment Guide](docs/in-cluster.md) for Gateway API and ingress exposure, authentication, and RBAC configuration.

</details>

---

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 596 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # Radar
  2. **The missing open-source Kubernetes UI, with a built-in MCP server for your AI agent.**
  3. <br>Single binary. No account required. Free forever.
  4. 🌐 **[radarhq.io](https://radarhq.io)** · [Docs](https://radarhq.io/docs) · [Benchmarks](https://radarhq.io/benchmark) · [Releases](https://github.com/skyhook-io/radar/releases) · [Slack](https://radarhq.io/slack)
  5. Radar shows you what's broken in a Kubernetes cluster, why, and what changed: issues, topology, a timeline of events and resource changes, Helm, GitOps, traffic, audit, and upgrade impact. Your AI agent reads the same cluster data and relationships through Radar's MCP server, and Radar can run an AI investigation for you with the agent CLI you already use. It runs on your laptop as a `kubectl` plugin or desktop app, or in-cluster with Helm.
  6. <a href="https://www.producthunt.com/products/radar-7?embed=true&utm_source=badge-top-post-badge&utm_medium=badge&utm_campaign=badge-radar-42edb7b0-e388-4fa8-9ba5-4876c2c0d638" target="_blank"><img src="https://api.producthunt.com/widgets/embed-image/v1/top-post-badge.svg?post_id=1130618&theme=neutral&period=daily" alt="Radar - The missing open-source Kubernetes UI | Product Hunt" width="250" height="54" /></a>
  7. [![CI](https://github.com/skyhook-io/radar/actions/workflows/ci.yml/badge.svg)](https://github.com/skyhook-io/radar/actions/workflows/ci.yml)
  8. [![CodeQL](https://github.com/skyhook-io/radar/actions/workflows/codeql.yml/badge.svg)](https://github.com/skyhook-io/radar/actions/workflows/codeql.yml)
  9. [![Release](https://img.shields.io/github/v/release/skyhook-io/radar?logo=github)](https://github.com/skyhook-io/radar/releases/latest)
  10. [![Downloads](https://img.shields.io/github/downloads/skyhook-io/radar/total?logo=github)](https://github.com/skyhook-io/radar/releases)
  11. [![Helm repo downloads](https://img.shields.io/github/downloads/skyhook-io/helm-charts/total?logo=helm&label=Helm%20repo%20downloads)](https://artifacthub.io/packages/helm/skyhook/radar)
  12. [![Slack](https://img.shields.io/badge/Slack-Join%20the%20community-4A154B?logo=slack&logoColor=white)](https://radarhq.io/slack)
  13. [![License](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](LICENSE)
  14. <details>
  15. <summary><b>Table of contents</b></summary>
  16. - [Why Radar?](#why-radar) · [Debugging in the UI](#debugging-in-the-ui)
  17. - [AI agents: MCP server and AI investigations](#ai-agents-mcp-server-and-ai-investigations) — Connect your agent · AI investigations · Benchmarks
  18. - [Installation](#installation)
  19. - [Usage](#usage)
  20. - [Views](#views) — Issues · Topology · Resources · Image Filesystem · Timeline · Helm · Compare · TLS · GitOps · Traffic · Metrics · Capacity · Cost · Audit · Network path · Upgrade impact · RBAC · Auth
  21. - [Supported Resources & Integrations](#supported-resources--integrations)
  22. - [Keyboard Shortcuts](#keyboard-shortcuts)
  23. - [Security](#security)
  24. - [Community and support](#community-and-support)
  25. - [Development](#development) · [Contributing](#contributing)
  26. </details>
  27. <p align="center">
  28. <img src="docs/screenshot.png" alt="Radar home view for one cluster: pod, deployment and node health, resource utilization, topology, Helm releases, timeline, traffic, and unhealthy workloads" width="800">
  29. </p>
  30. **Install and run in 30 seconds:**
  31. ```bash
  32. curl -fsSL https://get.radarhq.io | sh && kubectl radar
  33. ```
  34. Or `brew install kubectl-radar`. [Windows, Krew, desktop app and Helm ↓](#installation)
  35. **Then, with Radar running, connect your AI agent** (read-only):
  36. ```bash
  37. claude mcp add --transport http radar http://localhost:9280/mcp-readonly
  38. ```
  39. [Codex, Cursor, GitHub Copilot, other clients, and the desktop app ↓](#connect-your-agent)
  40. ## Why Radar?
  41. - **Nothing to install in your cluster** — a single binary on your laptop that talks to the Kubernetes API with your kubeconfig. No agents, no CRDs, no dependencies
  42. - **Fast on big clusters** — tested on tens of thousands of pods; watches the cluster through informers and pushes live updates to the browser over SSE
  43. - **Private by design** — your cluster data stays on your machine. No account, no agents, no cloud sync. Usage reporting is off unless you opt in, and then sends only anonymous usage counts and coarse cluster facts: Kubernetes version, platform, node-count range, known integrations ([what Radar sends](docs/configuration.md#what-radar-sends)). An AI agent you connect sends what it reads to its own model provider
  44. - **Airgapped-friendly** — runs as a single binary against the Kubernetes API and works in locked-down environments with outbound egress blocked
  45. - **Works everywhere** — GKE, EKS, AKS, minikube, kind, k3s, or any conformant cluster
  46. - **One model of the cluster, for you and your agent** — the UI, the [MCP server](#ai-agents-mcp-server-and-ai-investigations), and AI investigations read the same live data: relationships, health, events, and changes
  47. - **Ready for teams** — deploy in-cluster with Helm for shared access, with SSO (OIDC or an auth proxy) and per-user Kubernetes RBAC in the open-source build
  48. > "Have Radar deployed at work. As far as Kubernetes dashboards go, this is one of the best." — u/TheRealNetroxen
  49. ---
  50. ## Debugging in the UI
  51. Start from **[Issues](#issues)**, a ranked queue of what's broken right now. Open a failing resource to see it in context: its owners, Pods, Services, and config on the **[Topology](#topology)**, what changed and when on the **[Timeline](#timeline)** (with diffs), and its events, logs, and YAML in the detail drawer. **[Helm](#helm)**, **[GitOps](#gitops)**, and **[Traffic](#traffic)** cover how it got deployed and who talks to it. When you want help, **Investigate** hands the same evidence to your agent ([AI investigations](#ai-investigations)). Radar records resource changes while it watches the cluster; history is in memory by default, and `--timeline-storage=sqlite` or `postgres` keeps it across restarts.
  52. <p align="center">
  53. <img src="docs/screenshots/issues-view.png" alt="Radar's Issues queue in the shop namespace with two warnings: a crash loop on the checkout Deployment, and the orders-db-legacy Service, whose selector matches no pods. Each row has an Investigate button." width="800">
  54. <br><em>Issues for the incident the agent diagnoses below: a crash loop on checkout and a Service with no endpoints</em>
  55. </p>
  56. ---
  57. ## AI agents: MCP server and AI investigations
  58. Pointed at raw `kubectl`, an agent spends its context window on YAML and its time on round trips. Radar's built-in [Model Context Protocol](https://modelcontextprotocol.io) (MCP) server gives it what Radar already knows instead: how resources connect, what is unhealthy, deduplicated events, recent changes with diffs, and filtered logs. In our benchmarks, the same agent and model reached a diagnosis about 3× faster through Radar than through kubectl ([details](#benchmarks)).
  59. <p align="center">
  60. <img src="docs/screenshots/mcp-claude-code.png" alt="Claude Code connected to Radar's read-only MCP endpoint, asked why the last checkout rollout failed. It calls diagnose, get_changes, list_resources and get_resource, then answers: the rollout changed DB_HOST to orders-db-legacy, a Service with no pods behind it, so the new pod crash-loops while the two old pods keep serving." width="800">
  61. <br><em>Claude Code on Radar's read-only endpoint, finding why a rollout failed (replay of a real session)</em>
  62. </p>
  63. <a id="ai-integration-mcp"></a>
  64. ### Connect your agent
  65. MCP is on by default and served on the same port as the UI: `9280` unless you set `--port`. The desktop app picks its own port: copy the URL from Radar's MCP dialog and change the final `/mcp` to `/mcp-readonly`. Start with the read-only endpoint:
  66. ```bash
  67. # Claude Code
  68. claude mcp add --transport http radar http://localhost:9280/mcp-readonly
  69. # Codex
  70. codex mcp add radar --url http://localhost:9280/mcp-readonly
  71. ```
  72. Setup for Cursor, VS Code (GitHub Copilot), Copilot CLI, OpenCode, Google Antigravity, Kiro, JetBrains, Cline, Devin, Claude Desktop, Zed, Gemini CLI, and any other MCP client is in the **[MCP guide](docs/mcp.md#setup-instructions)**. Its examples use `/mcp`; use `/mcp-readonly` instead to keep Radar's tools read-only. Your agent's other tools follow its own configuration.
  73. - **Context, not raw YAML** — topology, health assessments, events, changes, and logs, minified so they don't burn the context window. The [tools](docs/mcp.md#available-tools) cover resources and topology, issues, events and changes, logs, Helm, audit, upgrade readiness, RBAC, cost, and Prometheus
  74. - **You pick the endpoint** — `/mcp-readonly` has no write tools. The full `/mcp` endpoint, also on by default, adds write tools (restart, scale, apply, rollback, GitOps sync, node drain) marked destructive so clients can ask before running them. On `/mcp`, `diagnose` can also run an in-cluster reachability probe that creates short-lived pods. Calls use Radar's Kubernetes access: your kubeconfig locally, or each user's own RBAC when authentication is on. `--mcp-read-only` turns `/mcp` off (and with it, applying a fix from an AI investigation); `--no-mcp` turns MCP and AI investigations off. Neither blocks ordinary UI writes
  75. - **Secret values are withheld** — Secret reads never include `.data` or `.stringData`. Environment variables, Helm values, and logs are scrubbed for known secret patterns, which can't catch everything, and the opt-in `exec_pod` tool returns raw command output. See [MCP security](docs/mcp.md#security)
  76. ### AI investigations
  77. Radar can also run the investigation for you, with the agent CLI you already have — Claude Code, Codex, Cursor, or OpenCode — on your machine and signed in with your own account. Radar needs no API key of its own. Start one from a resource's **Investigate** action, from an issue, by describing what you're seeing on the AI investigations page (where to start, since when, and optionally the resource it's about), or from a terminal against a running Radar:
  78. ```bash
  79. radar diagnose deploy/checkout -n shop
  80. radar diagnose deploy/checkout -n shop --json > conclusion.json
  81. ```
  82. Every investigation ends on the same Findings page, with the evidence behind each claim. Radar's investigation tools can only read the cluster, and Radar applies a fix only when you approve it, from an investigation of the resource it changes. What else the agent can do depends on how Radar runs it. **Radar safeguards** (Claude Code and Codex) shuts off the agent's other MCP servers and its ability to write. **Your agent setup** (the only option for Cursor and OpenCode) runs the agent with its normal configuration, tools, and MCP servers, which Radar cannot constrain and which may be able to change your cluster. Cursor and OpenCode approve tool requests automatically in these runs, without asking you. See [agents and isolation](https://radarhq.io/docs/features/diagnose#agents-and-isolation).
  83. Investigations need a supported agent CLI on the machine running Radar, MCP on, and authentication off. In-cluster installs don't run them. See the [AI investigations guide](https://radarhq.io/docs/features/diagnose) and [agent CLI setup](docs/configuration.md#ai-investigations-agent-cli).
  84. ### Benchmarks
  85. Three studies of an AI agent diagnosing live faults from [SREGym](https://github.com/SREGym/SREGym) (Microsoft and UIUC) on a 3-node EKS cluster, with the same judge scoring every tool. Times are averages to a submitted answer, right or wrong. These are our own benchmarks; compare numbers within a study, not across studies.
  86. | Study | Faults | Result |
  87. |-------|--------|--------|
  88. | [Radar MCP vs raw kubectl](https://radarhq.io/benchmark/mcp-vs-kubectl) — same agent and model | 50 | 64s vs 191s to a diagnosis (about 3× faster); 86% vs 60% diagnosed correctly within two minutes |
  89. | [Kubernetes MCP servers](https://radarhq.io/benchmark/kubernetes-mcp-servers) — Radar, containers/kubernetes-mcp-server, Flux159/mcp-server-kubernetes, Amazon EKS MCP Server, k8sgpt, raw kubectl | 25 | Radar took 57s, 2.3× faster than the next-fastest MCP server; on the 14 faults every tool got right, 33s vs 58s for the next-fastest |
  90. | [AI SRE tools](https://radarhq.io/benchmark/ai-sre-tools) — Claude Code + Radar MCP vs kubectl-ai, HolmesGPT, OpenSRE, kagent, AWS DevOps Agent | 50 | Claude Code + Radar MCP was the most accurate (44/50 correct), fastest (79s), and cheapest ($0.27 a fault) |
  91. Per-scenario scores and timings are downloadable from the [benchmark pages](https://radarhq.io/benchmark); the AI SRE study also includes costs.
  92. ---
  93. ## Installation
  94. **Quick Install:**
  95. ```bash
  96. curl -fsSL https://get.radarhq.io | sh
  97. ```
  98. **Homebrew:**
  99. ```bash
  100. brew install kubectl-radar
  101. ```
  102. Also available from our tap: `brew install skyhook-io/tap/radar`.
  103. Then run: `kubectl radar`. Quick install, PowerShell, Homebrew, and Scoop also set up the `radar` shorthand. Krew and direct downloads use `kubectl radar` unless you add your own `radar` symlink.
  104. <details>
  105. <summary><b>More install options</b> — Desktop App (macOS/Linux/Windows), Krew, Scoop, In-Cluster Helm</summary>
  106. #### CLI
  107. **Krew (kubectl plugin manager):**
  108. ```bash
  109. kubectl krew install radar
  110. ```
  111. **Scoop (Windows):**
  112. ```powershell
  113. scoop bucket add skyhook https://github.com/skyhook-io/scoop-bucket
  114. scoop install radar
  115. ```
  116. **PowerShell (Windows):**
  117. ```powershell
  118. irm https://get.radarhq.io/install.ps1 | iex
  119. ```
  120. **Custom install location (macOS/Linux):**
  121. ```bash
  122. curl -fsSL https://get.radarhq.io | INSTALL_DIR="$HOME/.local/bin" sh
  123. ```
  124. Quick install writes to `/usr/local/bin` unless `INSTALL_DIR` says otherwise. The directory is created if missing, and needs to be on your `PATH` for `radar` and `kubectl radar` to resolve.
  125. **Direct download** — [GitHub Releases](https://github.com/skyhook-io/radar/releases) for macOS, Linux, or Windows.
  126. #### Desktop App
  127. Native desktop app — no terminal needed.
  128. **Homebrew (macOS):**
  129. ```bash
  130. brew install --cask skyhook-io/tap/radar-desktop
  131. ```
  132. **Debian/Ubuntu** — download the `.deb` from [GitHub Releases](https://github.com/skyhook-io/radar/releases), then:
  133. ```bash
  134. sudo apt install ./radar-desktop_*.deb
  135. ```
  136. **Fedora/RHEL** — download the `.rpm` from [GitHub Releases](https://github.com/skyhook-io/radar/releases), then:
  137. ```bash
  138. sudo dnf install ./radar-desktop_*.rpm
  139. ```
  140. **Linux (AppImage, any distro)** — download the `.AppImage` from [GitHub Releases](https://github.com/skyhook-io/radar/releases), then:
  141. ```bash
  142. chmod +x radar-desktop_*_linux_amd64.AppImage
  143. ./radar-desktop_*_linux_amd64.AppImage
  144. ```
  145. The AppImage doesn't update itself. When a new version is out, Radar links to the download.
  146. If the Linux desktop app flashes black, shows black icons or crashes on NVIDIA, see [Linux desktop rendering](docs/configuration.md#linux-desktop-rendering).
  147. Kubeconfig login plugins (`exec`) run from inside the AppImage, not from the folder you started it in. If a plugin's `args` name a file by a relative path, such as `--token-file token.json`, the plugin can't find it and Radar shows "Authentication Failed". Give the full path instead, such as `--token-file /home/you/.kube/token.json`. A relative `command`, such as `./token.sh`, works: it's looked up next to the kubeconfig file.
  148. **Scoop (Windows):**
  149. ```powershell
  150. scoop bucket add skyhook https://github.com/skyhook-io/scoop-bucket
  151. scoop install radar-desktop
  152. ```
  153. **Windows (direct download)** — [GitHub Releases](https://github.com/skyhook-io/radar/releases).
  154. #### In-Cluster Deployment
  155. Deploy to your cluster for shared team access:
  156. ```bash
  157. helm repo add skyhook https://skyhook-io.github.io/helm-charts
  158. helm install radar skyhook/radar -n radar --create-namespace
  159. ```
  160. See the [In-Cluster Deployment Guide](docs/in-cluster.md) for Gateway API and ingress exposure, authentication, and RBAC configuration.
  161. </details>
  162. ---
  163. ## Usage
  164. ```bash
  165. # Opens browser automatically
  166. kubectl radar
  167. # Quick install, PowerShell, Homebrew, and Scoop also set up the bare command
  168. radar
  169. ```
  170. **Common flags**
  171. | Flag | Default | Description |
  172. |------|---------|-------------|
  173. | `--kubeconfig` | `~/.kube/config` | Path to primary kubeconfig file |
  174. | `--namespace` | (context namespace) | Initial namespace filter (supports multi-select in the UI; also used as RBAC fallback for namespace-scoped users). Unset, Radar uses your saved pick, then the kubeconfig context's namespace, then all namespaces |
  175. | `--port` | `9280` | Server port |
  176. | `--listen-address` | `127.0.0.1` | HTTP listen IP address (IPv4 or IPv6), or `localhost`. Bind a specific local IP or use `0.0.0.0` for all interfaces. Non-loopback access needs authentication and network controls. |
  177. | `--no-browser` | `false` | Don't auto-open browser |
  178. | `--timeline-storage` | `memory` | Timeline storage backend: `memory`, `sqlite`, or `postgres` |
  179. | `--disable-exec` | `false` | Disable pod terminal, debug shells, pod file browsing, CloudNativePG sessions and MCP `exec_pod` |
  180. | `--auth-mode` | `none` | Authentication mode: `none`, `proxy`, or `oidc` ([details](docs/authentication.md)) |
  181. | `--no-mcp` | `false` | Disable all MCP endpoints |
  182. | `--mcp-read-only` | `false` | Expose only read-only MCP tools; disable `/mcp` (env: `RADAR_MCP_READ_ONLY`) |
  183. <a id="tuning-for-slow-or-high-latency-clusters"></a>The [Configuration Guide](docs/configuration.md#cli-flags) describes every startup flag in the table above and 27 more, plus tuning for slow or high-latency clusters, kubeconfig precedence, and context switching.
  184. <details>
  185. <summary>The other 27 flags</summary>
  186. `--kubeconfig-dir`, `--namespaces`, `--namespace-scope`, `--base-path`, `--allowed-hosts`, `--trusted-origins`, `--browser`, `--timeline-db`, `--timeline-max-size`, `--history-limit`, `--disable-helm-write`, `--disable-local-terminal`, `--debug-image`, `--list-page-size`, `--context-switch-timeout`, `--first-paint-backstop`, `--namespace-list-timeout`, `--max-scope-candidates`, `--prometheus-url`, `--prometheus-single-cluster`, `--prometheus-cluster-label`, `--prometheus-header`, `--prometheus-header-from-env`, `--beyla-job-selector`, `--opencost-currency`, `--mcp-catalog-stdio`, `--version`
  187. </details>
  188. `radar --help` is authoritative for the installed version. `radar cloud status` inspects an in-cluster Radar Cloud installation without changing it ([details](docs/configuration.md#radar-cloud)).
  189. ---
  190. ## Views
  191. ### Issues
  192. One ranked queue of what's broken right now — crash loops, image pull failures, stuck rollouts, pods that can't be scheduled, dangling references, and failing Argo CD / Flux conditions — each with an **Investigate** action. See [Issues](https://radarhq.io/docs/features/issues).
  193. ### Topology
  194. Interactive graph showing how your Kubernetes resources are connected in real-time.
  195. <p align="center">
  196. <img src="docs/screenshots/topology-view.png" alt="Topology View" width="800">
  197. <br><em>Topology View — Visualize resource relationships</em>
  198. </p>
  199. - Two modes: **Resources** (full hierarchy) and **Traffic** (network flow path)
  200. - Group by namespace, app label, or view ungrouped
  201. - Filter by resource kind — click any node for full details
  202. - Auto-layout powered by ELK.js, live updates via SSE
  203. ### Resources
  204. Table-based resource browser with smart columns per resource kind.
  205. <p align="center">
  206. <img src="docs/screenshots/resources-view.png" alt="Resources View" width="800">
  207. <br><em>Resources View — Browse and filter all cluster resources</em>
  208. </p>
  209. - Browse all resource types including CRDs
  210. - Inspect CRD definitions, versions, instances, and searchable schemas
  211. - Search by name, filter by status or problems (CrashLoopBackOff, ImagePullBackOff, etc.)
  212. - Add custom columns from any label or annotation — sortable, filterable, and resizable
  213. - Click any resource for YAML manifest, related resources, logs, and events
  214. - Pod logs list init containers, marked `(init)`, and open on the init container a Pod is stuck on, so a Pod that never starts still shows why
  215. - Set regular or init-container images on Deployments, StatefulSets, DaemonSets, and Argo Rollouts, with live rollout progress in tables, drawers, workload views, and Applications
  216. ### Image Filesystem Viewer
  217. Inspect container image filesystems directly from the Pod view — no need to pull images locally or exec into containers.
  218. <p align="center">
  219. <img src="docs/screenshots/image-filesystem-viewer.png" alt="Image Filesystem Viewer" width="800">
  220. <br><em>Image Filesystem Viewer — Browse container image contents</em>
  221. </p>
  222. - Browse, search, and download files from any container image in a Pod
  223. - Works with public images (Docker Hub, Quay, GHCR) and private registries (GCR, ECR, ACR) using your cluster's ImagePullSecrets
  224. See [Image filesystem](https://radarhq.io/docs/features/image-filesystem).
  225. ### Timeline
  226. Unified timeline of Kubernetes events and resource changes.
  227. <p align="center">
  228. <img src="docs/screenshots/timeline-view.png" alt="Timeline View" width="800">
  229. <br><em>Timeline View — Track cluster activity in real-time</em>
  230. </p>
  231. - Filter by event type (all or warnings only)
  232. - Resource change diffs showing what changed (replicas, images, etc.)
  233. - Real-time updates as new events occur
  234. ### Helm
  235. Manage Helm releases deployed in your cluster — inspect values and rendered manifests, diff revisions, see why an upgrade or hook failed, then upgrade, roll back, or uninstall. Radar tracks available chart upgrades from your configured repos or your own OCI registries. See [Helm Support](docs/helm.md) for the detailed behavior and limits.
  236. <p align="center">
  237. <img src="docs/screenshots/helm-view.png" alt="Helm View" width="800">
  238. <br><em>Helm View — Manage your Helm deployments</em>
  239. </p>
  240. ### Compare Resources
  241. Diff any two Kubernetes resources of the same kind side-by-side — like comparing a staging Deployment to its production sibling, or two pods that should be identical but aren't. Server-assigned noise (`managedFields`, `resourceVersion`, last-applied) is stripped, and diff-only and spec-only modes cut the rest. See [Compare](https://radarhq.io/docs/features/compare).
  242. <p align="center">
  243. <img src="docs/screenshots/compare-view.png" alt="Compare View" width="800">
  244. <br><em>Compare View — Side-by-side YAML diff with field-level highlighting</em>
  245. </p>
  246. ### TLS Certificate Management
  247. View TLS certificate details and expiry dates across all namespaces — catch expiring certificates before they cause outages.
  248. - Parses TLS secrets to show certificate subject, issuer, and validity period
  249. - Dashboard-level certificate expiry overview
  250. - Available from the resource detail view for any TLS-type Secret
  251. ### GitOps
  252. Monitor, diagnose, and manage FluxCD and ArgoCD resources in one place.
  253. <p align="center">
  254. <img src="docs/screenshots/gitops-view.png" alt="GitOps fleet view" width="800">
  255. <br><em>GitOps fleet view — Argo + Flux applications side-by-side with sync, health, source, destination, and lifecycle state</em>
  256. </p>
  257. - Fleet view + per-app detail page for **ArgoCD** (`Application`, `ApplicationSet`, `AppProject`) and **FluxCD** (`GitRepository`, `OCIRepository`, `HelmRepository`, `Bucket`, `Kustomization`, `HelmRelease`, `Alert`)
  258. - **Diagnosis** — field-level drift, recent events per resource, stuck-drift-loop detection, parsed operation failures, one-click remediation
  259. - Sync, suspend, resume, reconcile, and rollback from the UI or through MCP
  260. See the [GitOps guide](docs/gitops.md) for the full feature matrix, RBAC requirements, demo cluster, and single-cluster scope notes.
  261. ### Traffic
  262. Visualize live network traffic between services using Hubble, Caretta, Istio, or Beyla.
  263. <p align="center">
  264. <img src="docs/screenshots/traffic-view.png" alt="Traffic View" width="800">
  265. <br><em>Traffic View — See how services communicate in real-time</em>
  266. </p>
  267. - Auto-detects Hubble (Cilium), Istio, Caretta, or Grafana Beyla as traffic data sources, with a setup wizard to install one if none is detected
  268. - Beyla needs its `network` feature enabled, and per-port edges additionally need `dst.port` and `transport` named in `attributes.select` — both are off by default, and Radar says so in the Traffic view rather than showing partial edges silently
  269. - Animated flow graph showing requests per second between services, filterable by namespace, protocol, or status code
  270. - Focus on a workload to see only it and what it talks to; the focus is in the URL, so it can be shared
  271. See [Traffic](https://radarhq.io/docs/features/traffic) for source-specific requirements and large-cluster behavior.
  272. ### Workload Metrics
  273. Open a Deployment, StatefulSet or DaemonSet's **Metrics** tab to investigate
  274. request rate, HTTP errors, latency, CPU, memory and throttling. Radar reads an
  275. existing Prometheus-compatible backend; resource charts do not require HTTP
  276. instrumentation, and request charts use supported Beyla or Istio observations.
  277. See [Workload metrics](docs/workload-metrics.md) for screenshots, prerequisites,
  278. supported configurations and local multi-cluster setup limitations.
  279. ### Capacity (Karpenter)
  280. Read-only diagnosis for Karpenter-managed fleets — why is my pod pending, which NodePool could take it, why aren't my nodes joining, what is disruption doing to my fleet? Appears automatically when Karpenter NodePools are detected (RBAC-gated). Overview, NodePool detail, Demand, and Activity screens; every quantity carries its certainty (`= ≥ ≤ ?`), so unavailable is never shown as zero. See [docs/capacity.md](docs/capacity.md).
  281. ### Cost Insights
  282. Track Kubernetes spending from OpenCost metrics in a PromQL-compatible backend or a Kubecost 3 Aggregator: allocated workload cost, namespace and workload breakdowns with efficiency scoring, node costs, and trends when Prometheus history is available. Appears automatically when compatible data is detected. See [Cost](https://radarhq.io/docs/features/cost).
  283. ### Cluster Audit
  284. Proactive best-practices scanner with 48 checks across security, reliability, and efficiency — inspired by Polaris, Kubescape, Trivy, and NSA/CISA guidelines. Runs instantly against cached data with zero cluster-side installation.
  285. - Security: privileged containers, privilege escalation, host namespaces, runtime socket mounts, secrets in ConfigMaps, and more
  286. - Reliability: missing probes, image tag `latest`, single-replica deployments, missing PDB/topology spread, deprecated API versions, CloudNativePG clusters with no backup destination, no WAL archiving, a single instance or the deprecated in-tree Barman backup
  287. - Efficiency: missing requests and limits, orphan ConfigMaps/Secrets, PVCs with no consumer observed, long-Pending PVCs, and Released or Failed PVs
  288. - Remediation guidance per finding, NSA/CISA and CIS framework labels, and per-resource opt-out via the `radarhq.io/ignore-checks` annotation
  289. See [Cluster audit](https://radarhq.io/docs/features/cluster-audit) and [audit configuration](docs/configuration.md#per-resource-check-suppression).
  290. ### Network Path Diagnose
  291. Hop-ordered diagnosis for Service, Ingress, HTTPRoute, GRPCRoute, and Gateway — answering "if traffic is sent toward this resource, does it reach a healthy process, and if not which hop breaks first?" It names the first broken hop with a kubectl reproducer, predicts NetworkPolicy blocks, and can run an optional DNS / TCP / TLS / HTTP probe from your laptop or in-cluster. Open the **Reachability** tab on the resource; see [docs/reachability.md](docs/reachability.md).
  292. ### Kubernetes Upgrade Impact
  293. Open **Checks → Upgrade impact** before upgrading the control plane. Radar compares the current cluster with a target Kubernetes minor and orders evidenced compatibility, health, admission, drain, runtime, and configuration checks by required action — APIs removed in the target release, kubelet and kube-proxy skew, overlapping PodDisruptionBudgets, removed feature gates — using live resources, Helm release manifests, last-applied configuration, and API server metrics. On k3s and RKE2 it also lists the system-upgrade-controller Plans that upgrade the distribution, with their version and state.
  294. See the [Kubernetes upgrade impact guide](https://radarhq.io/docs/features/upgrade-impact) for the check catalog, coverage semantics, and RBAC notes.
  295. ### Vulnerabilities in Deployed Images
  296. With [Trivy Operator](https://aquasecurity.github.io/trivy-operator/) installed, **Checks → Vulnerabilities** rolls its VulnerabilityReports up to the images that run now: which images carry Critical and High CVEs, which have a fix, and which workloads and namespaces run them, by image, by CVE or by workload. **By fix** turns the fixable findings into a list of package upgrades: each row says what to upgrade to and every CVE that clears. Reports about older revisions are left out, an image used by many workloads is one row, and running images without a report are listed as not scanned rather than clean. The tab appears only when the cluster serves Trivy's VulnerabilityReport kind. See [Trivy Operator](docs/integrations.md#trivy-operator).
  297. <p align="center">
  298. <img src="docs/screenshots/vulnerabilities-view.png" alt="Checks → Vulnerabilities by image: 62 images with Critical CVEs of 99 scanned and 16 not scanned yet, a severity bar, and one row per running image with its findings, how many have a fix, and the workloads that run it" width="800">
  299. <br><em>Vulnerabilities — Critical and High CVEs in the images that run now</em>
  300. </p>
  301. ### Access Control (RBAC visibility)
  302. Inspect what any ServiceAccount can actually do — without three `kubectl describe` calls.
  303. - **ServiceAccount, Role, and binding details**: direct and inherited bindings, effective permissions, and the Pods that use a ServiceAccount
  304. - **Pod and workload Permissions**: the most-permissive rules the Pod's ServiceAccount grants, with a blast-radius alert for wildcards, cluster-admin, escalation verbs, or cluster-wide `create pods`
  305. - **"My Permissions" panel**: a live `SelfSubjectRulesReview` for the current user, for fast "why can't I do X" debugging
  306. See [Access control](https://radarhq.io/docs/features/access-control).
  307. ### Authentication
  308. For shared in-cluster deployments, Radar supports optional user authentication with per-user Kubernetes RBAC.
  309. - **Proxy mode** — works with oauth2-proxy, Pomerium, Cloudflare Access, or any auth proxy that sets forwarded headers
  310. - **OIDC mode** — built-in login via Google, Okta, Dex, Keycloak, or any OIDC provider
  311. - Per-user namespace scoping and write authorization via K8s impersonation
  312. - UI adapts automatically — buttons only appear if the user has RBAC permission
  313. No auth by default (local use). See the **[Authentication Guide](docs/authentication.md)** for setup.
  314. ---
  315. ## Supported Resources & Integrations
  316. Radar auto-discovers any CRD in your cluster. Popular tools get [dedicated integrations](docs/integrations.md) with resource views, topology, AI context and application evidence. Coverage varies by integration.
  317. The Helm chart grants read access to common built-in Kubernetes kinds; Secrets, RBAC objects and CertificateSigningRequests depend on chart settings and the authentication mode. CRD-based integrations need the CRD installed in your cluster *and* read access; most API groups are granted by default, and the chart's [RBAC](deploy/helm/radar/README.md#rbac) and [CRD access](deploy/helm/radar/README.md#crd-access) sections list what is on, what is opt-in, and how to add rules.
  318. | Category / integration | Coverage |
  319. |----------|-----------|
  320. | **Workloads** | Deployments, DaemonSets, StatefulSets, ReplicaSets, Pods, Jobs, CronJobs |
  321. | **Networking** | Services, Ingresses, NetworkPolicies, Endpoints, EndpointSlices, PodDisruptionBudgets |
  322. | **Configuration** | ConfigMaps, Secrets (names only, values hidden), LimitRanges, ResourceQuotas |
  323. | **Storage** | PersistentVolumeClaims, PersistentVolumes, StorageClasses |
  324. | **Autoscaling** | HorizontalPodAutoscalers, VerticalPodAutoscalers |
  325. | **Cluster** | Nodes, Namespaces, ServiceAccounts, Events |
  326. | **Other Kubernetes APIs** | CertificateSigningRequests; Workloads, PodGroups, CompositePodGroups, PodCertificateRequests, ClusterTrustBundles (only when served by the cluster) |
  327. | **GitOps (FluxCD)** | GitRepository, OCIRepository, HelmRepository, Kustomization, HelmRelease, Alert |
  328. | **GitOps (ArgoCD)** | Application, ApplicationSet, AppProject |
  329. | **Argo Rollouts** | Rollout |
  330. | **Argo Workflows** | Workflow, WorkflowTemplate |
  331. | **[Reflector](docs/integrations.md#configmap-and-secret-reflection-reflector)** | ConfigMap/Secret reflection details, source and mirror relationships, recorded copy evidence |
  332. | **cert-manager** | Certificate, CertificateRequest, Order, Challenge, Issuer, ClusterIssuer |
  333. | **Gateway API** | Gateway, GatewayClass, HTTPRoute, GRPCRoute, TCPRoute, TLSRoute, UDPRoute |
  334. | **Istio** | VirtualService, DestinationRule, Gateway, ServiceEntry, PeerAuthentication, AuthorizationPolicy |
  335. | **Traefik** | IngressRoute, IngressRouteTCP, IngressRouteUDP, Middleware, MiddlewareTCP, TraefikService, ServersTransport, ServersTransportTCP, TLSOption, TLSStore |
  336. | **Contour** | HTTPProxy |
  337. | **Knative Serving** | Service, Configuration, Revision, Route, DomainMapping |
  338. | **Knative Eventing** | Broker, Trigger, EventType, Channel, InMemoryChannel, Subscription |
  339. | **Knative Sources** | PingSource, ApiServerSource, ContainerSource, SinkBinding |
  340. | **Knative Flows** | Sequence, Parallel |
  341. | **Knative Networking** | Ingress, Certificate, ServerlessService |
  342. | **Karpenter** | NodePool, NodeClaim (+ provider-specific NodeClasses via auto-discovery) |
  343. | **OpenTelemetry Operator** | [OpenTelemetryCollector and Instrumentation](docs/integrations.md#opentelemetry-operator): reconciliation, configured pipelines and injection settings |
  344. | **System Upgrade Controller** | [Plan](docs/integrations.md#system-upgrade-controller): per-node upgrade progress, an Issue for an invalid Plan, and k3s/RKE2 upgrade Plans on the Upgrade impact page |
  345. | **Flagger** | [Canary and MetricTemplate](docs/integrations.md#flagger): recorded rollout state, target/autoscaler/template links and failed-rollout Issues |
  346. | **KEDA** | ScaledObject, ScaledJob, TriggerAuthentication, ClusterTriggerAuthentication |
  347. | **Prometheus Operator** | ServiceMonitor, PodMonitor, PrometheusRule, Alertmanager |
  348. | **Security (Trivy)** | VulnerabilityReport, ConfigAuditReport, ExposedSecretReport, ClusterComplianceReport, SbomReport, RbacAssessmentReport, InfraAssessmentReport |
  349. | **Strimzi** | [KafkaConnector failure evidence](docs/integrations.md#strimzi-kafka-connectors) (connector/task status) |
  350. | **[RabbitMQ](docs/integrations.md#local-runtime-evidence-rabbitmq-nats-and-vault)** | Node-reported disk and memory alarms - **local collection** |
  351. | **[NATS](docs/integrations.md#local-runtime-evidence-rabbitmq-nats-and-vault)** | JetStream consumer backlog, acknowledgment-pending and redelivery counters - **local collection** |
  352. | **Velero** | Backup, Restore, Schedule, BackupStorageLocation, VolumeSnapshotLocation |
  353. | **External Secrets** | ExternalSecret, ClusterExternalSecret, SecretStore, ClusterSecretStore |
  354. | **Secrets Store CSI Driver** | [SecretProviderClass and Pod mounts](docs/integrations.md#secrets-store-csi-driver): mount state, object versions and synced Secrets in the Pod drawer |
  355. | **[Vault](docs/integrations.md#local-runtime-evidence-rabbitmq-nats-and-vault)** | Initialization, seal and standby state - **local collection** |
  356. | **CloudNativePG** | Cluster, Backup, ScheduledBackup, Pooler, Database, Publication, Subscription, ImageCatalog, ClusterImageCatalog, ObjectStore — plus [dedicated views](docs/cnpg.md) for fleet, protection and declaration triage |
  357. | **Crossplane** | Managed Resources (any provider), Composite Resources, Claims, Provider, ProviderConfig, Function, Configuration, Composition, CompositionRevision, XRD |
  358. | **Kyverno** | Policy, ClusterPolicy, PolicyReport, ClusterPolicyReport |
  359. | **Sealed Secrets** | SealedSecret |
  360. | **Dynamic Resource Allocation** | ResourceClaim, ResourceClaimTemplate, DeviceClass, ResourceSlice (resource.k8s.io, K8s 1.32+) |
  361. | **NVIDIA GPU Operator** | ClusterPolicy, NVIDIADriver |
  362. | **Calico** | NetworkPolicy, GlobalNetworkPolicy, StagedNetworkPolicy, StagedGlobalNetworkPolicy, StagedKubernetesNetworkPolicy, IPPool, HostEndpoint, Tier |
  363. | **Kueue** | ClusterQueue, LocalQueue, Workload, ResourceFlavor, AdmissionCheck (+ Cluster Autoscaler ProvisioningRequest) — basic |
  364. | **KubeRay** | RayCluster, RayJob, RayService, RayCronJob — basic |
  365. | **KServe** | InferenceService, ServingRuntime, ClusterServingRuntime, InferenceGraph, TrainedModel, LLMInferenceService — basic |
  366. | **Inference Gateway** | InferencePool (v1 + alpha groups), InferenceObjective — basic |
  367. | **Batch** | LeaderWorkerSet, JobSet, Volcano (Job/Queue/PodGroup/JobFlow/JobTemplate), Kubeflow (PyTorchJob/TFJob/MPIJob/TrainJob) — basic |
  368. | **KAI Scheduler** | Queue, PodGroup — basic |
  369. | **Model serving** | KAITO (Workspace, RAGEngine), NVIDIA NIM (NIMService/NIMCache/NIMPipeline), AMD GPU Operator (DeviceConfig) — basic |
  370. | **Cost (OpenCost / Kubecost)** | Namespace/workload/node cost via compatible Prometheus metrics or the Kubecost 3 Aggregator (no CRDs) |
  371. | **CRDs** | Any Custom Resource Definition in your cluster (auto-discovered) |
  372. ### Local runtime evidence
  373. When Radar runs locally, use **Collect RabbitMQ evidence**, **Collect NATS evidence** or **Collect Vault evidence** in resource details to select a Pod and collect explicitly. MCP clients can also collect after operator approval.
  374. These observations describe one Pod endpoint, not overall application health, and do not add automatic Issues detection. See the [collection requirements and limitations](docs/mcp.md#explicit-local-runtime-evidence).
  375. ---
  376. ## Keyboard Shortcuts
  377. Radar is keyboard-first: `?` lists every shortcut, `⌘K` opens the command palette, `/` focuses search, and `g` followed by a letter switches views (`g i` Issues, `g t` Topology, `g l` Timeline, `g r` Resources). The full list is in the [keyboard shortcuts reference](https://radarhq.io/docs/reference/keyboard-shortcuts).
  378. ---
  379. ## Security
  380. Radar reads your cluster through your own credentials and keeps cluster data local. It does not upload manifests, logs, events, metrics, or resource data to Skyhook, and it does not require an account, agent, or cloud backend. When you connect an AI agent or run an AI investigation, what Radar returns goes to that agent and its model provider. Found a vulnerability? Please report it privately to **security@skyhook.io** — see [SECURITY.md](SECURITY.md) for the process and response timelines.
  381. ---
  382. ## Community and support
  383. - **[Slack](https://radarhq.io/slack)** is the fastest way to get help. Ask in `#radar-help`, share feedback, and talk Kubernetes with the Radar team and other users.
  384. - **[GitHub Discussions](https://github.com/skyhook-io/radar/discussions)** for ideas and longer questions you want others to find later.
  385. - **[GitHub Issues](https://github.com/skyhook-io/radar/issues)** for bugs and feature requests.
  386. ---
  387. ## Development
  388. See the **[Development Guide](DEVELOPMENT.md)** for building from source and contributing. For automation and integrations, see the [HTTP API reference](https://radarhq.io/docs/reference/api).
  389. Quick start:
  390. ```bash
  391. git clone https://github.com/skyhook-io/radar.git
  392. cd radar
  393. make deps
  394. # Terminal 1: Frontend with hot reload (port 9273)
  395. make watch-frontend
  396. # Terminal 2: Backend with hot reload (port 9280)
  397. make watch-backend
  398. ```
  399. ---
  400. ## Contributing
  401. Contributions are welcome! Please read our [Contributing Guide](CONTRIBUTING.md) for details on the development workflow, pull request process, and coding standards.
  402. Questions about a change? Ask in [Slack](https://radarhq.io/slack) before you start, or open a [Discussion](https://github.com/skyhook-io/radar/discussions).
  403. ---
  404. ## About
  405. Radar is built and maintained by [Skyhook](https://skyhook.io) (YC W23) and is open source under Apache-2.0. The OSS version is fully featured and the recommended way to run Radar.
  406. For teams that want hosted multi-cluster Radar, with fleet views, alerts, and shared links, we also offer [Radar Cloud](https://radarhq.io).
  407. ---
  408. ## License
  409. Apache 2.0 — see [LICENSE](LICENSE)
  410. ---
  411. <p align="center">
  412. <strong>Open source. Free forever.</strong>
  413. <br>
  414. <sub>Built by <a href="https://skyhook.io">Skyhook</a></sub>
  415. </p>

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.