Minecraft is a game about placing blocks and going on adventures.
This chart creates a single Minecraft Pod, plus Services for the Minecraft server and RCON.
To install the chart with the release name my-release, read the Minecraft EULA run:
$ helm install –name my-release –set minecraftServer.eula=true stable/minecraft
This command deploys a Minecraft dedicated server with sensible defaults.
Tip: List all releases using helm list
To uninstall/delete the my-release deployment:
$ helm delete my-release
The command removes all the Kubernetes components associated with the chart and deletes the release.
Refer to values.yaml for the full run-down on defaults. These are a mixture of Kubernetes and Minecraft-related directives that map to environment variables in the itzg/minecraft-server Docker image.
Specify each parameter using the –set key=value[,key=value] argument to helm install. For example,
$ helm install –name my-release \
–set minecraftServer.eula=true,minecraftServer.Difficulty=hard \
stable/minecraft
Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,
$ helm install –name my-release -f values.yaml stable/minecraft
Tip: You can use the default values.yaml
The itzg/minecraft-server image stores the saved games and mods under /data.
By default a PersistentVolumeClaim is created and mounted for saves but not mods. In order to disable this functionality you can change the values.yaml to disable persistence under the sub-sections under persistence.
“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.”
Tell us about a new Kubernetes application
Never miss a thing! Sign up for our newsletter to stay updated.
Discover and learn about everything Kubernetes
