draforge

DRAForge Dashboard

The web dashboard is a read-only React single-page application served by the DRAForge server. It visualizes cluster DRA resources, device pools, claims, allocation status, and the live resource relationship graph.

Read-Only Model

The dashboard enforces a strict read-only public API model:

• All data is fetched via HTTP GET requests.
• The frontend never performs write operations (no POST/PUT/PATCH/DELETE).
• Cluster modifications (scenario application, fault injection) are CLI-only operations using the administrator’s kubeconfig.
• CORS defaults to * (public), configurable via CORS_ALLOWED_ORIGINS.

API Endpoints

Endpoint	Method	Description
/api/summary	GET	Cluster-wide counts (pools, devices, claims, doctor status)
/api/pools	GET	Simulated device pools
/api/devices	GET	Discovered devices
/api/claims	GET	ResourceClaims and their allocation status
/api/graph	GET	Snapshot of the resource relationship graph
/api/doctor	GET	Diagnostics check results (PASS/WARN/FAIL)
/api/explain?claim=X&namespace=default	GET	Allocation explanation tree for a claim
/api/stream	SSE	Live graph updates via Server-Sent Events

SSE Stream

The /api/stream endpoint pushes ResourceGraph JSON updates every 5 seconds.

The dashboard handles the stream with controlled reconnection:

• Connection opens → status shows connected
• On error/close → status shows reconnecting with backoff: 1s → 2s → 5s (max)
• On successful reconnect → resets to 1s and shows connected
• Component unmount → EventSource closed, no memory leak

A stream status badge is visible in the dashboard header.

Empty Cluster Behavior

When no DRA resources are discovered, the dashboard shows clear messages:

• Pools tab: “No DRA resources discovered yet.”
• Devices tab: “No DRA resources discovered yet.”
• Claims tab: “No ResourceClaims found in the current cluster.”
• Graph tab: “No resource relationships to display. Deploy a SimulatedDevicePool scenario to populate the graph.”
• Doctor tab: “Unable to load DRAForge diagnostics.” (on error)

Error Handling

API errors are displayed inline without raw stack traces:

• Connection errors show a warning banner at the top of the page.
• Individual tab errors show a per-section message.
• Structured errors { "error": { "message": "...", "code": "..." } } are parsed safely.
• Legacy { "error": "..." } format is also supported.

Development

# Install dependencies
pnpm --dir web install

# Start dev server (port 3000, proxies /api to localhost:8080)
pnpm --dir web dev

# Build for production
pnpm --dir web build

# Lint
pnpm --dir web lint

The production build outputs to web/dist/, which is served by the Go server from ./web/dist/.

Troubleshooting

| Symptom | Likely Cause | Check | |—|—|—| | Dashboard shows “Disconnected” | Go server not running or /api/stream unreachable | Server logs, network | | All data shows “No DRA resources” | No SimulatedDevicePool CRD applied | kubectl get simpool | | Doctor tab shows no data | Server cannot connect to cluster | kubectl cluster-info | | Graph empty | No resource relationships exist | Deploy a scenario | ```

This site is open source. Improve this page.