{"repo":"qumine/ingress-controller","free":true,"listed":false,"github":"https://github.com/qumine/ingress-controller","clone":"git clone https://github.com/qumine/ingress-controller.git","description":"Route Minecraft connection to backends based on the requested hostname of the server. Forget about using multiple IPs or ports just for minecraft.","language":"Go","stars":35,"topics":["minecraft","minecraft-server","docker","kubernetes","kubernetes-ingress","ingress","minecraft-servers","kubernetes-ingress-controller","minecraft-proxy","reverse-proxy"],"license":"AGPL-3.0","category":"deployment-docker-iac","readme_excerpt":"QuMine - Ingress --- Kubernetes ingress controller for routing Minecraft connections based on the requested hostname Usage Kubernetes HELM Charts can be found here: qumine/charts Ingress The ingress should be run as a daemonset on all of your outwards facing nodes. By default the ingress should run fine without customization, but if you need to the behaviour of the ingress can be customized by setting a couple of arguments. Here is the full list of available arguments. All configuration options can also be set via environment variables Upstream Services To enable a service to be discovered by the ingress it needs to have the annotations. Optionaly you can set the annotation to define which port will be used for the minecraft connection. Outside of Kubernetes If you want to run the ingress outside of kubernetes you can do so by providing the flag or environment variable. Keep in mind tho that the routing towards the internal kubernetes services needs to be configured. Development Perfrom a Snapshot release locally","default_branch":null,"files":null,"tree":[],"storefront":"/r/qumine","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/qumine/ingress-controller/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}