There are bugs with the IPv6DualStack feature flag in 1.17/4.4 even in single-stack clusters. Bug 1794376 removed it from openshift/api and updated cluster-kube-apiserver-operator but didn't update cluster-kube-controller-manager-operator so we were still setting that flag for kcm.
Confirmed with payload: 4.4.0-0.nightly-2020-03-08-213224, the issue has fixed: [root@dhcp-140-138 ~]# oc rsh -n openshift-kube-controller-manager po/kube-controller-manager-ip-10-0-136-132.us-east-2.compute.internal sh-4.2# cat /etc/kubernetes/static-pod-resources/configmaps/config/config.yaml | python -m json.tool { ... "feature-gates": [ "RotateKubeletServerCertificate=true", "SupportPodPidsLimit=true", "NodeDisruptionExclusion=true", "ServiceNodeExclusion=true", "SCTPSupport=true", "LegacyNodeRoleBehavior=false" ],
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