Description of problem:

Ccurrent default values is Max(unlimited) for pids-limit, If it's set to 1234 for CRI-o value, kata runtime does not take effect. But runC runtime works well.

Version-Release number of selected component (if applicable):

How reproducible:
kata-runtime : 2.4.0-alpha1
crio version 1.23.0
crictl version 1.22.0-72-gcf75c45a
Host kernel:4.18.0-358.el8.x86_64

Steps to Reproduce:
1.change pids_limit option values in crio.conf

1. cat /etc/crio/crio.conf
   [crio.runtime]
   pids_limit = 1234
   cgroup_manager = "systemd"

[crio.runtime.runtimes.kata]
runtime_path = "/usr/local/bin/containerd-shim-kata-v2"
runtime_type = "vm"
runtime_root = "/run/vc"
...

2. Restart crio service
#systemctl restart crio

3.
#crictl pull quay.io/crio/redis:alpine

4.
#crictl runp --runtime kata sandbox_config.json
55607e2a2bfdc4f7cd4080295b4fe15e87d13806f8f5903ed89787e9fb6a11b6

5.

1. crictl create 55607e2a2bfdc container_pids_limit.json sandbox_config.json
   ef40b58858b6194d502e82d5432dcc02b632a9cc7ef99ad8f1a5d7696bba5630

6.

1. crictl start ef40b58858b6194d502e82d5432dcc02b632a9cc7ef99ad8f1a5d7696bba5630
   ef40b58858b6194d502e82d5432dcc02b632a9cc7ef99ad8f1a5d7696bba5630

1. crictl exec -i -t ef40b58858b6194d502e82d5432dcc02b632a9cc7ef99ad8f1a5d7696bba5630 cat /sys/fs/cgroup/pids/pids.max

Actual results:
max

Expected results:
1234

Additional info: