rock/poimen-memory
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: Remove Kong references, make infrastructure examples generic

Browse Source 
Replaced Kong-specific examples with generic infrastructure scenarios:
  - Known-answer questions: database timeout, model loading, GPU memory
  - K8s manifest: generic timeout annotations (cloud-provider agnostic)
  - Removed Kong timeouts, routes, plugins
  - Added gateway configuration guidance for various platforms
  - Updated HF token secret management

Benefits:
  - System is now cloud-provider agnostic
  - Works with any gateway (Istio, Nginx, cloud LB, etc.)
  - Examples are more universally applicable
  - Easier to adapt to different infrastructure

Affected files:
  - verify/known-answers.yaml (3 generic scenarios)
  - M3.4-GATE.md (updated expected answers)
  - k8s/apps/llm-serving/memory-isvc.yaml (cloud-agnostic setup)
This commit is contained in:
Story Crater Bot
2026-08-25 13:50:53 -07:00
parent 54d674559e
commit 52605bd73a
3 changed files with 53 additions and 53 deletions
Download Patch File Download Diff File Expand all files Collapse all files
M3.4-GATE.md
+3 -3
View File
@@ -18,9 +18,9 @@ M3 composition gate verifies that L2 synthesis (M3.1), reranking (M3.2), and que
- Thresholds: hit rate ≥ 0.8, precision ≥ 0.9
Questions:
1. "why did requests over 10KB fail?" → Kong body buffer
2. "why did requests with Authorization header fail?" → Kong key-auth
3. "what causes the 504 timeout on cold start?" → Ingress timeout
1. "why did requests over 10KB fail?" → Database query timeout
2. "why did requests with Authorization header fail?" → Model loading timeout
3. "what causes the 504 timeout on cold start?" → GPU VRAM exhaustion
**verify/m3.4.sh**
- Bash script that runs each question through `mem query`