Enhancement - enable additional volume to persist WKO Operator and WKO Webhook pods logs

[Michalski-Piotr]

Hello,
one of our customers reported requirement to collect WKO Operator logs on persistent volume (and distribute later the logs to centralized logs harvester like DynaTrace).

Currently there is no option to add any PV to weblogic-operator for this usecase.
ELK integration is not an option for customer.

Currently logs are stored only on ephemeral storage in /logs directory:

k get all -n wls-operator
NAME                                             READY   STATUS    RESTARTS   AGE
pod/weblogic-operator-6b7d47c86-nxdkj            1/1     Running   14         37d
pod/weblogic-operator-webhook-6974c9749c-4xnhb   1/1     Running   14         37d

NAME                                    TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)             AGE
service/weblogic-operator-webhook-svc   ClusterIP   10.28.7.28   <none>        8083/TCP,8084/TCP   37d

NAME                                        READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/weblogic-operator           1/1     1            1           37d
deployment.apps/weblogic-operator-webhook   1/1     1            1           37d

NAME                                                   DESIRED   CURRENT   READY   AGE
replicaset.apps/weblogic-operator-6b7d47c86            1         1         1       37d
replicaset.apps/weblogic-operator-webhook-6974c9749c   1         1         1       37d




k exec -it -n wls-operator pod/weblogic-operator-6b7d47c86-nxdkj -- /bin/bash -l


[oracle@weblogic-operator-6b7d47c86-nxdkj deployment]$ cd /logs/
[oracle@weblogic-operator-6b7d47c86-nxdkj logs]$ ls
operator0.log  operator0.log.lck  operator1.log  operator2.log	operator3.log
[oracle@weblogic-operator-6b7d47c86-nxdkj logs]$ pwd
/logs
[oracle@weblogic-operator-6b7d47c86-nxdkj logs]$ pwd
/logs
[oracle@weblogic-operator-6b7d47c86-nxdkj logs]$ ls -ltr
total 61988
-rw-r--r-- 1 oracle root        0 May 20 13:47 operator0.log.lck
-rw-r--r-- 1 oracle root 20000254 May 21 04:24 operator3.log
-rw-r--r-- 1 oracle root 20000307 May 21 19:20 operator2.log
-rw-r--r-- 1 oracle root 20000103 May 22 09:48 operator1.log
-rw-r--r-- 1 oracle root  1448948 May 22 10:50 operator0.log

Regards,
Piotr Michalski
Oracle CSS

[jshum2479]

This is a reasonable request, we will look into adding this in future release.

[jshum2479]

The feature has been implemented and will be available in the next release.

[jshum2479]

Several new options are added the the helm chart, they can be used to set the PVC name, log mount point, and actual log directory.

operatorLogPVC specifies the PVC name for persistent storage for operator log files.
operatorLogDir specifies the operator logging directory. The operator will create the directory but the default uid
(oracle:1000) must have permission to create the directory.
operatorLogMount specifies the operator logging volumeMount.

They are all required for persisting file.