Default image-pruner pods do not have toleration for tainted nodes.

Solution Verified - Updated -


  • If all the nodes are tainted, the image-pruner cronjobs remain in pending state due to missing tolerations.
# oc get pods -n openshift-image-registry
NAME                                   READY       STATUS    RESTARTS    AGE    NODE
image-pruner-1624924800-m5rxg           1/1         Pending     0        5s   <none>        
  • There is no supported way to provide tolerations to image-pruner pods.


  • Red Hat OpenShift Container Platform
    • 4.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content