Cx has mentioned:

The RH team has built a custom solution for Log Linking based on request from Adobe. Adobe already uses a similar solution for the Adobe-managed K8s clusters. In order to achieve feature/configuration parity and avoid application owners from specifying different configs for ROSA/ARO clusters and Adobe k8s clusters, we would like to ensure that logs are structured in a particular format. Application logs should be created under logging-volume directory similarly to how Adobe structures these files today. At Adobe: ls la /logging-volume/ -rw-r---. 1 root root 58640147 Oct 4 15:48 1f19a37e793996cc04226916690b832b3aa22475e73020cd85e3942148a6efba.log On OpenShift the file structure is different: # ls -la -R /logging-volume/ /logging-volume/: total 0 drwxrwsrwx. 3 root daemon 18 Sep 26 19:10 . dr-xr-xr-x. 1 root root 61 Sep 26 19:10 .. drwxr-xr-x. 4 root root 191 Sep 26 19:10 logs /logging-volume/logs: total 0 drwxr-xr-x. 4 root root 191 Sep 26 19:10 . drwxrwsrwx. 3 root daemon 18 Sep 26 19:10 .. lrwxrwxrwx. 1 root root 16 Sep 26 19:10 1141575e9722b9c7cad7d20d7d61adcb837a5ed169e6ab7202b7d434848d0457 -> fluent-bit/0.log lrwxrwxrwx. 1 root root 21 Sep 26 19:10 3a124d8ce6f1f0e1eb53a4a52e2a97d6d2c4381daee4d27c3b0d333bf81da524 -> sa-spark-driver/0.log drwxr-xr-x. 2 root root 19 Sep 26 19:10 fluent-bit drwxr-xr-x. 2 root root 19 Sep 26 19:10 sa-spark-driver /logging-volume/logs/fluent-bit: total 4 drwxr-xr-x. 2 root root 19 Sep 26 19:10 . drwxr-xr-x. 4 root root 191 Sep 26 19:10 .. -rw-----. 1 root root 3846 Sep 26 19:10 0.log /logging-volume/logs/sa-spark-driver: total 264 drwxr-xr-x. 2 root root 19 Sep 26 19:10 . drwxr-xr-x. 4 root root 191 Sep 26 19:10 .. -rw------. 1 root root 267206 Sep 26 19:40 0.log Key differences: * OpenShift adds additional subdirectories, while Adobe has all log files top level. * OpenShift stores fluent-bit files as well, while Adobe only stores application-level files.

Cx is using ROSA(Red Hat Openshift on AWS). With cluster id:  9914e47f-a541-4f80-bf83-1a56498f32ad, fea240c4-cbac-4c0e-8ed9-073772374c43, eb5c4da5-dbf9-405e-b54a-f663a442ec96

i tried to mention the issue type as RFE, but Jira is not accepting this type. If the issue type is mentioned incorrectly kindly mention the correct one.

We had an internal discussion: https://issues.redhat.com/browse/OHSS-27752

Let us know your thoughts on this.

Thanks in advance.