Open eks-distro-pr-bot opened 1 week ago
The following steps in the upgrade flow failed:
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Once this PR has been reviewed and has the lgtm label, please assign mitalipaygude for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Hi @eks-distro-pr-bot. Thanks for your PR.
I'm waiting for a aws 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.
The following steps in the upgrade flow failed:
https://github.com/containerd/containerd/blob/main/docs/containerd-2.0.md#whats-breaking Breaking changes in container v2.0.0
The following steps in the upgrade flow failed:
The following steps in the upgrade flow failed:
The following steps in the upgrade flow failed:
The following steps in the upgrade flow failed:
The following steps in the upgrade flow failed:
The following steps in the upgrade flow failed:
The following steps in the upgrade flow failed:
The following steps in the upgrade flow failed:
The following steps in the upgrade flow failed:
The following steps in the upgrade flow failed:
The following steps in the upgrade flow failed:
The following steps in the upgrade flow failed:
The following steps in the upgrade flow failed:
The following steps in the upgrade flow failed:
This PR bumps containerd/containerd to the latest Git revision.
Compare changes Release notes
/hold /area dependencies
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.