twinki14 / palworld-server-chart

A helm chart for the popular palworld-server-docker Docker image

palworld-server-chart

Official helm chart for the popular Palworld Server Docker docker image

Usage

Helm must be installed to use the charts. Please refer to Helm's documentation to get started.

Once Helm is set up properly, add the repository as follows:

helm repo add palworld-server https://twinki14.github.io/palworld-server-chart

Running helm search repo palworld-server should now display the chart and it's versions

To install the helm chart, use

helm install palworld palworld-server/palworld --create-namespace --namespace palworld-server

Values

You can find the values.yaml summary in the charts directory

palworld-server-chart's Issues

Extra volume mounts on the deployment

I would like to specify an NFS mount to /palworld/backups so that I can back up to NFS. I can implement this, but I'm not sure which approach you'd prefer to handle it. An equally valid usecase might be to simply have a separate PVC for holding backups independent of the main PVC

Currently, the values looks like:

server:
  # Storage definitions related to the palworld-server
  #
  storage:
    external: false
    externalName: ""

    # Keeps helm from deleting the PVC, by default helm does not delete pvcs
    #
    preventDelete: false

    size: 12Gi
    storageClassName: ""

I was thinking something like

server:
  # Storage definitions related to the palworld-server
  #
  storage:
    external: false
    externalName: ""

    # Keeps helm from deleting the PVC, by default helm does not delete pvcs
    #
    preventDelete: false

    size: 12Gi
    storageClassName: ""

    extraVolumes:
    - mountPath: /data
      nfs:
        path: /mnt/data/backups/palworld
        server: ip.of.my.nas

in this vein it should also support any volumes as defined by the k8s api, not just NFS: https://kubernetes.io/docs/reference/kubernetes-api/config-and-storage-resources/volume/#Volume. The only special case being persistentVolumeClaim where an extra size, storageClassName, and preventDelete arguments to create a PVC resource with.

Any thoughts or feelings about this approach?