How snowops-oss/snowopslabs works
SnowOps Labs is a Kubernetes operations simulator. Engineers use labctl or the browser UI to provision a real platform, activate scenarios or inject incidents, then verify fixes against the live cluster; results, learning paths, timed challenges, traffic exercises, and app/provider comparison extend that workflow. The graph includes the CLI, runtime and domain engines, HTTP/UI boundary, and key user-facing capabilities. Some domain wiring is documented only at a high level, so uncertain links are dashed rather than asserted as inspected calls.
Main entry points: main.go labctl CLI · server.go HTTP API · engine.go Scenario engine · main.tsx Browser UI
Components 20
Entry points
- labctl CLI
src/cmd/labctl/main.go - Browser UI
src/ui/src/main.tsx
Lab operations
- Cluster runtimes
src/internal/runtime/manager.go - Platform providers
src/internal/platform/registry.go - Workload apps
src/internal/workload/workload.go - Scenario engine
src/internal/scenario/engine.go - Incident engine
src/internal/incident/incident.go - Traffic exercises
src/internal/traffic/traffic.go
Practice and assessment
- Live checks
src/pkg/checks/runner.go - Learning paths
src/internal/learn/learn.go - Timed challenges
src/internal/challenge/challenge.go - Provider comparison
src/internal/compare/compare.go
API and interface
- HTTP API
src/internal/httpapi/server.go - Product views
src/ui/src/views/Scenarios.tsx - UI API client
src/ui/src/api/client.ts - Query cache
src/ui/src/lib/queryClient.ts
State and results
- Run execution
src/internal/run/engine.go - Persistent state
src/internal/store/store.go - Results and leaderboard
src/internal/results/results.go
Other components
- Engineer
Connections 22
- Engineer → labctl CLI: runs commands
README.md - Engineer → Browser UI: operates lab
README.md - Browser UI → Product views: renders routes
- Browser UI → UI API client: requests data
- Product views → UI API client: calls endpoints
- Product views → Query cache: reads cached data
- UI API client → HTTP API: sends HTTP requests
- labctl CLI → Cluster runtimes: provisions clusters
README.md - labctl CLI → Platform providers: builds platform
README.md - labctl CLI → Scenario engine: activates scenarios
README.md - labctl CLI → Incident engine: injects faults
README.md - Scenario engine → Live checks: grades work
src/internal/scenario/engine.go - Scenario engine → Workload apps: binds workload
src/internal/scenario/engine.go - labctl CLI → Traffic exercises: drives traffic
- labctl CLI → Learning paths: runs curriculum
- labctl CLI → Timed challenges: runs challenges
- labctl CLI → Provider comparison: compares providers
- HTTP API → Scenario engine: serves operations
- HTTP API → Incident engine: serves operations
- HTTP API → Run execution: dispatches actions
- Run execution → Persistent state: persists run state
- Results and leaderboard → Persistent state: reads outcomes