feat: Add the option to specify if the volumePermissions chmod command should be recursive or not. Add volumePermissions to the PostgreSQL chart
Both the PostgreSQL and the Synapse pods fail to start due to write permissions being denied, in certain situations, even when enabling "volumePermissions".
While "volumePermissions" helps by running a chmod on the provisioned filesystem, it fails because Oracle places a .snapshot directory on the filesystem's root.
Same problem happens with certain Bitnami charts:: https://github.com/bitnami/charts/issues/31612
chown: /synapse/data/.snapshot: Read-only file system
chown: /synapse/data/.snapshot: Read-only file system
In case of the PostgreSQL pod, I added a volumePermissions entry to values.yaml, which are passed to the Bitnami chart. In this case, all works fine.