Provide out-of-lifed image warning in status

[castrojo]

In Universal Blue we add a message to the user's terminal motd when they're on an image older than 90 days to remind them that they need to upgrade. This has been pretty useful and I've been thinking of how this can just be built into bootc if people think it's a good idea.

Maybe adding it to bootc status with the eol date of the image and then there's a visual indicator if it's past it's freshness date.

Then to go along with that maybe we could add a label, random example containers.bootc.eol-date so that can be adjusted depending on the use case, then people can just centralize that as policy when they build and push. Or maybe just surface quay.expires-after? Might be useful for QA folks who'll end up testing a bunch of development images, etc.

[cgwalters]

In Universal Blue we add a message to the user's terminal motd when they're on an image older than 90 days to remind them that they need to upgrade.

Agreed, makes total sense!

Or maybe just surface quay.expires-after?

IMO that feature is a trap because there's definitely use cases for others to push "expired" images to their own private mirrors, etc.

Then to go along with that maybe we could add a label, random example containers.bootc.eol-date

This is a generic container issue not specific to bootc I believe...would be useful to try to drive something like this via OCI right?

[castrojo]

On Sun, Sep 29, 2024 at 5:53 PM Colin Walters ***@***.***> wrote: This is a generic container issue not specific to bootc I believe...would be useful to try to drive something like this via OCI right?

I don't know what the process is via OCI but I will find out.

…

Message ID: ***@***.***>

[vrothberg]

It's probably worth pursuing both: starting with a bootc-specific label and proposing to the OCI in parallel. The latter can take a lot of time and usually requires some in-the-wild experience with the proposed feature.