-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[1.30] Remove deprecated kublet flag pod-infra-container-image
#7408
Comments
The upstream issue is still tracking as incomplete. |
pod-infra-container-image
pod-infra-container-image
Update: Upstream is on track to no-op the argument in 1.29, with remove in 1.30+ |
pod-infra-container-image
pod-infra-container-image
Upstream bumping it out to "future release" during 1.27 development. kubernetes/kubernetes@a1def4b Later it was supposed to be 1.29, but cri-dockerd was still not ready, so now its 1.30 |
The flag doesn't do anything in 1.29, so the kubelet now tries to garbage collect the pause image for docker... But most of the time, there is some pod or other still using it - so that won't make much of a difference in practice. |
The pause image is supposed to get pinned via CRI if the runtime supports it. I'm not sure that cri-dockerd does yet though. |
I made a quick hack for it, but it got stuck in CI due to the missing API (since it only did k8s 1.22 at the time) |
Thanks! If upstream doesn't merge that, we might pull it into our fork. |
Validated using v1.30.0-rc2+k3s1 and v1.30.0-rc2+rke2r1This log warning is no longer present. See only deprecation warning remaining:
config.yaml used:
|
Is your feature request related to a problem? Please describe.
Running K3s with
--pause-image=:"rancher/mirrored-pause:3.5"
produces logs with:Describe the solution you'd like
Describe alternatives you've considered
Additional context
kubernetes/kubernetes#106893
The text was updated successfully, but these errors were encountered: