CRI-O's config fields LogSizeMax and PidsLimit were introduced before the kubelet supported similar values. However, now the kubelet does, and keeping the values around only adds confusion on which should be specified. To reduce confusion, CRI-O should deprecate the fields in favor of the kubelet's.

Since both of these fields correspond to fields in the ContainerRuntimeConfig, the ctrcfg will have to learn how to translate between the two values (cri-o's and kubelets) and set the correct value in the kubelet instead. In the long term, I think deprecating the ctrcfg options will be needed as well.