DUPLICATE Artifactory and cluster image cleanup.

[Jose-Matsuda]

Sorry it never occurred to me that I could just change the original issue to become the epic...

#461 is growing out of its initial scope and has moved past a simple "get old images, get vulnerable images, delete".

A starting point courtesy of Blair / Justin

• Define the types of images we are looking at. Issue tracking here Discuss 'types' of images present in the cluster and how to clean them up. #499
• Determine the appropriate course of action for each.
• Regardless of the outcome of the above, we can position ourselves such that we can handle the situation. Something actionable and solid here is to; create a collection of vulnerable images, compare it against images in the cluster, and make a list of the intersection with a date attached to them. This information should be persisted somewhere such that the next item can take it. Issue tracking [here]
• Again regardless, send notifications using that information. (Will require a way to get an email associated with a namespace of a container)
• TBD

Add more checkboxes as they appear.

[Jose-Matsuda]

CLOSING AS DUPLICATE