-
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 depracated pod-infra-container-image
kubelet flag
#7409
Conversation
We should confirm that the containerd CRI implementation actually exposes this and it is used by the kubelet; CRI related warnings from the kubelet are not always in sync with the reality of CRI implementation maturity. |
Good call Brad, looking around, it appears that containerd has the proper implementation, but crio and cri-dockerd are not yet fully implemented. Seems this has been pushed off until 1.28 for upstream. I am converting this to a draft until that has been resolved. crio: cri-o/cri-o#6816 |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #7409 +/- ##
==========================================
- Coverage 48.92% 40.73% -8.19%
==========================================
Files 158 158
Lines 14032 14030 -2
==========================================
- Hits 6865 5715 -1150
- Misses 5885 7272 +1387
+ Partials 1282 1043 -239
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Should we check with @Oats87 and co to ensure they're prepared for this |
0bb00af
to
9b705d4
Compare
pod-infra-container-image
kubelet flagpod-infra-container-image
kubelet flag
0f52e02
to
5a07405
Compare
You mentioned earlier that cri-dockerd didn't support this yet, do we need to bump the embedded cri-dockerd version as part of this? |
Good catch, it seems that they still have not implemented this and that full removal has moved back to 1.30 |
pod-infra-container-image
kubelet flagpod-infra-container-image
kubelet flag
There is a PR, if you want to patch your fork. Main issue is that cri-dockerd is still using the 1.22 API |
@afbjorklund we might take a look at pulling that in. Our fork already upgrades the CRI API and stubs out the metrics calls - although we do it by just returning an Unimplemented error, instead of returning empty/zero metrics like the current upstream PR appears to do. |
Probably a better idea, it's been a few months now since that initial hack |
cri-dockerd has support as of v0.3.10, so 1.30 will see this merged. |
Signed-off-by: Derek Nola <[email protected]>
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.
LGTM
Proposed Changes
Types of Changes
CLI
Verification
Start k3s with
--pause-image=rancher/mirrored-pause:3.5
and check the logs for the kubelet command. Should see no complaints from kubelet.Testing
Linked Issues
#7408
User-Facing Change
Further Comments