A server is just another resource

Kobblestone teaches the Kubernetes API about Minecraft. A Server says what to run: the server type, game version, storage and resources. The operator builds and looks after everything underneath it.

server.yaml
apiVersion: kobblestone.io/v1alpha1
kind: Server
metadata:
name: my-server
spec:
eula: true
type: Paper
version: "26.2"
storage:
size: 1Gi
resources:
limits:
memory: 2Gi

Everything a Minecraft network needs

Custom resources that snap together like blocks. Start with a single server and add proxies, routing, backups and bots when you need them.

Alpha and highly experimental. All resources are in the v1alpha1 API version. Some features and concepts are not fully implemented yet, and fields and behavior can change between releases, sometimes with manual migration steps. Don't rely on Kobblestone for production worlds yet.

See them in detail

Made for how clusters actually run

  • Gateway API native

    Attach servers, networks and routers to your existing Gateways and Kobblestone manages the TCPRoutes. Plain LoadBalancer Services work too.

  • Sleeps when nobody plays

    Empty servers pause ticking, or hibernate completely and start again as soon as a player connects through a Router. Your nodes stay free for everything else.

  • Backups without downtime

    Live backups coordinate with the running server over RCON. Backups and restores of the same server queue up and run one at a time.

  • Bots you can script

    Bots run Minecraft-Console-Client and are programmed with its own configuration, command scripts and C# scripts, straight from ConfigMaps.

  • Sessions any workload can use

    Signed-in accounts produce a session Secret in a documented format, so your own tools can mount it. The refresh token stays in a separate Secret.

  • Every server flavor

    Vanilla, Paper, Purpur, Folia, Fabric, Quilt, Forge and more, on the game version you choose, each with its own storage and resource limits.

Up and running in three steps

All you need is a Kubernetes cluster, kubectl and helm.

  1. Install the operator

    The Helm chart installs the operator and its custom resources.

    Terminal
    helm repo add kobblestone https://kobblestoneio.github.io/charts
    helm install kobblestone kobblestone/kobblestone \
    --namespace kobblestone-system --create-namespace

    Not using Helm? You can also install the plain manifest with kubectl.

  2. Describe your server

    Accept the EULA, pick a type and version, and give it some storage and memory. The server.yaml above is all it takes.

  3. Apply it and connect

    The first start downloads the server, so give it a moment. Then expose it with a LoadBalancer Service, the Gateway API or a Router.

    Terminal
    kubectl apply -f server.yaml \
    && kubectl wait --for=condition=Running=True server/my-server --timeout=5m

Place your first block.

Kobblestone is free and open source under the Apache 2.0 license. The docs walk you through servers, routing, backups and bots.

Built on the shoulders of docker-minecraft-server, mc-router, docker-mc-backup, docker-mc-proxy, Velocity and Minecraft-Console-Client. Thank you to itzg and every other maintainer.