Description of problem: The cluster coreDNS Daemonset update function does not iterate over the "kube-rbac-proxy" image reference when updating the container images in the daemonset. Version-Release number of selected component (if applicable): 4.5 How reproducible: Steps to Reproduce: 1.Start a 4.5 cluster 2.Update to newer 4.x cluster version with a newer version of "kube-rbac-proxy" Actual results: "kube-rbac-proxy" image reference won't be update to the correct version. Expected results: "kube-rbac-proxy" is updated. Additional info:
Upgrade from 4.5.0-0.nightly-2020-04-21-103613 to 4.5.0-0.nightly-2020-04-25-17044 and the KUBE_RBAC_PROXY_IMAGE is updated after upgrade. before upgrade: KUBE_RBAC_PROXY_IMAGE=quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:80328072c0dd75fb3e207e07dd1374e999c2f7da7104e707f87a0bd83f7ac5d5 after upgrade: KUBE_RBAC_PROXY_IMAGE=quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:c09411a27f0627e1eabf82d6e607b282e81154bd64db90dc0a4347fa4f1a637b
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, 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/RHBA-2020:2409