anchor.diff:  worker  rendered-worker-169  False    True      False     3             1                  1                    0                     9h
   ----
   
  -. Open an `oc debug` session to a worker node and run `chroot /host`.
  -
  -. Verify the changes by running:
  -+
  -[source,terminal]
  -----
  -$ crio config | egrep 'log_level|pids_limit'
  +. Verify that the settings were applied in CRI-O:
  +
  +.. Open an `oc debug` session to a node in the machine config pool and run `chroot /host`.
  ++
  +[source, terminal]
  +----
  +$ oc debug node/<node_name>
  +----
  ++
  +[source, terminal]
  +----
  +sh-4.4# chroot /host
  +----
  +
  +.. Verify the changes in the `crio.conf` file:
  ++
  +[source,terminal]
  +----
  +sh-4.4# crio config | egrep 'log_level|pids_limit|log_size_max'
   ----
   +
   .Example output
  
positive.code: [id="create-a-containerruntimeconfig_{context}"]
  = Creating a `ContainerRuntimeConfig` CR to edit CRI-O parameters
  
  The `ContainerRuntimeConfig` custom resource definition (CRD) provides a structured way of changing settings associated with the {product-title} CRI-O runtime. Using a `ContainerRuntimeConfig` custom resource (CR), you select the configuration values you want and the MCO handles rebuilding the `crio.conf` and `storage.conf` configuration files.
  
  Parameters you can set in a `ContainerRuntimeConfig` CR include:
  
  * **PIDs limit**: Sets the maximum number of processes allowed in a container. By default, the limit is set to 1024 (`pids_limit = 1024`).
  * **Log level**: Sets the level of verbosity for log messages. The default is `info` (`log_level = info`). Other options include `fatal`, `panic`, `error`, `warn`, `debug`, and `trace`.
  * **Overlay size**: Sets the maxim size of a container image. The default is 10 GB.
  * **Maximum log size**: Sets the maximum size allowed for the container log file. The default maximum log size is unlimited (`log_size_max = -1`). If it is set to a positive number, it must be at least 8192 to not be smaller than  the `conmon` read buffer. Conmon is a program that
  monitors communications between a container manager (such as Podman or CRI-O) and the OCI runtime (such as runc or crun) for a single container.
  
  The following procedure describes how to change CRI-O settings using the `ContainerRuntimeConfig` CR.
  
  .Procedure
  
  . To raise the `pidsLimit` to 2048, set the `logLevel` to `debug`, and set the `overlaySize` to 8 GB, create a CR file (for example, `overlay-size.yaml`) that contains that setting:
  +
  [source,yaml]
  ----
  $ cat << EOF > /tmp/overlay-size.yaml
  apiVersion: machineconfiguration.openshift.io/v1
  kind: ContainerRuntimeConfig
  metadata:
  
negative.code: spec:
   machineConfigPoolSelector:
     matchLabels:
       pools.operator.machineconfiguration.openshift.io/worker: '' <1>
   containerRuntimeConfig:
     pidsLimit: 2048 <2>
     logLevel: debug <3>
     overlaySize: 8G <4>
     logSizeMax: "-1" <5>
  ----
  <1> Specifies the machine config pool label.
  <2> Optional: Specifies the level of verbosity for log messages.
  <3> Optional: Specifies the maximum size allowed for the container log file. If set to a positive number, it must be at least `8192`.
  <4> Optional: Specifies the maximum size of a container image. 
  <5> Optional: Specifies the maximum number of processes allowed in a container.
  	
  .Procedure
  
  To change CRI-O settings using the `ContainerRuntimeConfig` CR:
  
  . Create a YAML file for the `ContainerRuntimeConfig` CR:
  +
  [source,yaml]
  ----
  apiVersion: machineconfiguration.openshift.io/v1
  kind: ContainerRuntimeConfig
  metadata:
   name: overlay-size
  spec:
   machineConfigPoolSelector:
     matchLabels:
       pools.operator.machineconfiguration.openshift.io/worker: '' <1>
   containerRuntimeConfig: <2>
     pidsLimit: 2048
     logLevel: debug
     overlaySize: 8G
     logSizeMax: "-1"
  ----
  <1> Specify a label for the machine config pool that you want you want to modify.
  <2> Set the parameters as needed.  
  
  . Create the `ContainerRuntimeConfig` CR:
  +
  [source,terminal]
  ----
  $ oc create -f <file_name>.yaml
  ----
  
  . Verify that the CR is created:
  +
  [source,terminal]
  ----
  $ oc get ContainerRuntimeConfig
  ----
  +
  .Example output
  [source,terminal]
  ----
  NAME           AGE
  overlay-size   3m19s
  ----
  
  . Check that a new `containerruntime` machine config is created:
  +
  [source,terminal]
  ----
  $ oc get machineconfigs | grep containerrun
  ----
  +
  .Example output
  [source,terminal]
  ----
  99-worker-generated-containerruntime   2c9371fbb673b97a6fe8b1c52691999ed3a1bfc2  3.1.0  31s
  ----
  
  . Monitor the machine config pool until all are shown as ready:
  +
  [source,terminal]
  ----
  