Max world size inconsistent between Docker image and Helm default values.yaml

Nobody has claimed this yet.

I am switching my Minecraft from my Docker host to my Kubernetes cluster.
On the Docker side, I can't find any defaults for the envvar of the maximum world size, and when `/worldborder get` is run in-game, it shows what I understand to be the Minecraft default of 5999968, or roughly 60 million.
Meanwhile, the Helm Chart's default values.yaml shows that the Helm default is set to `maxWorldSize: 10000`.

This could cause an imported world to be significantly altered to fit the new constraints, which is undesired.
Could the default value for `maxWorldSize` be changed to the Minecraft default or at least be consistent with the behavior observed when the same image is deployed on Docker?

Start with the Helm chart's default values.yaml and trace how maxWorldSize is passed to the container. Compare that with the Docker image's observed default when /worldborder get is run. Done means the Helm default is consistent with the Docker behavior or explicitly uses the Minecraft default, with any relevant chart checks passing.

Written by the indexing model from the issue text.