| 일 | 월 | 화 | 수 | 목 | 금 | 토 |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | 6 | |
| 7 | 8 | 9 | 10 | 11 | 12 | 13 |
| 14 | 15 | 16 | 17 | 18 | 19 | 20 |
| 21 | 22 | 23 | 24 | 25 | 26 | 27 |
| 28 | 29 | 30 |
- Cloud Systems
- MSSQL
- Multi Agent Systems
- ML
- Kind
- rllib
- spring boot
- karpenter
- 스프링부트
- Kafka
- keda
- minreplica
- polars
- virtualservice
- Reinforcement Learning
- propogation
- Observability
- traceId
- hammerDB
- Failure Prediction
- Prometheus
- zset
- AIOpsLab
- 0 replica
- Database
- XGBoost
- Kubernetes
- Borg
- HPA
- eks
- Today
- Total
목록Kind (2)
김태오
The local dual-cluster comparison became the most important dashboard phase of the project.Before this, I had an experimental controller and a live dashboard. That was useful, but it was still too easy to fool myself. I needed a baseline. Not a perfect cloud baseline, but at least a local setup where the same external stimulus hit two Kubernetes clusters: one running the experimental Agent A/B/C..
After the six-layer stack existed, the next problem was making it feel alive. Synthetic traces were useful, but I wanted the dashboard to react to Kubernetes state, not just replayed rows.This phase had two jobs. First, I needed trace and synthetic inputs to keep exercising the orchestrator when no cluster was running. Second, I needed a live Kubernetes loop that could collect a snapshot, run th..