김태오

The last major phase was about honesty: were the controller decisions actually touching Kubernetes, and was the dashboard explaining the result without overclaiming?The dual-cluster comparison gave me a strong local framework, but it also exposed a subtle gap. Agent A/B/C decisions were being evaluated through the orchestrator path, while the dashboard was reading real Kubernetes metrics. That m..

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..