mc-router
mc-router copied to clipboard
Routes Minecraft client connections to backend servers based upon the requested server address
Bumps [k8s.io/api](https://github.com/kubernetes/api) from 0.18.5 to 0.24.4. Commits 44d27eb Update dependencies to v0.24.4 tag 0bf1867 Revert "Introduce APIs to support multiple ClusterCIDRs (#108290)" 2de6996 Merge pull request #109241 from ravisantoshgudimetla/sts-ar-optional 7734d26...
Bumps [k8s.io/client-go](https://github.com/kubernetes/client-go) from 0.18.5 to 0.24.4. Commits 3e73df6 Update dependencies to v0.24.4 tag 5e66e32 Merge pull request #111274 from Abirdcfly/automated-cherry-pick-of-#111235-up... 37577f3 fix a possible panic because of taking the address...
Bumps [k8s.io/apimachinery](https://github.com/kubernetes/apimachinery) from 0.18.5 to 0.24.4. Commits 97e5df2 fix remove implicit copy of a lock 6550efd Merge pull request #109102 from liggitt/darwin-tls 00f0711 Merge pull request #109031 from Jefftree/openapiv3beta 53a85ef...
Docker swarm support is added (#60) and it should work with non-swarm deployments as well, however if you start it with --in-docker-swarm you get this: time="2022-08-15T17:23:00Z" level=fatal msg="Unable to start...
Rather than using the hostname of a docker image that is on the same network, is it possible to use the LAN ip of another machine that is already hosting...
I'm not actually sure if there's anything the router can do about this, but I figured I'd see if anyone else has run into this. I have DNS setup like...
./mc-router -debug -connection-rate-limit 100 --mapping "mc.sientys.cloud=10.0.0.1:25566,mc.goldensmp.net=10.20.220.13:25565" I am running mc-router standalone and I keep getting WARN[0004] Unable to find registered backend serverAddress=mc.sientys.cloud same with IPs and all other domains.
Here is my docker-compose, running on a docker swarm, domain is just a placeholder. One of the hosts is 172.16.100.56 ``` version: '3.4' services: router: image: itzg/mc-router ports: - 25565:25565...
While searching for a way to forward the client IP I found #22 (issue: #13) which has already been released, but the README doesn't contain any info about it. First...
With the introduction of #29 for #21, a possible future enhancement on that front, for anyone interested in contributing here, is this: Now that `mc-router` can "wake up" back-ends, the...