Data node readiness/liveness probe fails for new Uber Chart

[juv]

Hi @kimoonkim
I am trying the commits in your uber chart repository.
The data nodes fail because the pods apparently lack permissions to run the readiness/liveness probe.

 Readiness probe failed: rpc error: code = 2 desc = oci runtime error: exec failed: container_linux.go:247: starting container process caused "exec: \"/dn-scripts/check-status.sh\": permission denied"
11 times in the last 16 minutes 

Note that I had to remove the securityContext from the data node. Is this required? I am not allowed to submit pods with that securityContext in my cluster.

          securityContext:
            privileged: true