To increase the detail in operator logs for troubleshooting, the operator's runtime configuration for logging verbosity must be changed. A standard and flexible method for managing such configurations in Kubernetes and OpenShift is through a ConfigMap. By creating or modifying a ConfigMap with specific keys (e.g., LOGLEVEL: TRACE or LOGLEVEL: DEBUG) and ensuring the operator's deployment is configured to consume these values, an administrator can dynamically increase the log detail without rebuilding or directly patching the core deployment object.

A. The logs command is used to view existing logs that have already been generated by the pod; it does not influence the level of detail in future log entries.

B. The oc adm must-gather command is a diagnostic tool for collecting a wide range of cluster information, including logs, for offline analysis. It does not configure runtime logging levels.

C. Increasing Ansible log verbosity affects the output of Ansible playbooks during their execution, not the runtime logs of the operators that are deployed by those playbooks.

1. IBM Cloud Pak for Business Automation v21.0.3 Documentation: In the section for troubleshooting specific components

the method for increasing log verbosity is described. For example

for the IBM Business Automation Navigator operator

the documentation states: "You can set the log level for the operator by editing the ibm-fncm-operator configmap." This confirms that configuring a ConfigMap is the correct procedure.

Source: IBM Documentation

"Setting the log level for the operator" (for IBM Business Automation Navigator).

2. IBM Cloud Pak for Business Automation v21.0.3 Documentation: When troubleshooting the CP4BA operator

the guidance often involves adjusting logging levels. The documentation for the Content Platform Engine operator troubleshooting states: "To get more details from the operator logs

you can change the log level by adding an environment variable to the operator deployment." A ConfigMap is a primary method for managing such environment variables externally.

Source: IBM Documentation

"Troubleshooting an operator installation" (for IBM FileNet Content Manager).