Update containerd to v1.6.20

[anthonyhaussman]

• https://github.com/containerd/containerd/releases/tag/v1.6.19
• https://github.com/containerd/containerd/releases/tag/v1.6.20

[k8s-ci-robot]

Hi @anthonyhaussman. Thanks for your PR.

I'm waiting for a kubernetes 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.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[hakman]

/ok-to-test

[hakman]

@anthonyhaussman This looks good. Could you split the Go part into a separate commit, like in https://github.com/kubernetes/kops/pull/15159/commits? It would make it easier to cherry-pick.

[anthonyhaussman]

@anthonyhaussman This looks good. Could you split the Go part into a separate commit, like in https://github.com/kubernetes/kops/pull/15159/commits? It would make it easier to cherry-pick.

It's done @hakman 🙂

[hakman]

Thanks @anthonyhaussman!
/retest

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hakman

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [hakman]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[hakman]

/retest

[k8s-triage-robot]

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

• The PR does have any do-not-merge/* labels
• The PR does not have the needs-ok-to-test label
• The PR is mergeable (does not have a needs-rebase label)
• The PR is approved (has cncf-cla: yes, lgtm, approved labels)
• The PR is failing tests required for merge

You can:

• Review the full test history for this PR
• Prevent this bot from retesting with /lgtm cancel or /hold
• Help make our tests less flaky by following our Flaky Tests Guide

/retest

[k8s-triage-robot]

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

• The PR does have any do-not-merge/* labels
• The PR does not have the needs-ok-to-test label
• The PR is mergeable (does not have a needs-rebase label)
• The PR is approved (has cncf-cla: yes, lgtm, approved labels)
• The PR is failing tests required for merge

You can:

• Review the full test history for this PR
• Prevent this bot from retesting with /lgtm cancel or /hold
• Help make our tests less flaky by following our Flaky Tests Guide

/retest

[rifelpet]

/hold the e2e jobs are failing until the credential provider is fixed and released in cloud-provider-aws

[olemarkus]

It's been released, but kOps needs to start supporting downloading and using it. The credentials provider is also not really tested upstream, so there may be more work needed there as well.

Currently working on what's needed kOps-side and will then add e2e in the aws cloud provider.

[hakman]

@rifelpet @olemarkus Should we maybe make these 2 tests optional for now?

[rifelpet]

How about reverting the deps update? That way the head of master is not broken

[olemarkus]

The problem is that the functionality for pulling ECR-containers are removed from kubelet. So we'd have to run these tests with K8s 1.26 instead. Which I am not necessarily against. If the ECR credentials provider is also broken, we won't get the PR to start using it into the repo either.

[rifelpet]

If we know k8s 1.27 doesn't work with kops yet then temporarily pinning our presubmit tests to k8s 1.26 seems reasonable

[hakman]

/test all

[k8s-ci-robot]

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

Test name	Commit	Details	Required	Rerun command
pull-kops-e2e-cni-amazonvpc	a28b11f	link	false	/test pull-kops-e2e-cni-amazonvpc
pull-kops-e2e-cni-kuberouter	a28b11f	link	false	/test pull-kops-e2e-cni-kuberouter

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.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[hakman]

/test pull-kops-e2e-cni-flannel

[hakman]

/hold cancel