DRAForge is a Dynamic Resource Allocation (DRA) observability, simulation, and diagnostics platform for Kubernetes. It allows developers and administrators to model, simulate, and diagnose cluster hardware resource allocations (GPUs, edge devices, smartNICs) dynamically—without requiring physical accelerator hardware.
Kubernetes Dynamic Resource Allocation (DRA) offers fine-grained, driver-controlled accelerator sharing. However, developing and debugging DRA configurations presents a major challenge:
- Hardware Scarcity: Acquiring and configuring dedicated accelerator nodes (e.g., NVIDIA H100 GPUs) for test environments is costly and slow.
- Observability Gap: Native Kubernetes scheduling logs make it difficult to visualize why a resource claim failed to bind to a pod.
DRAForge bridges this gap by providing an evidence-based diagnostics registry, a dynamic virtual device simulator, a terminal user interface (TUI), and a real-time interactive relationship graph dashboard.
- Virtual Device Pools: Simulate arbitrary hardware profiles (e.g. GPUs, FPGAs, High-Speed NICs) on worker nodes using custom attributes and capacities.
- Diagnostics Doctor: Honest, non-mocked configuration analysis (e.g. API availability, version compatibility, ResourceSlice consistency checks).
- Explain Engine: Real-time evaluation of selectors, capacity bounds, and node affinity to pinpoint why claims are pending.
- Bubble Tea TUI: Professional terminal-based monitor for dynamic pool capacities.
- Interactive Graph Dashboard: Real-time SVG visualization of relationships between Pods, Claims, Devices, and Pools.
graph TD
subgraph DOKS Cluster
Server[DRAForge Server] <--> WebSPA[Vite + React SPA Dashboard]
Controller[DRAForge Controller] <--> SimulatedDevicePool[SimulatedDevicePool CRD]
Plugin[Node Plugin DaemonSet] --> ResourceSlice[ResourceSlice Spec]
APIServer[Kubernetes API Server] <--> Server
APIServer <--> Controller
APIServer <--> Plugin
end
CLI[DRAForge CLI] <--> APIServer
go install github.com/oaslananka/draforge/cmd/draforge@latestOr clone and build locally:
git clone https://github.com/oaslananka/draforge.git
cd draforge
task build # Builds all three binaries into bin/
./bin/draforge versionBinaries are also available as pre-built archives from the GitHub Releases page.
To run DRAForge locally using a Go development environment and a kind cluster:
-
Prerequisites:
- Install Go 1.26+
- Install
kind(with DRA feature gate enabled) - Install
task
-
Build and Deploy:
task build kubectl apply -f deploy/crds/simulateddevicepool-crd.yaml kubectl apply -f examples/scenarios/basic-gpu.yaml
-
Launch TUI:
./bin/draforge tui
⚠️ Billable Resources: This task provisions a live DOKS cluster and DOCR registry on your DigitalOcean account and incurs cloud costs. Always runtask demo:downwhen finished to destroy all billable resources.
To deploy a live read-only public showcase to DOKS:
task demo:upThis script audits resource limits, runs Terraform provisioners, builds images remotely via Kaniko, installs the Helm release, and outputs the live external URL.
To tear down the showcase and clean all billable resources:
task demo:down# Run all unit tests (fast, no race)
go test ./...
# or: task test:unit
# Run unit tests with race detector and coverage
go test -race -coverprofile=coverage.out ./...
# or: task test:race
# Run all Go vet checks
go vet ./...
# or: task vet
# Run full CI suite (unit + race)
task testEnd-to-end tests require a real Kubernetes cluster with DRA feature gate and are gated by DRAFORGE_E2E=1:
DRAFORGE_E2E=1 go test ./tests/e2e -vSee docs/release.md for the full release process.
task release:local
# or: goreleaser release --snapshot --clean --skip=docker,sbom,signgit tag v0.x.x
git push origin v0.x.x
goreleaser release --clean| Command | Description | Example |
|---|---|---|
draforge version |
Print binary version and commit details | draforge version |
draforge discover |
Lists active DRA pools, devices, and resource claims | draforge discover -o json |
draforge claims |
Summarizes claims status in a formatted table | draforge claims |
draforge graph |
Generates relationship graph in DOT or Mermaid formats | draforge graph -o mermaid |
draforge explain |
Troubleshoots why a ResourceClaim is pending | draforge explain my-pending-claim |
draforge doctor |
Executes cluster and driver diagnostics checks | draforge doctor |
draforge tui |
Launches the terminal-based monitor console | draforge tui |
draforge serve |
Runs HTTP API server and Vite dashboard frontend | draforge serve |
| Resource | Description |
|---|---|
| Contributing Guide | Setup, testing, PR expectations, and what not to commit |
| Security Policy | Vulnerability reporting and security model |
| Installation Guide | Demo and production installation profiles |
| Operations Guide | Day-two operations, upgrades, metrics, logs, and cleanup |
| Troubleshooting Guide | Diagnostics for common issues and pending claims |
| Maintainer Checklist | Internal review and release processes |
| Release Process | Snapshot and tagged release workflow |
| Dashboard Guide | Web dashboard setup and usage |
| Simulator Scenarios | Scenario authoring and fault injection |
| Kubernetes DRA Compatibility | DRA API support matrix |
| Maintainers | Current project maintainers |
| Governance | Decision-making and roles |
| Support | How to get help |
Screenshots of the terminal UI and web dashboard are stored in docs/assets/ when available.
DRAForge enforces a read-only public API model. The Go web server exposes read-only endpoints and SSE streams to the dashboard, preventing any write actions or pod execution from the web UI. Cluster modifications (scenario application and fault injections) are strictly restricted to the CLI and authenticated using the administrator's local kubeconfig (see ADR-0009).
For Kubernetes DRA API support and known limitations, see Kubernetes DRA Compatibility.
This project is licensed under the Apache License, Version 2.0. See LICENSE for the full license text.