Garnet Docs — The runtime review for your PRs

Archived — Kubernetes/DaemonSet deployment is Phase-2 runtime-platform content, not part of the current PR-review launch. Kept for reference.

Privileged DaemonSet — Jibril loads eBPF on each node. Linux kernel 5.10+ required. See Jibril requirements.

Add Helm repo

helm repo add garnet https://helm.garnet.ai
helm repo update

Install

helm install garnet garnet/garnet \
  --namespace garnet \
  --create-namespace \
  --set garnet.token=YOUR_API_TOKEN

Replace YOUR_API_TOKEN with a token from app.garnet.ai → Settings → API Tokens.

Verify

kubectl get pods -n garnet

One pod per node. Runs appear at app.garnet.ai within seconds — with Run Profiles and check results.

Configuration

Parameter	Description	Default
`garnet.token`	API token from app.garnet.ai	`""` (required)
`cluster.name`	Display name in dashboard	`garnet-cluster`

For init containers, heartbeat intervals, and full chart overrides, see the chart’s values.yaml and Jibril Kubernetes docs.

Agent doesn't appear in the dashboard

Check pod status and logs:

kubectl get pods -n garnet
kubectl logs -n garnet -l app=garnet

Verify garnet.token is set correctly. The token must match a valid API token from app.garnet.ai → Settings → API Tokens.

Pods in CrashLoopBackOff

Jibril requires Linux kernel 5.10+ with eBPF support. Verify your node kernel versions:

kubectl get nodes -o wide

If nodes are running an older kernel, upgrade to a supported version. See Jibril requirements.

Custom cluster name

helm upgrade --install garnet garnet/garnet \
  --namespace garnet \
  --set garnet.token=YOUR_API_TOKEN \
  --set cluster.name=my-cluster

Upgrade or reinstall

helm upgrade garnet garnet/garnet \
  --namespace garnet \
  --set garnet.token=YOUR_API_TOKEN

⌘I