Consider improving the behaviour of importing keystores from ConfigMap volume which is always mounted read-only.

[khteh]

Problem description

#7362
https://kubernetes.io/docs/concepts/storage/volumes/#:~:text=A%20ConfigMap%20is%20always%20mounted,other%20character%20encodings%2C%20use%20binaryData%20.

The validator fails to start when it runs as k8s STS and tries to import keystores from ConfigMap volume which is always mounted read-ony.

Solution description

As you can see, the ConfigMap is mounted on different path. I don't see any reason why it wouldn't work from it's current working directory which is different from the ConfigMap mount point.

Additional context

No response

[nflaig]

so if I understand the solution you'd like is to write the lock files in current working directory instead of the same directory the keystores are in?

we can probably add a cli flag to configure this