Skip to content

Shuttle Success Criteria

  1. Deploys to a DOKS cluster and registers with Starbase
  2. Creates the full per-customer resource set with correct labels from desired state
  3. Fluent Bit and vmagent successfully attribute logs/metrics via Shuttle's labels
  4. Reports pod snapshots every 60s for correct per-minute billing
  5. Reports cluster capacity every 60s
  6. Handles Starbase unavailability without crashing
  7. Garbage-collects resources removed from desired state
  8. Applies cluster_config changes (e.g., LB size unit)
  9. Passes go build ./... and go vet ./...
  10. Memory under 200Mi for 500+ customer pods

Cross-references

The per-customer resource set in criterion 2 → §20.2 · the labels behind criterion 3 → §24.1 · the snapshot/capacity cadence in criteria 4–5 → §25 · Starbase-unavailability handling in criterion 6 → §27 · the memory ceiling in criterion 10 → §28.