Status: IN
OpenShift image lifecycle management spans creation to deletion: images require the `openshift.io/image.managed` annotation for pruning eligibility, the ImagePruner (managed by the Image Registry Operator) runs as a CronJob, and pruning requires a registry restart to clear the blob metadata cache — creating a multi-step lifecycle with manual intervention points.
Three base beliefs about image pruning combine into a complete image lifecycle management model
Depends on (SL): ocp-managed-image-annotation-required, imagepruner-managed-by-image-registry-operator, ocp-image-pruning-requires-registry-restart