Removing old pidslimit and logSizeMax parameter from Crtcfg

Removing old pidslimit and logSizeMax parameter from Crtcfg as its already deprecated

Removing old pidslimit and logSizeMax parameter from Crtcfg

Author: PoornimaSingour

modules/create-a-containerruntimeconfig-crd.adoc

@@ -50,7 +50,6 @@ $ oc get ctrcfg
 [source,terminal]
 ----
 NAME         AGE
-ctr-pid      24m
 ctr-overlay  15m
 ctr-level    5m45s
 ----
@@ -75,7 +74,7 @@ $ oc get mc | grep container
 ...
 ----
 
-The following example raises the `pids_limit` to 2048, sets the `log_level` to `debug`, sets the overlay size to 8 GB, and sets the `log_size_max` to unlimited:
+The following example sets the `log_level` field to `debug` and sets the overlay size to 8 GB:
 
 .Example `ContainerRuntimeConfig` CR
 [source,yaml]
@@ -89,19 +88,14 @@ spec:
    matchLabels:
      pools.operator.machineconfiguration.openshift.io/worker: '' <1>
  containerRuntimeConfig:
-   pidsLimit: 2048 <2>
-   logLevel: debug <3>
-   overlaySize: 8G <4>
-   logSizeMax: "-1" <5>
-   defaultRuntime: "crun" <6>
+   logLevel: debug <2>
+   overlaySize: 8G <3>
+   defaultRuntime: "crun" <4>
 ----
 <1> Specifies the machine config pool label.
-<2> Optional: Specifies the maximum number of processes allowed in a container.
-<3> Optional: Specifies the level of verbosity for log messages.
-<4> Optional: Specifies the maximum size of a container image.
-<5> Optional: Specifies the maximum size allowed for the container log file. If
-	set to a positive number, it must be at least 8192.
-<6> Optional: Specifies the container runtime to deploy to new containers. The default is `runc`.
+<2> Optional: Specifies the level of verbosity for log messages.
+<3> Optional: Specifies the maximum size of a container image.
+<4> Optional: Specifies the container runtime to deploy to new containers. The default value is `runc`.
 
 .Procedure
 
@@ -120,10 +114,8 @@ spec:
    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.
@@ -195,15 +187,13 @@ sh-4.4# chroot /host
 +
 [source,terminal]
 ----
-sh-4.4# crio config | egrep 'log_level|pids_limit|log_size_max'
+sh-4.4# crio config | grep 'log_level'
 ----
 +
 .Example output
 +
 [source,terminal]
 ----
-pids_limit = 2048
-log_size_max = -1
 log_level = "debug"
 ----
 

modules/set-the-default-max-container-root-partition-size-for-overlay-with-crio.adoc

@@ -8,7 +8,7 @@
 
 The root partition of each container shows all of the available disk space of the underlying host. Follow this guidance to set a maximum partition size for the root disk of all containers.
 
-To configure the maximum Overlay size, as well as other CRI-O options like the log level and PID limit, you can create the following `ContainerRuntimeConfig` custom resource definition (CRD):
+To configure the maximum Overlay size, as well as other CRI-O options like the log level, you can create the following `ContainerRuntimeConfig` custom resource definition (CRD):
 
 [source,yaml]
 ----
@@ -21,7 +21,6 @@ spec:
    matchLabels:
      custom-crio: overlay-size
  containerRuntimeConfig:
-   pidsLimit: 2048
    logLevel: debug
    overlaySize: 8G
 ----