Bump github.com/containerd/containerd from 1.6.19 to 1.7.3

[dependabot]

Bumps github.com/containerd/containerd from 1.6.19 to 1.7.3.

Release notes

Sourced from github.com/containerd/containerd's releases.

containerd 1.7.3

Welcome to the v1.7.3 release of containerd!

The third patch release for containerd 1.7 contains various fixes and updates.

Notable Updates

• RunC: Update runc binary to v1.1.8 (#8843)
• CRI: Fix additionalGids: it should fallback to imageConfig.User when securityContext.RunAsUser,RunAsUsername are empty (#8824)
• CRI: write generated CNI config atomically (#8825)
• Port-Forward: Correctly handle known errors (#8806)
• Resolve docker.NewResolver race condition (#8799)
• Fix net.ipv4.ping_group_range with userns (#8786)
• Runtime/V2/RunC: handle early exits w/o big locks (#8712)
• SecComp: always allow name_to_handle_at (#8753)
• CRI: Windows Pod Stats: Add a check to skip stats for containers that are not running (#8654)
• Task: don't close() io before cancel() (#8658)
• Remove CNI conf_template deprecation (#8638)
• Fix issue for HPC pod metrics (#8634)

See the changelog for complete list of changes

Please try out the release binaries and report any issues at https://github.com/containerd/containerd/issues.

Contributors

• Akihiro Suda
• Phil Estes
• Sebastiaan van Stijn
• Wei Fu
• Derek McGowan
• Kazuyoshi Kato
• Austin Vazquez
• Samuel Karp
• Shingo Omura
• Jin Dong
• Maksym Pavlenko
• Aditi Sharma
• Danny Canter
• James Sturtevant
• Laura Brehm
• Rodrigo Campos
• Akhil Mohan
• Andrey Epifanov
• Bjorn Neergaard
• Cory Snider
• Madhav Jivrajani
• Mahamed Ali
• Priyanka Saggu

... (truncated)

Changelog

Sourced from github.com/containerd/containerd's changelog.

Versioning and Release

This document details the versioning and release plan for containerd. Stability is a top goal for this project, and we hope that this document and the processes it entails will help to achieve that. It covers the release process, versioning numbering, backporting, API stability and support horizons.

If you rely on containerd, it would be good to spend time understanding the areas of the API that are and are not supported and how they impact your project in the future.

This document will be considered a living document. Supported timelines, backport targets and API stability guarantees will be updated here as they change.

If there is something that you require or this document leaves out, please reach out by filing an issue.

Releases

Releases of containerd will be versioned using dotted triples, similar to Semantic Version. For the purposes of this document, we will refer to the respective components of this triple as <major>.<minor>.<patch>. The version number may have additional information, such as alpha, beta and release candidate qualifications. Such releases will be considered "pre-releases".

Major and Minor Releases

Major and minor releases of containerd will be made from main. Releases of containerd will be marked with GPG signed tags and announced at https://github.com/containerd/containerd/releases. The tag will be of the format v<major>.<minor>.<patch> and should be made with the command git tag -s v<major>.<minor>.<patch>.

After a minor release, a branch will be created, with the format release/<major>.<minor> from the minor tag. All further patch releases will be done from that branch. For example, once we release v1.0.0, a branch release/1.0 will be created from that tag. All future patch releases will be done against that branch.

Pre-releases

Pre-releases, such as alphas, betas and release candidates will be conducted from their source branch. For major and minor releases, these releases will be done from main. For patch releases, these pre-releases should be done within the corresponding release branch.

While pre-releases are done to assist in the stabilization process, no guarantees are provided.

... (truncated)

Commits

• 7880925 Merge pull request #8871 from aepifanov/release_notes_1.7.3
• 4cb2f15 [release/1.7] Add release notes for v1.7.3
• 1b659e7 Merge pull request #8869 from mqasimsarfraz/release/1.7
• b461eca cri: memory.memsw.limit_in_bytes: no such file or directory
• d47069b Merge pull request #8875 from akhilerm/cherry-pick-8862-release/1.7
• 14328ae migrate to community owned bucket
• a0f8325 Merge pull request #8843 from thaJeztah/1.7_backport_bump_runc_binary_1.1.8
• b985f7e update runc binary to v1.1.8
• 68bd89e Merge pull request #8824 from thaJeztah/1.7_backport_fix-additiona-gids-to-re...
• e4c98f8 Merge pull request #8825 from thaJeztah/1.7_backport_issue-8607
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[tekton-robot]

Hi @dependabot[bot]. Thanks for your PR.

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

[vdemeester]

/lgtm

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester

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 [vdemeester]

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