feat: add fleet autoscaling baseline

This commit is contained in:
Josh Creek
2026-08-31 21:58:42 +01:00
parent b2ee9ec92d
commit 90126a4be7
5 changed files with 33 additions and 3 deletions
+5 -2
View File
@@ -127,8 +127,11 @@ product policy are in [`docs/MATCHMAKING.md`](docs/MATCHMAKING.md).
Agones integration remains.
- [ ] Deliver/verify the signed roster after allocation and expose client
tickets only after backend `assignment_ready`.
- [ ] Keep >=2 Ready processes across >=2 on-demand nodes/failure domains per
queue-enabled region; only Allocated count may fall to zero.
- [ ] **IN PROGRESS:** Keep >=2 Ready processes across >=2 on-demand
nodes/failure domains per queue-enabled region; only Allocated count may
fall to zero. A provider-neutral Agones FleetAutoscaler now encodes a
two-process Ready buffer and six-process warm cap; regional node pools,
pre-pull rollout and measured N+1 capacity remain.
- [ ] Spread on-demand capacity across zones with N+1 headroom; do not place
live matches on interruptible nodes.
- [ ] Benchmark native x86_64 boot, p99 CPU/RSS/network and tick health; set