How to use the CHECK_STORAGE_INIT_COMMAND_ARGS for storage check ?

[susmitaganguli]

Hello,

Am using the storage check for kuberhealthy with the following image:
docker pull chrishirsch/kuberhealthy-storage-check:v0.0.1

Kuberhealthy is deployed in the cluster using Helm
Following are the attributes in the values.yaml
storage:
enabled: true
storageClass: ["csi-sc", "managed-nfs-storage"]
runInterval: 30m
timeout: 10m
securityContext:
runAsNonRoot: true
image:
registry: xxxx
repository: xxx
tag: v0.0.1
extraEnvs:
CHECK_STORAGE_IMAGE: xxx/bitnami/nginx:1.19
CHECK_STORAGE_INIT_IMAGE: xxx/bitnami/nginx:1.19
CHECK_STORAGE_INIT_COMMAND_ARGS: "chmod 777 /data && echo storage-check-ok > /data/index.html && ls -la /data && cat /data/index.html"

I had to include chmod 777 /data because pods created by the storage-check-pvc-csi-sc-init-job errors out with the message:
/bin/sh: 1: cannot create /data/index.html: Permission denied

Although the khcheck storage-check-csi-sc CRD is changed, the storage-check-pvc-csi-sc-init-job yaml doesn't show this change in the arguments and the pod still errors out.

Any suggestions to fix this ?

Thanks and regards,
Susmita