Logrotate error in model api logs

Issue:  
Model instance logs are polluted with large number of error messages from logrotate. 
Example:

time="2022-11-17T11:03:00Z" level=info msg=starting iteration=0 job.command="logrotate /home/domino/logrotate.conf --state /home/domino/logrotate.state" job.position=0 job.schedule="*/1 * * * *"
time="2022-11-17T11:03:00Z" level=info msg=starting iteration=0 job.command="logrotate /home/domino/logrotate.conf --state /home/domino/logrotate.state" job.position=0 job.schedule="*/1 * * * *"
time="2022-11-17T11:03:00Z" level=info msg="error: stat of /logs/*.log failed: No such file or directory" channel=stderr iteration=0 job.command="logrotate /home/domino/logrotate.conf --state /home/domino/logrotate.state" job.position=0 job.schedule="*/1 * * * *"
time="2022-11-17T11:03:00Z" level=info msg="error: stat of /logs/*.log failed: No such file or directory" channel=stderr iteration=0 job.command="logrotate /home/domino/logrotate.conf --state /home/domino/logrotate.state" job.position=0 job.schedule="*/1 * * * *"
time="2022-11-17T11:03:00Z" level=error msg="error running command: exit status 1" iteration=0 job.command="logrotate /home/domino/logrotate.conf --state /home/domino/logrotate.state" job.position=0 job.schedule="*/1 * * * *"
time="2022-11-17T11:03:00Z" level=error msg="error running command: exit status 1" iteration=0 job.command="logrotate /home/domino/logrotate.conf --state /home/domino/logrotate.state" job.position=0 job.schedule="*/1 * * * *"

Scope:
This problem affects Domino versions 5.1.x and 5.2.x . 

Root Cause:
This problem occurs due to a change in the logging facilities in the Model API  and has been fixed in
Domino version 5.3 and up. 

Resolution: 
To fix this problem in versions 5.1.x and 5.2.x you can edit the config map for pod logrotate-config
and add a parameter "missingok" to the logrotate configuration block.  The namespace for the 
configmap should be "compute" . 

Example: 

kubectl edit configmap -n <DOMINO_NAMESPACE> logrotate-config

Adding the additional option to the existing logrotate configuration: 
(Note this is an example from a test deployment, you will only need to add missingok in to your existing config map)

# Please edit the object below. Lines beginning with a '#' will be ignored,
# and an empty file will abort the edit. If an error occurs while saving this file will be
# reopened with the relevant failures.
#
apiVersion: v1
data:
logrotate.conf: |
/logs/*.log {
nocopytruncate
nocompress
rotate 1
size 50M
missingok
}
kind: ConfigMap
metadata:
annotations:
meta.helm.sh/release-name: nucleus
meta.helm.sh/release-namespace: domino-platform
creationTimestamp: "2022-09-12T14:25:00Z"
labels:
app.kubernetes.io/instance: nucleus
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/name: nucleus
helm.sh/chart: nucleus-0.80.9
name: logrotate-config
namespace: domino-compute
resourceVersion: "19089887"
uid: 7b6463e9-ed0a-4743-bb17-251212c4b8a8