- Kubeletconfig with setting containerLogMaxFiles to '1' would cause MCP in "updating" state forever. Kubelet fails with the specified error after restarting the node manually.
~~~
Nov 27 19:47:55 k8s01-5pw7x-infra-kjvkf kubenswrapper[27544]: E1127 19:47:55.246643   27544 run.go:74] "command failed" err="failed to run Kubelet: failed to create kubelet: failed to initialize container log manager: invalid MaxFiles 1, must be > 1"
Nov 27 19:47:55 k8s01-5pw7x-infra-kjvkf systemd[1]: kubelet.service: Main process exited, code=exited, status=1/FAILURE

~~~

- Kubeletconfig with setting containerLogMaxFiles to '1' would cause failure in starting the kubelet service,
~~~ 
$ cat crio-kubeconfig.yaml
apiVersion: machineconfiguration.openshift.io/v1
kind: KubeletConfig
metadata:
name: cr-logrotation
spec:
kubeletConfig:
  containerLogMaxFiles: 1
  containerLogMaxSize: 390Mi
machineConfigPoolSelector:
  matchLabels:
    custom-kubelet-log: logrotation
 ~~~

    - It should not allow to create kubeletconfig with unsupported value.

- Replacing CR with "containerLogMaxFiles" value to "2", will allow starting kubelet service.