+++ This bug was initially created as a clone of Bug #1789420 +++ In a single-stack IPv6 environment cluster-kube-apiserver-operator needs to generate the correct config for kube-apiserver. --- Additional comment from Dan Winship on 2020-01-09 09:38:32 EST --- Tested in the ipv6 builds. Not currently QA-able.
This was resolved by https://github.com/openshift/cluster-kube-apiserver-operator/pull/712
(In reply to Russell Bryant from comment #1) > This was resolved by > https://github.com/openshift/cluster-kube-apiserver-operator/pull/712 turns out we still need https://github.com/openshift/cluster-kube-apiserver-operator/pull/710
Assigning all 4.3.z IPv6 bugs to Marius Cornea for QA, as they are not yet QA-able in stock release-4.3 builds.
This BZ cannot be verified for now on the 4.3-ipv6 release as the latest build(4.3.0-0.nightly-2020-02-10-055634-ipv6.3) includes a custom cluster-kube-apiserver-operator image according to https://github.com/openshift-kni/ocp-ipv6/blob/master/builds.yaml
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:2436