Running a Minecraft server is easy. Running a handful of them, behind a proxy, with backups, on infrastructure you actually trust, is where it gets messy: shell scripts, cron jobs, a VM nobody wants to touch.
Kubernetes already solves most of this for every other workload. Kobblestone brings Minecraft along.
Minecraft as a first-class citizen
Kobblestone is an operator. It adds custom resources to your cluster that describe Minecraft infrastructure, and it does the work of turning them into running pods, services, volumes and jobs.
apiVersion: kobblestone.io/v1alpha1kind: Servermetadata: name: my-serverspec: eula: true type: Paper version: '26.2' storage: size: 1GiThat is a whole server. Apply it, and it shows up in kubectl get servers like anything else.
What is in the box
- Server for every common server type, with optional auto sleep while nobody is online.
- Network to put several servers behind a Velocity proxy.
- Router and Route to send players to the right place by hostname, through one endpoint.
- BackupRepo, Backup and Restore for live or offline backups to S3 or a volume.
- Command and CommandGroup to run RCON commands declaratively.
- Account and Bot for signed-in Minecraft-Console-Client bots you program with scripts.
Servers can be exposed through the Gateway API, a LoadBalancer Service, or a Router.
Standing on giants
Kobblestone would not exist without itzg’s container images for Minecraft servers, routing, backups and proxies, or without Minecraft-Console-Client. Thank you.
Try it
Install the operator with the Helm chart, then follow the getting started guide. If something breaks or you are missing a feature, open an issue. We would love to hear what you build.
