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

Build succeeded.

• containerd-build-arm64 : SUCCESS in 4m 45s (non-voting)
• containerd-test-arm64 : SUCCESS in 6m 02s (non-voting)
• containerd-integration-test-arm64 : SUCCESS in 25m 29s (non-voting)

Build succeeded.

• containerd-build-arm64 : SUCCESS in 4m 32s (non-voting)
• containerd-test-arm64 : SUCCESS in 6m 03s (non-voting)
• containerd-integration-test-arm64 : SUCCESS in 24m 52s (non-voting)

/ok-to-test

/test pull-containerd-node-e2e

@Jordy24: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Looks like something is up with the e2e tests, but given this PR only changes comments and docs, I'm pretty sure we don't need to validate e2e node tests :)