Players sharing a Minecraft world need a server that keeps the world available and preserves their progress between sessions. This historical chart packaged a Minecraft Java server using the community itzg container image. Kubernetes could run the process and expose its game port, but the world files, game version and any modifications remained important application state. It is a game-server deployment package, not a Minecraft distribution published by Mojang.
Current guidance
The recovered stable chart’s values identify itzg/minecraft-server. This is a community container wrapper, not a Kubernetes distribution published by Mojang. Current image documentation says it downloads a Minecraft Java server at startup and allows explicit VERSION and TYPE selection; leaving defaults can change the downloaded game version independently of the chart.
Pin the container and game version together, including the Java runtime and any mod loader or plugins. Persist the documented /data directory and take a consistent world backup before upgrades. A successful pod restart is not proof that an older world remains compatible after a game-version change.
Keep server administration and RCON access separate from the public game port, and grant operator privileges only to intended players. Review the game’s EULA before accepting it; a sample chart cannot accept it for a server owner. Test a restored world and controlled shutdown, and avoid mounting one writable world into competing server replicas. The historical memory minimum is not a sizing recommendation for modern versions or modpacks.
Historical upstream link check · 2026-10-09
The recorded upstream address responded successfully (HTTP 200) on 2026-10-09. GitHub confirms that helm/charts is archived: this is a historical chart distribution, not evidence that the application itself is retired. Link availability does not certify the historical installation instructions or current security support.
Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.
Historical Kubedex content
Preserved for context. Commands, versions, prices and results below reflect the original research.
Minecraft is a game about placing blocks and going on adventures.
Introduction
This chart creates a single Minecraft Pod, plus Services for the Minecraft server and RCON.
Prerequisites
- 512 MB of RAM
- Kubernetes 1.4+ with Beta APIs enabled
- PV provisioner support in the underlying infrastructure
Installing the Chart
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
Uninstalling the Chart
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.
Configuration
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
Persistence
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.”
Sources & further reading
Spotted something that needs another look?
Help improve this page →