Curious; will this fix the linked issue? Because I see that mentions code that looks for (commented above) sandBoxImage, not pinnedImages (plural); https://github.com/kubernetes/kubernetes/blob/8f8c94a04d00e59d286fe4387197bc62c6a4f374/cmd/kubeadm/app/preflight/checks.go#L841C2-L848C3

not the same issue.

Just find this potential typo during looking into that issue.

I think the issue is related to #11114 and #11117

sandboxImage vs. pinnedImages is handled in this configuration migration:

        var pinnedImages map[string]interface{}
        if v, ok := dst["pinned_images"]; ok {
                pinnedImages = v.(map[string]interface{})
        } else {
                pinnedImages = map[string]interface{}{}
        }

        if simage, ok := src["sandbox_image"]; ok {
                pinnedImages["sandbox"] = simage
        }
        if len(pinnedImages) > 0 {
                dst["pinned_images"] = pinnedImages
        }

when it moved from the RuntimeConfig to the ImageConfig, in 3baf5ed

You still get some warning, even after the migration (until updated to v3)

level=warning msg="Ignoring unknown key in TOML for plugin" error="strict mode: fields in the document are missing in the target struct key=sandbox_image plugin=io.containerd.cri.v1.runtime

maybe it needs to delete the sandbox_image, during the above process?

maybe it needs to delete the sandbox_image, during the above process?

Yeah there are many other fields that also have the warning even after the migration. I have a PR to fix that a while ago #10980. Need to revisit the PR and see if I can get some review there then.

@djdongjin #10980 was merged.

@thaJeztah Could you take a look and see if the current PR is meaningful?