Skip to content
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

fix: take into account the moment seen when cleaning up CRI images #8225

Merged
merged 1 commit into from
Feb 1, 2024

Conversation

smira
Copy link
Member

@smira smira commented Jan 31, 2024

Fixes #8069

The image age from the CRI is the moment the image was pulled, so if it was pulled long time ago, the previous version would nuke the image as soon as it is unreferenced. The new version would allow the image to stay for the full grace period in case the rollback is requested.

@smira smira added this to the v1.7 milestone Jan 31, 2024
Fixes siderolabs#8069

The image age from the CRI is the moment the image was pulled, so if it
was pulled long time ago, the previous version would nuke the image as
soon as it is unreferenced. The new version would allow the image to
stay for the full grace period in case the rollback is requested.

Signed-off-by: Andrey Smirnov <[email protected]>
@smira smira force-pushed the fix/cri-image-gc-age branch from ed20307 to 17567f1 Compare February 1, 2024 10:44
@smira
Copy link
Member Author

smira commented Feb 1, 2024

/m

@talos-bot talos-bot merged commit 17567f1 into siderolabs:main Feb 1, 2024
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backported
Status: Backported
Development

Successfully merging this pull request may close these issues.

CRI image cleanup might be too aggressive
3 participants