@k8s-infra-cherrypick-robot: GitHub didn't allow me to assign the following users: djdongjin.

Note that only containerd members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

Hi @k8s-infra-cherrypick-robot. Thanks for your PR.

I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

FAIL - does not have a valid DCO

But how did this pass in main?

Somehow the cherrypick bot lost this part of the commit message??

---
updated-dependencies:
- dependency-name: actions/cache
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>

Somehow the cherrypick bot lost this part of the commit message??

It's likely some issue with the bot (other repos have similar issues, e.g., kubernetes/ingress-nginx@c39e75b v.s. kubernetes/ingress-nginx@481de71)

I just created a manual cherrypick here #11405

already replaced by a non-cherry-picked version in #11405