I've created an e2e test and updated the RBAC rules which I believe fix this issue, and allow the configmap to be automatically recreated upon deletion. Should this bug be updated to target 4.4 for the PR to merge, or should I clone it to 4.4?
Confirmed with payload: 4.4.0-0.nightly-2019-12-15-184910, the issue has fixed: [root@dhcp-140-138 ~]# oc get cm -n kube-system NAME DATA AGE bootstrap 1 117m cluster-config-v1 1 126m extension-apiserver-authentication 6 126m kube-controller-manager 0 126m root-ca 1 126m [root@dhcp-140-138 ~]# oc delete cm/kube-controller-manager -n kube-system configmap "kube-controller-manager" deleted [root@dhcp-140-138 ~]# oc get cm -n kube-system NAME DATA AGE bootstrap 1 118m cluster-config-v1 1 126m extension-apiserver-authentication 6 126m kube-controller-manager 0 11s root-ca 1 126m
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:0581