-
Notifications
You must be signed in to change notification settings - Fork 526
Fix wrong sandbox image path in containerd/config.toml v3 #12665
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix wrong sandbox image path in containerd/config.toml v3 #12665
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
/lgtm
/approve
LGTM label has been added. Git tree hash: ed717daeed9b37fbd03d882727a14965f9d0582f
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: LucaBernstein 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:
Approvers can indicate their approval by writing |
/retest |
/cherry-pick release-v1.123 |
@vpnachev: once the present PR merges, I will cherry-pick it on top of release-v1.123 in a new PR and assign it to you. In response to this:
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-sigs/prow repository. |
/cherry-pick release-v1.122 |
@vpnachev: once the present PR merges, I will cherry-pick it on top of release-v1.122 in a new PR and assign it to you. In response to this:
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-sigs/prow repository. |
/cherry-pick release-v1.124 |
@vpnachev: once the present PR merges, I will cherry-pick it on top of release-v1.124 in a new PR and assign it to you. In response to this:
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-sigs/prow repository. |
/lgtm |
@vpnachev: new pull request created: #12670 In response to this:
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-sigs/prow repository. |
@vpnachev: new pull request created: #12671 In response to this:
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-sigs/prow repository. |
@vpnachev: new pull request created: #12672 In response to this:
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-sigs/prow repository. |
How to categorize this PR?
/area os
/kind bug
What this PR does / why we need it:
With PR #11623 the paths for various configuration items in
containerd/config.toml
are retrieved from a look-up table depending on the version of thecontainerd/config.toml
file. Unfortunately, said PR contained an error for the sandbox image configuration which results in containerd 2.x always using the defaultregistry.k8s.io/pause:3.10
. This will not work in environments that cannot access theregistry.k8s.io
container registry and nodes with containerd 2.x in such environments will not be able to join the cluster.With containerd 2.x (and thus
containerd/config.toml
v3), the sandbox image is configured at[plugins.'io.containerd.cri.v1.images'.pinned_images]
according to https://github.com/containerd/containerd/blob/e2404157c476efcf0ecf6cd49aa3c7ed8a26c858/docs/cri/config.md?plain=1#L189-L190.This PR fixes the wrong path so that the sandbox image location can be properly configured to a custom image with containerd 2.x.
Which issue(s) this PR fixes:
Fixes #
Release note: