JMX exporter runs before init containers that prepare the shared volume
Init containers run in the order in which they are specified. In the chart, the very first thing is fetch-jmx-exporter:
In our EFS enabled setup, we also use the additionalInitContainers parameter to fire up a container that uses the init-script.sh to chown on the EFS mountpoint.
If the init-script.sh doesn't run first, then the fetch-jmx-exporter will die.
I think the right path is to make sure that customer provided additionalInitContainers run ahead of the JMX exporter fetch. if that actually impacts some other customer uses then, maybe you can provide a more direct way to just do the chown, possibly with its own init container ordered before everything else.
Seems like this would also be a problem with the NFS permission fixer which runs later in the chain, too?