kubelet image GC after a maximum age

[haircommander]

Enhancement Description

• One-line enhancement description (can be used as a release note): Add Kubelet option to specify the maximum age an image will be kept around before it is garbage collected
• Kubernetes Enhancement Proposal:
• Discussion Link: Discussed in SIG-Node as well as SIG-Node Image GC WG
• Primary contact (assignee): @haircommander
• Responsible SIGs: Node
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.29
  • Beta release target (x.y):
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s): KEP-4210: Add ImageGCMaximumAge KEP #4211
  • Code (k/k) update PR(s): KEP-4210: add support for ImageMaximumGCAge field kubernetes#121275
  • Docs (k/website) update PR(s): garbage collection: add blurb about ImageMaximumGCAge website#43544

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[haircommander]

/sig node

[SergeyKanzhelev]

/stage alpha
/milestone v1.29
/label lead-opted-in

[dchen1107]

cc/ @bsdnet to help reviewing.

[npolshakova]

Hello @haircommander 👋, 1.29 Enhancements team here!

Just checking in as we approach enhancements freeze on 01:00 UTC, Friday, 6th October, 2023.

This enhancement is targeting for stage alpha for 1.29 (correct me, if otherwise)

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: 1.29. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.
• KEP readme has up-to-date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here).

It looks like https://github.com/kubernetes/enhancements/pull/4211/files will address most of these issues when it merges in!

The status of this enhancement is marked as at risk for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

[kannon92]

/assign @haircommander

[npolshakova]

Hi @haircommander, just checking in once more as we approach the 1.29 enhancement freeze deadline this week on 01:00 UTC, Friday, 6th October, 2023. The status of this enhancement is marked as at risk for enhancement freeze.

It looks like #4211 will address most of the requirements when it merges. Let me know if I missed anything. Thanks!

[npolshakova]

With KEP PR #4211 approved, the enhancement is ready for the enhancements freeze. The status is now marked as tracked for enhancement freeze for 1.29. 🚀 Thank you!

[katcosgrove]

Hey there @haircommander! 👋, v1.29 Docs Lead here.
Does this enhancement work planned for v1.29 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.29 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday, 19 October 2023.
Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.
Thank you!

[pacoxu]

containerd/containerd#9022 adds support for image expiration in GC, which is a similar concept. But this is a containerd v2.0 feature.

[katcosgrove]

Hi again @haircommander! The deadline to open a placeholder PR against k/website for required documentation is this Thursday, 19 October. Could you please update me on the status of docs for this enhancement? Thank you!

[haircommander]

thanks for the reminder @katcosgrove I've opened the draft here kubernetes/website#43544

[npolshakova]

Hey again @haircommander 👋 1.29 Enhancements team here,

Just checking in as we approach code freeze at 01:00 UTC Wednesday 1st November 2023: .

Here's where this enhancement currently stands:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PR/s are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

This KEP is currently marked as at risk for code freeze.

Also, please let me know if there are other PRs in k/k we should be tracking for this KEP.
As always, we are here to help if any questions come up. Thanks!

[kannon92]

@haircommander can you update this issue with the relevant PRs for alpha?

kubernetes/kubernetes#121275 should be added to this description.

#4211 is another that should be added.

[a-mccarthy]

Hi @haircommander, 👋 from the v1.29 Release Team-Communications! We would like to check if you have any plans to publish a blog for this KEP regarding new features, removals, and deprecations for this release.

If so, you need to open a PR placeholder in the website repository.
The deadline will be on Tuesday 14th November 2023 (after the Docs deadline PR ready for review)

Here is the 1.29 calendar

[npolshakova]

Thanks for updating the issue description. This is now tracked for code freeze for 1.29! 🚀

[sftim]

SIG Node, don't forget to document the changes here. SIG Docs (and SIG Release's release docs subteam) can help you understand what to do.

[haircommander]

I updated the PR!