50ff433fd0a946b0151026c1208cba1d3f11db0d
Routes Minecraft client connections to backend servers based upon the requested server address.
Usage
Flags:
--help Show context-sensitive help (also try --help-long
and --help-man).
--port=25565 The port bound to listen for Minecraft client
connections
--api-binding=API-BINDING The host:port bound for servicing API requests
--mapping=MAPPING ... Mapping of external hostname to internal server
host:port
REST API
GET /routesRetrieves the currently configured routesPOST /routesRegisters a route given a JSON body structured like:
{
"serverAddress": "CLIENT REQUESTED SERVER ADDRESS",
"backend": "HOST:PORT"
}
DELETE /routes/{serverAddress}Deletes an existing route for the givenserverAddress
Example kubernetes deployment
- Declares an
mc-routerservice that exposes a node port 25565 - Declares a service account with access to watch and list services
- Declares
--in-kube-clusterin themc-routercontainer arguments - Two "backend" Minecraft servers are declared each with an
"mc-router.itzg.me/externalServerName"annotation that declares their external server name
kubectl apply -f https://raw.githubusercontent.com/itzg/mc-router/master/docs/k8s-example-auto.yaml
Notes
- This deployment assumes two persistent volume claims:
mc-stableandmc-snapshot - I extended the allowed node port range by adding
--service-node-port-range=25000-32767to/etc/kubernetes/manifests/kube-apiserver.yaml
Description
Fork of itzg/mc-router with automc extensions (Postgres LISTEN/NOTIFY route source, login-state kick to waker). Soft fork — upstream/main tracked verbatim, automc-specific code in internal/automc/.
Languages
Go
99.6%
Dockerfile
0.3%
