Commit Graph

4 Commits

Author SHA1 Message Date
Chris Evich 56f11b1016
Cirrus: Load base-image names indirectly
Rather than hard-coding all four base-image env. var name,
load the values based on the shared variable name suffix.

Thanks to Ed Santiago <santiago@redhat.com> for the suggestion.

Signed-off-by: Chris Evich <cevich@redhat.com>
2019-08-30 09:46:43 -04:00
Chris Evich 78b0773f7d
Cirrus: Enable VM image housekeeping
Also do some minor cleanup and add additional safety-checks to pruning
script (container image).

Signed-off-by: Chris Evich <cevich@redhat.com>
2019-08-26 14:30:40 -04:00
Chris Evich d36c62d88d
Revert "Cirrus: Temp. workaround missing imgprune image"
This reverts commit 9b2e98f1e8.

Signed-off-by: Chris Evich <cevich@redhat.com>
2019-08-12 15:04:30 -04:00
Chris Evich e8564dc44f
Cirrus: Print images that should be pruned
Over time unless they're removed, the project could grow quite a large
collection of VM images.  While generally cheap (less than a penny each,
per month), these will become a significant cost item if not kept
in-check.

Add a specialized container for handling image-pruning, but limit
it to only finding and printing (not actually deleting) images.

Also update the image-building workflow so that base-images used to
compose cache-images are also labeled with metadata.

N/B: As an additional safeguard, the service account which
     executes the new container in production *DOES NOT*
     have access to delete images.  This can be enabled
     by adding the GCE IAM role: CustomComputeImagePrune

Signed-off-by: Chris Evich <cevich@redhat.com>
2019-07-15 15:26:26 -04:00