Merge pull request #88598 from mburke5678/wmco-debug-logging

Make debugLogging non-default

Author: mburke5678

modules/wmco-configure-debug-logging.adoc

@@ -0,0 +1,40 @@
+// Module included in the following assemblies:
+//
+// windows_containers/enabling-windows-container-workloads.adoc
+
+:_mod-docs-content-type: CONCEPT
+[id="wmco-configure-debug-logging_{context}"]
+= Configuring debug-level logging for the Windows Machine Config Operator
+
+By default, the Windows Machine Config Operator (WMCO) is configured to use the `info` log level. You can change the log level to `debug` by editing the WMCO `Subscription` object. 
+
+.Procedure
+
+. Edit the `windows-machine-config-operator` subscription in the `windows-machine-config-operator` namespace by using the following command:
++
+[source,terminal]
+----
+$ oc edit subscription windows-machine-config-operator -n openshift-windows-machine-config-operator
+----
+
+. Add the follwing parameters to the `.spec.config.env` stanza:
++
+[source,yaml]
+----
+apiVersion: operators.coreos.com/v1alpha1
+kind: Subscription
+# ...
+  name: windows-machine-config-operator
+  namespace: openshift-windows-machine-config-operator
+# ...
+spec:
+# ...
+  config:
+    env:
+    - name: ARGS <1>
+      value: --debugLogging <2>
+----
+<1> Defines a list of environment variables that must exist in all containers in the pod.
+<2> Specifies the `debug` level of verbosity for log messages.
+
+You can revert to the default `info` log level by removing the `name` and `value` parameters that you added. 

windows_containers/enabling-windows-container-workloads.adoc

@@ -51,6 +51,8 @@ include::modules/installing-wmco-using-cli.adoc[leveloffset=+2]
 
 include::modules/configuring-secret-for-wmco.adoc[leveloffset=+1]
 
+include::modules/wmco-configure-debug-logging.adoc[leveloffset=+1]
+
 include::modules/wmco-cluster-wide-proxy.adoc[leveloffset=+1]
 
 .Additional resources