Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upRFE: ability to mark/flag images so they're excluded from image pruning #12289
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
ncdc
Dec 16, 2016
Contributor
While an annotation may be appropriate and may be the way this gets implemented, I'd recommend just asking for the basic requirement - a way to mark or flag an image such that it is not considered a candidate for pruning.
|
While an annotation may be appropriate and may be the way this gets implemented, I'd recommend just asking for the basic requirement - a way to mark or flag an image such that it is not considered a candidate for pruning. |
ncdc
changed the title from
Enhancement request: Using annotation with oadm prune images
to
RFE: ability to mark/flag images so they're excluded from image pruning
Dec 16, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Agreed |
soltysh
added
component/image
kind/enhancement
labels
Dec 19, 2016
soltysh
self-assigned this
Dec 19, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
@mfojtik fyi |
pweil-
added
the
priority/P2
label
Dec 19, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
smarterclayton
Dec 29, 2016
Member
How would you fit such a tag into your process? Would this be a manual administration step? What criteria would you use to identify the images you would tag?
|
How would you fit such a tag into your process? Would this be a manual administration step? What criteria would you use to identify the images you would tag? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
fgiloux
Dec 31, 2016
Contributor
It would evolve with the release process, first manual and then automated as part of a release pipeline. The tag would be applied at the time the image is either rolled out into production or marked for roll out.
|
It would evolve with the release process, first manual and then automated as part of a release pipeline. The tag would be applied at the time the image is either rolled out into production or marked for roll out. |
fgiloux commentedDec 16, 2016
"oadm prune images" is a very useful command to clear old images. It takes in consideration images that are in use or have been recently used and allow deleting a pile of images created as part of the development process. It is however for auditing and potential rollback required to keep some old images that may not have been in use for a longer time. Typically images that have been rolled out into production at some point (and decommissioned later on) and have been annotated accordingly.
This enhancement request is to add an option to exclude images with a particular annotation from the pruning operation.