What's missing
All the scenarios under config/scenarios/ put some gateway in front of the model server (istio, agentgateway, gke, epponly, etc). There's no way to just expose it via a plain Service with nothing in front.
Why this matters
If you want to measure gateway/router overhead (like agentgateway+EPP vs no routing at all), you need a baseline where the load generator hits the model server directly, no proxy in between. Right now the only way to do that is to stand the target up manually outside the framework and point existing_stack/run_only.sh at its base_url. Works, but it means this baseline can't just live as a regular scenario like everything else.
Idea
Something like gateway.className: none that skips gateway setup entirely and just exposes the model server via a Service. Then this baseline could be its own scenario and get pulled into DoE experiments/cross_treatment comparisons like the rest.
can help build this if useful
What's missing
All the scenarios under config/scenarios/ put some gateway in front of the model server (istio, agentgateway, gke, epponly, etc). There's no way to just expose it via a plain Service with nothing in front.
Why this matters
If you want to measure gateway/router overhead (like agentgateway+EPP vs no routing at all), you need a baseline where the load generator hits the model server directly, no proxy in between. Right now the only way to do that is to stand the target up manually outside the framework and point existing_stack/run_only.sh at its base_url. Works, but it means this baseline can't just live as a regular scenario like everything else.
Idea
Something like
gateway.className: nonethat skips gateway setup entirely and just exposes the model server via a Service. Then this baseline could be its own scenario and get pulled into DoE experiments/cross_treatment comparisons like the rest.can help build this if useful