Description of problem: When custom tolerations are set via the imagepruner resource, the operator doesn't propagete them into the cronjob. Version-Release number of selected component (if applicable): 4.8 How reproducible: Always Steps to Reproduce: 1. set spec.tolerations on imagepruner Actual results: The image pruner cron job uses these tolerations. Expected results: Default tolerations are always used. Additional info:
Verified on 4.9.0-0.nightly-2021-06-24-123715: spec: failedJobsHistoryLimit: 3 ignoreInvalidImageReferences: true keepTagRevisions: 3 logLevel: Normal schedule: '* * * * *' successfulJobsHistoryLimit: 3 suspend: false tolerations: - effect: NoSchedule key: key operator: Equal value: value
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:3759