Hi @aitumik. 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.

A few comments:

• Files needs to be goformatted to satisfy linter.
• Could you please sign off your commits (try git commit -s) in order to pass CI checks?
  https://github.com/containerd/project/blob/master/CONTRIBUTING.md#sign-your-work
• Could you please backport these tests to observer as well.

This should resolve #7826

Could you please backport these tests to sbserver as well.

@aitumik If this was confusing, we split the CRI codebase in two while we work on an experimental feature here. This is where you'd need to duplicate your changes: https://github.com/containerd/containerd/tree/main/pkg/cri/sbserver. It should be a pretty easy copy and paste for that and the files are named the same. Thanks for working on this!

Could you pls squash the commits?

/test pull-containerd-sandboxed-node-e2e

Can you try a rebase to see if we can get the windows tests passing. The errors don't seem related to your change, but I don't quite understand the failure either.

@dmcgowan It was this #8073, which was fixed by #8074. Rebase should resolve this like you said