Upgrade to containerd v1.5 #6449
Assignees
Labels
area: shim
An issue with the containerd shim
runtime: containerd
Issues related to containerd
type: enhancement
New feature or request
Comments
ianlewis
added
area: shim
|
Cc: @fvoznika |
|
We need to wait for Kubernetes 1.23, which uses containerd 1.4, to reach end of life before we can start using 1.5. Otherwise we loose the ability to issue security patches to 1.23 if needed. This link has the schedule for release deprecations. 1.23 end of life is set to 2023-05. Apart from #6414, is there any other problem you're facing using containerd 1.5 with gVisor's shim? |
copybara-service bot
pushed a commit
that referenced
this issue
Oct 22, 2021
"cri.runtimeoptions.v1" moved to "runtimeoptions.v1" and containerd configuration format version 2 is required. Updates #6449 PiperOrigin-RevId: 404671168
copybara-service bot
pushed a commit
that referenced
this issue
Oct 25, 2021
"cri.runtimeoptions.v1" moved to "runtimeoptions.v1" and containerd configuration format version 2 is required. Updates #6449 PiperOrigin-RevId: 405474653
|
A friendly reminder that this issue had no activity for 120 days. |
github-actions
bot
added
the
stale-issue
|
This issue is unblocked, so I'll start working on it. |
manninglucas
removed
the
stale-issue
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The
containerd/containerddependency is currently two minor versions behind the latest release:v1.3.9v1.5.5There are subtle incompatibilities between gVisor and newer versions of containerd that require temporary workarounds and fixes (see #6414 and #6232). These workarounds allow gVisor users to upgrade containerd beyond v1.3, but they should eventually be removed in favor of upgrading the containerd version used by gVisor.
Is this feature related to a specific bug?
Do you have a specific solution in mind?
No response
The text was updated successfully, but these errors were encountered: