2.2.0 (2026-10-15)

✨ JET Pilot 2.2: GitOps, usage history and access review

JET Pilot now understands the tools around your workloads, and every side panel tells you what an object is doing.

One page for every Flux Kustomization, Flux HelmRelease and Argo CD Application across your clusters, problems first.
Open one to see its source, what it delivered and why it fails, then reconcile, suspend, sync or refresh it.

CPU and memory charts (plus network for pods) over 1h, 6h, 24h or 7d in the side panel of pods, workloads, nodes and namespaces, with requests and limits drawn in.
Nothing to set up: JET Pilot finds the cluster's Prometheus, Thanos Query or VictoriaMetrics by itself and queries it through the API server, so there's nothing to port-forward. Without one, the charts show metrics-server's last 15 minutes.

Ask "Can I delete deployments in payments?" or "Who can…?" and get the answer with the binding and role behind it, or see everything a user, group or service account may do.
Roles, bindings and service accounts get side panels that read like sentences.

Releases and their history load straight from the cluster, without the helm binary. A release panel shows notes, resources, values and a revision timeline that says what changed, with rollback and compare.
Find and install charts: search your repositories and Artifact Hub, then install with a values editor checked against the chart's schema and a dry-run preview.

Every custom resource shows its CRD's printer columns, and well-known projects get their own sidebar sections.
cert-manager, Gateway API, Karpenter, KEDA, External Secrets and Prometheus Operator get curated columns, states in words and side panels, with actions such as Renew, Pause and Sync now.

Every panel opens with the object's state in a sentence and links to related objects, with sections for pods, nodes, services, ingresses, storage, HPAs, jobs, cron jobs, config maps and namespaces.
Edit labels, annotations and node taints in place, with a preview before you save. Describe and YAML now come straight from the API, so they work without kubectl.

Forwards run over the Kubernetes API and follow their pod through restarts and rollouts.
Ports show by name, forwards remember their local ports, and an HTTP tester sends requests through a forward.

One small YAML file per action: open a URL, run a command or kubectl, exec into a container, apply a patch or copy text. They show up in row menus, the side panel and the command palette (Settings › Actions).
Safe by design: values from the cluster never become code, and actions that change the cluster go through the guardrails.

JET Pilot loads a fifth less code before it first draws, and the side panel and dialogs follow right after.

Every change to a cluster in this release goes through the guardrails: read-only clusters block it, and protected clusters ask you to type the name.

The full history is in the new changelog.

access review: Can I, Who can, and what a subject can do (#114) (1e50ce6)
custom actions, one-click actions from small YAML files (#116) (b7c774b)
GitOps for Flux and Argo CD (#111) (9139aee)
native Helm releases, a release panel, chart search and a guided install (#113) (814fffd)
native, self-healing port forwards with an HTTP tester (#115) (c3f8fd4)
printer columns for every CRD, friendly navigation and operator views (#117) (e96be55)
rich side panels, inline label and taint editing, and a native describe (#118) (9df21a1)
usage history from Prometheus in the side panel (#112) (ea055e0)
What's New and README for 2.2 (#122) (b3ef97b)

load the side panel and dialogs after the first frame (#120) (d8971d1)
split radix-vue per component and load startup code as one chunk (#121) (96868dd)

macOS: brew install --cask unxsist/tap/jet-pilot, or download the .dmg for Apple Silicon (aarch64) or Intel (x64).
[!IMPORTANT]
JET Pilot isn't notarized by Apple. The Homebrew tap removes the quarantine flag for you. If you install the .dmg yourself and macOS says the app "is damaged" or "can't be verified", run this once:
```
xattr -dr com.apple.quarantine "/Applications/JET Pilot.app"
```
Windows: the .exe or .msi installer (SmartScreen: More info → Run anyway).
Linux: .deb, .rpm or .AppImage for x64 and ARM64.

Existing installs update themselves.