Why is there no backoffLimit set for the Image Registry pruning in OpenShift Container Platform 4
Issue
- In the
openshift-image-registrynamespace, we would see a image-pruner Pod in error. In its log, some issue connecting to the API server. Doesn't retry. Pod exits. Then Job is marked as failed and Backoff Limit is 0. CronJob won't ever re-schedule a Job, CO is then marked as degraded. - Why is there no backoffLimit set for the Image Registry pruning in OpenShift Container Platform 4
Environment
- Red Hat OpenShift Container Platform (OCP) 4
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
