the ci problem I think is fundamentally easier, since each is its own instance, you just need an orcestrator to coordinate, that can also be one per a group of repositories (there are no cross-repo triggers anyway). The actions issues we keep facing seem to be at the agregation/collector side of things, similar to general api issues, not a fundamental kubernetes scaling issue.