Starting from version 5.0 fails

[unnamedsos]

Describe the bug
If we start using the charts from version 5.0 we get error permission denied during the command { echo "started" > ${BACKUP_DIR}/${TIMESTAMP}.state }
we are just saving to the pvc and nothing else.

however, if we start with version 4.2 and do our first db backup, and THEN upgrade to the version 5.0 it works O.o

Version of Helm and Kubernetes:
rancher 4.2

Client Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.8", GitCommit:"ec6eb119b81be488b030e849b9e64fda4caaf33c", GitTreeState:"clean", BuildDate:"2020-03-12T21:00:06Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.4", GitCommit:"8d8aa39598534325ad77120c120a22b3a990b5ea", GitTreeState:"clean", BuildDate:"2020-03-12T20:55:23Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/amd64"}
Helm Version:
3

Which version of the chart:
4.2->5

What happened:
read write to backup folder not working as it should with the current user ?

What you expected to happen:
to be able to write to backup folder as new installation of version 5.0

How to reproduce it (as minimally and precisely as possible):
clean isntall from version chart 5.0 and only save locally

allDatabases:
enabled: "false"
debug: "true"
mysql:
db: "somedb"
existingSecret: "somedb-auth-secret"
host: "somedb-mysql"
port: "3306"
username: "root"
persistentVolumeClaim: "somedb-backup"
schedule: "*/4 * * * *"
securityContext:
enabled: "false"

Anything else we need to know: