IPCEICIS-2952 #20
Loading…
Reference in a new issue
No description provided.
Delete branch "IPCEI-2952"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
see https://jira.telekom-mms.com/browse/IPCEICIS-2952
IPCEI-2952to IPCEICIS-2952echo "logrotate❌100:" >> /etc/group
There are multiple components needed for the logging of OpenBao audits:
openbao-logging.yaml - References the openbao-logging directory.
openbao-logging/create-logging-directory.yaml - DaemonSet that creates a directory on the node's hostPath. Since this task has to be done by a priviledged user and we have a non-root policy for pods which doesn't apply to DeamonSets this appears to be the only possible solution.
openbao-logging/logrotate-configmap.yaml - Consists of the logrotate.conf file which speciefies how the logrotation should happen. It's mounted to the CronJob.
openbao-logging/logrotate-cronjob.yaml - The definition of the CronJob which runs every hour.
openbao-logging/passwd-user-configmap.yaml - Needed for identifying as the user openbao:100 which is required to …
openbao-logging/sidecar-script-configmap.yaml - Responsible for setting up two scripts: start.sh - for starting a server listening on the port 3030 for the signal from the CronJob; sidecar.sh - for sending the SIGHUP to openbao.
openbao-logging/sidecar-script-service.yaml - The service for the sidecar container inside the openbao-0 pod
openbao/values.yaml - Sets up a sidecar container called "sidecar" which is allowed to access the bao process and enables a File Audit Device one the node's hostPath.
Pull request closed