chore(deps): Bump protobuf version#10270
Conversation
|
/test |
|
@c-du: The
The following commands are available to trigger optional jobs:
Use
DetailsIn 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/test-infra repository. |
|
Images are ready for the commit at da70fce. To use with deploy scripts, first |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #10270 +/- ##
=======================================
Coverage 47.96% 47.96%
=======================================
Files 2420 2420
Lines 169393 169393
=======================================
+ Hits 81247 81253 +6
+ Misses 81461 81457 -4
+ Partials 6685 6683 -2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
Merge commit has been cherry-picked to branch |
(cherry picked from commit 6c4b0d3)
io.cri-containerd.pinned has known bugs (containerd#9328, #10270) that make it unreliable for preventing image GC. Replace the pinning approach with a re-pull step: after the prefetcher completes, run ctr images pull on each node for any images whose tag reference was lost to GC. Since layers are still cached, re-pulls are near-instant. Uses the same image list configmap as the prefetcher. Only re-pulls images that are missing (ctr images check); skips images that are still present. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
io.cri-containerd.pinned has known bugs (containerd#9328, #10270) that make it unreliable for preventing image GC. Replace the pinning approach with a re-pull step: after the prefetcher completes, run ctr images pull on each node for any images whose tag reference was lost to GC. Since layers are still cached, re-pulls are near-instant. Uses the same image list configmap as the prefetcher. Only re-pulls images that are missing (ctr images check); skips images that are still present. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
io.cri-containerd.pinned has known bugs (containerd#9328, #10270) that make it unreliable for preventing image GC. Replace the pinning approach with a re-pull step: after the prefetcher completes, run ctr images pull on each node for any images whose tag reference was lost to GC. Since layers are still cached, re-pulls are near-instant. Uses the same image list configmap as the prefetcher. Only re-pulls images that are missing (ctr images check); skips images that are still present. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
io.cri-containerd.pinned has known bugs (containerd#9328, #10270) that make it unreliable for preventing image GC. Replace the pinning approach with a re-pull step: after the prefetcher completes, run ctr images pull on each node for any images whose tag reference was lost to GC. Since layers are still cached, re-pulls are near-instant. Uses the same image list configmap as the prefetcher. Only re-pulls images that are missing (ctr images check); skips images that are still present. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
io.cri-containerd.pinned has known bugs (containerd#9328, #10270) that make it unreliable for preventing image GC. Replace the pinning approach with a re-pull step: after the prefetcher completes, run ctr images pull on each node for any images whose tag reference was lost to GC. Since layers are still cached, re-pulls are near-instant. Uses the same image list configmap as the prefetcher. Only re-pulls images that are missing (ctr images check); skips images that are still present. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Description
Pickup the fix for GO-2024-2611(CVE-2024-24786)
Checklist
If any of these don't apply, please comment below.
Testing Performed
Existing tests
Reminder for reviewers
In addition to reviewing code here, reviewers must also review testing and request further testing in case the
performed one does not seem sufficient. As a reviewer, you must not approve the change until you understand the
performed testing and you are satisfied with it.