- The pruner should not ever delete any used image (in any possible openshift object - also the beta/alpha types!)
- The pruner should not ever delete layers that are used (also via cache) in such an image
I don't know what issues you already know about, or are already fixed in 3.5+. Here a few things to consider if the basic solution stays the way it is today:
Builds happen on an node based on "docker caching logic" and on the "local docker pool", not based on the upstream registry
- This way the cache-reuse happens based on the "docker logic" and against the local docker pool -> The pruning must know about dockers "caching logic". This could be tricky if docker changes that behaviour in a future version and the pruner is not aligned