When a runtime is specified as default_runtime_name, the cri_handler of the runtime cannot be used.

[ToviHe]

I have a config.toml configuration as follows

[plugins."io.containerd.grpc.v1.cri".containerd]
   default_runtime_name = "kata"
    [plugins."io.containerd.grpc.v1.cri".containerd.runtimes]
        [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc]
           runtime_type = "io.containerd.runc.v2"
        [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.kata]
           runtime_type = "io.containerd.kata.v2"
           cri_handler = "cc"

When I create a new pod, for example

cat <<-EOF | kubectl apply -f -
apiVersion: node.k8s.io/v1
kind: RuntimeClass
metadata:
  name: kata
handler: kata
EOF

cat <<-EOF | kubectl apply -f -
apiVersion: v1
kind: Pod
metadata:
  name: nginx-sandbox
spec:
  runtimeClassName: kata
  containers:
  - image: docker.io/zhouliang121/alpine-84688df7-2c0c-40fa-956b-29d8e74d16c1-gcm:latest
    command:
      - top
    imagePullPolicy: IfNotPresent
    name: alpine
  restartPolicy: Never
EOF

It was found that the pod startup uses the cri_handler="cc" feature.
But when I deleted the runtimeClassName:kata corresponding to the pod, I found that the feature of cri_handler="cc" was not used.
like:

cat <<-EOF | kubectl apply -f -
apiVersion: v1
kind: Pod
metadata:
  name: nginx-sandbox
spec:
  containers:
  - image: docker.io/zhouliang121/alpine-84688df7-2c0c-40fa-956b-29d8e74d16c1-gcm:latest
    command:
      - top
    imagePullPolicy: IfNotPresent
    name: alpine
  restartPolicy: Never
EOF

Is there any special connection between the runtimeClassName provided in k8s and the runtime declared in containerd? Why does cri_handler not take effect?