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: https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4210-max-image-gc-age

• 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): 1.30
  • 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

• Beta

  • KEP (k/enhancements) update PR(s):
    • KEP-4210: retarget to beta for 1.30 #4426
  • Code (k/k) update PR(s):
    • KEP-4210: add e2e tests and add small fix for ImageGCMaxAge kubernetes#123343
    • KEP-4210: kubelet: add reason field to image gc metric kubernetes#123345
    • Promote ImageMaximumGCAge to beta kubernetes#123424
  • Docs (k/website) update(s):
    • ImageGCMaxAge beta bump website#45153

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