The current: Refer to the apirequestcount.apiserver.openshift.io resources to identify the workload. is not particularly specific, and folks might not think to look at the '-o yaml' or similar detailed view to see consumer information. We now have a kbase solution [1] walking folks through the analysis in more detail. We should link to it from the alert description. [1]: https://access.redhat.com/articles/6329921
Already fixed via an explicit '-o yaml' in 4.9+. Moving this straight to MODIFIED to hang a 4.8.z backport on.
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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), 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/RHSA-2021:3759