Kubernetes · Live Cluster · Autoscaling Demo

Three card-game bots.
One cluster that reacts to you.

The bots from the Flip7 game on this site play against each other as fast as the CPU allows — each simulated game is real computation. You control the demand below. Kubernetes adds and removes simulation pods to keep up, on a live single-node cluster, not a recording. Try killing a pod mid-run and watch it come back.


Demand

Each demand unit is a load-generator pod hammering the simulation service with requests. Pick a level, hit Start, and the autoscaler reacts when CPU crosses its target. Table size changes what every simulated game costs — an 18-bot game is several times the computation of a 4-bot game.

Bots per table
table: 4 bots
Demand level
demand: 0

Idle for 5 minutes and demand resets to 0 on its own. The whole namespace is capped by ResourceQuota — this demo cannot eat the server, by design rather than by hope.

Simulation pods


The score

Three bot personalities from the live game: Tactician stops at three number cards, Gambler flips until six, Wildcard flips a coin. Every game seats a random mix of them, and the table size changes the odds — compare how each strategy holds up at a 4-bot, 8-bot and 18-bot table. Your session counts games since you opened this page; historic is everything this cluster has ever played.

Your session

games
0
games/sec (all)
0

All-time historic

games
0
busts/game
flip7s/game