// the find
PlayFab/thundernetes
Thundernetes makes it easy to run your game servers on Kubernetes
Thundernetes is a Kubernetes operator from the PlayFab/Azure team that manages game server lifecycle — standby pools, allocation, scaling — using custom CRDs. It targets studios that want to self-host multiplayer servers on Kubernetes without rebuilding the scaffolding PlayFab normally handles for you. The README is upfront that this is beta and not production-supported, which is refreshingly honest.
The GSDK compatibility layer is genuinely useful: if you're already using PlayFab Multiplayer Servers, you can drop Thundernetes in without rewriting your game server integration. The node agent design (a DaemonSet process per node that handles heartbeats and allocation state locally) avoids the thundering-herd problem you'd get if all servers talked directly to the controller. E2E test coverage is solid — there are dedicated test files for crash recovery, unhealthy servers, allocation exhaustion, and operator restarts, which suggests the team actually ran into these edge cases. The standby forecaster with pluggable algorithms (even if experimental) is a real operational need that most DIY setups skip.
Beta status with no production support from Microsoft is a meaningful risk — the README says it explicitly, but studios may not internalize what that means until something breaks at 2am. The intelligent standby forecaster is marked experimental inside an already-beta project, so there are two layers of 'don't rely on this' stacked on a feature that directly affects cost and player experience. Port management is handled via a registry with a configurable range, which works until you have many builds across many nodes and start hitting conflicts in ways that are annoying to debug. Windows container support exists but is clearly second-class — separate Dockerfiles, separate docs, and the e2e suite doesn't appear to exercise it consistently.