Currently relatedobjects are only filled when an operator is running, with https://github.com/openshift/cluster-version-operator/pull/318 we should be able to report that information during operator creation.
Checked with payload: 4.5.0-0.nightly-2020-05-06-003431, the issue has fixed: During installation, login bootstrap , check the operator: After the master running immediately , we could see: oc get co kube-controller-manager kube-apiserver -o json --kubeconfig=/opt/openshift/auth/kubeconfig | jq '.items[].status.relatedObjects' [ { "group": "operator.openshift.io", "name": "cluster", "resource": "kubecontrollermanagers" }, { "group": "", "name": "openshift-config", "resource": "namespaces" }, { "group": "", "name": "openshift-config-managed", "resource": "namespaces" }, { "group": "", "name": "openshift-kube-controller-manager", "resource": "namespaces" }, { "group": "", "name": "openshift-kube-controller-manager-operator", "resource": "namespaces" } ] [ { "group": "operator.openshift.io", "name": "cluster", "resource": "kubeapiservers" }, { "group": "apiextensions.k8s.io", "name": "", "resource": "customresourcedefinitions" }, { "group": "security.openshift.io", "name": "", "resource": "securitycontextconstraints" }, { "group": "", "name": "openshift-config", "resource": "namespaces" }, { "group": "", "name": "openshift-config-managed", "resource": "namespaces" }, { "group": "", "name": "openshift-kube-apiserver-operator", "resource": "namespaces" }, { "group": "", "name": "openshift-kube-apiserver", "resource": "namespaces" } ]
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