Chapter 9. Viewing logs and audit records

Procedure

1. Log in to the OpenShift as a cluster administrator.
2. Click Operators Installed Operators and then click the Red Hat OpenShift AI Operator.
3. Click the DSC Initialization tab.
4. Click the default-dsci object.
5. Click the YAML tab.

6. In the spec section, update the .spec.devFlags.logmode flag with the log level that you want to set.

   apiVersion: dscinitialization.opendatahub.io/v2
   kind: DSCInitialization
   metadata:
     name: default-dsci
   spec:
     devFlags:
       logmode: development

7. Click Save.

Procedure

1. In a terminal window, if you are not already logged in to your OpenShift cluster as a cluster administrator, log in to the OpenShift CLI as shown in the following example:

   $ oc login <openshift_cluster_url> -u <admin_username> -p <password>

2. To access the full content of the changed custom resources, set the OpenShift audit log policy to WriteRequestBodies or a more comprehensive profile. For more information, see Configuring the audit log policy.

3. Fetch the audit log files that are available for the relevant control plane nodes. For example:

   oc adm node-logs --role=master --path=kube-apiserver/ \
     | awk '{ print $1 }' | sort -u \
     | while read node ; do
         oc adm node-logs $node --path=kube-apiserver/audit.log < /dev/null
       done \
     | grep opendatahub > /tmp/kube-apiserver-audit-opendatahub.log

4. Search the files for the DSC and DSCI custom resources. For example:

   jq 'select((.objectRef.apiGroup == "dscinitialization.opendatahub.io"
                   or .objectRef.apiGroup == "datasciencecluster.opendatahub.io")
                 and .user.username != "system:serviceaccount:redhat-ods-operator:redhat-ods-operator-controller-manager"
                 and .verb != "get" and .verb != "watch" and .verb != "list")' < /tmp/kube-apiserver-audit-opendatahub.log