Minecraft proxies allows for a single server to become a network of seamlessly integrated servers.
BungeeCord is the most well known solution in this arena, but several other forks of BungeeCord and new projects such as Velocity have become popular choices.
This chart relies on the itzg/bungeecord container which supports BungeeCord, Waterfall, and Velocity out of the box. It is also designed to allow the use of any other custom proxies with some additional configuration.
This chart creates a single Proxy Pod, Services for the BungeeCord, server and RCON.
- 512 MB of RAM
- Kubernetes 1.4+ with Beta APIs enabled
- PV provisioner support in the underlying infrastructure
Refer to values.yaml for the full run-down on defaults. These are a mixture of Kubernetes and BungeeCord-related directives that map to environment variables in the itzg/bungeecord Docker image.
Specify each parameter using the --set key=value[,key=value] argument to helm install.
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart.
Tip: You can use the default values.yaml
The itzg/bungeecord image stores config and state under /server.
When persistence.dataDir.enabled in values.yaml is set to true PersistentVolumeClaim is created and mounted. In order to enable this functionality
you can change the values.yaml to enable persistence under the sub-sections under persistence.
The config file for the server can be added to the persistent volume manually, or optionally, you can set it by amending the config file path (if your proxy type has a different config path) and pasting your config under bungeecord.configFilePath and bungeeCord.config in values.yaml.
"If persistence is not enabled, an emptyDir volume is first created when a Pod is assigned to a Node, and exists as long as that Pod is running on that node. When a Pod is removed from a node for any reason, the data in the emptyDir is deleted forever."