docker-test/ does the same, so what it proves is what a rented network would do rather than what Kubernetes did.
It brings up a standalone MongoDB, a Redis, two shards, a hub and a Velocity proxy on one Docker network, and none of the shards are declared in velocity.toml — they register themselves, which is the piece that replaced the Kubernetes operator.
Running it
Needs Docker and about 6 GB of memory.localhost:25577. setup.sh downloads the pinned Paper and Velocity builds, generates one world and copies it to each shard, writes the configuration, and assembles a compose file. It is idempotent.
What it checks
The plugins enable
On the real Paper, Velocity and Java versions, which is the single most likely thing to differ on a host you do not control.
A standalone database works
The read concern adapts and the log says which it chose.
Self-registration
Both shards appear on the proxy from their address alone.
Restart and recovery
Stopping a shard withdraws it and the proxy unregisters it; starting it brings the topology back.
Real clients
docker-test/bot drives the network with real Minecraft 26.2 and 26.3 clients. Released mineflayer stops at 26.1, so its setup.sh installs pinned versions and adds the newer protocols from PrismarineJS’s open pull requests, plus what a 26.3 server enforces that nothing upstream does yet.
/tpa, /back, /rtp — then quits, rejoins and checks nothing exists twice. The client version must match the servers’, and the proxy needs both seamless settings on.