Description
We have per-repo quotas, but these are applied separately at each federation member. This means that a per-repo limit of 100 can actually take up 100 slots on each federation member, or over 60% of our whole federation capacity right now. This wouldn't be a huge issue if our per-repo limit were significantly less than each federation member's capacity, but each federation member only allows 80-200 slots. This becomes more of an issue now that GKE has a limit, which is effectively increasing the repo quota on repos assigned to GKE any time GKE itself is considered full.
To properly apply limits, we need federated quotas, counting sessions for repos across all members, to use for applying limits. That sounds complicated, but I don't know another way