Ensuring File Conflict Management for mod_auth_openidc on OpenShift

[ysdkisk]

Hello,

I am contacting you with an inquiry about the file storage type for the mod_auth_openidc cache. We plan to deploy an httpd container on OpenShift. Our intention is to store the mod_auth_openidc output files in a PersistentVolumeClaim. However, we are concerned that using a Deployment might lead to multiple Pods operating on shared storage, which could result in file name conflicts.

The documentation mentions using a "temp directory - possibly a shared file system across multiple Apache processes and/or servers." Could you please confirm whether this setup avoids file conflicts entirely? If conflicts are possible, could you explain the potential issues and provide your recommendations?

Thank you for your assistance.

Best regards,
Keisuke Yasuda

[zandbelt]

for individual servers - i.e. not working together as a single logical cluster - you can configure a different OIDCCacheDir on each instance to avoid conflicts

[ysdkisk]

Thank you for your previous response. In the case of a single system composed of three web servers under a load balancer, should these three web servers be considered as a single logical cluster?

[zandbelt]

yes