Draft
Conversation
After each successful CRI PullImage, use the containerd native client API to set io.cri-containerd.pinned=pinned on the image. This tells kubelet's image GC to skip the image. The CRI API doesn't support setting image labels, so we connect to containerd directly (same socket) using the containerd client library in the k8s.io namespace. The pinning happens immediately after each successful pull, before GC has a chance to evict the image. This is a proof-of-concept to test if pinning at pull time (via the containerd API) works better than post-hoc pinning via ctr CLI, which has known bugs (containerd#9328, #10270). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.