Test potential latency gains from distributing KAS across multiple regions
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Goal
We consider deploying KAS across multiple regions, likely using Runway. Before we decide about it, we want to better understand the value it might provide to our users.
Proposal
From:
Do we have any data on the global distribution of agentk usage? Can we get it from referrer IP addresses? Before we spend time on this, we should figure out if it's worth the effort:
- how many regions would we want to support?
- how many users do we have today and expect to have in the future?
- how many of them would churn or not become users if we don't add multi-region KAS support?
- how much work would it be to set multi-region KAS support up?
We already have a simple load test. Can be run with go test ./internal/module/kubernetes_api/test in the agent repo. It needs to be adjusted to work/do what you want - credentials, concurrency, delay, kas URL. t.SkipNow() should be removed so that it is actually executed. It doesn't calculate any timing information either.