Details
-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
False
-
None
-
False
Description
In https://bugzilla.redhat.com/show_bug.cgi?id=2041540 it was noted that ACM 2.4 still (despite all our work via https://github.com/openshift/hive/pull/1395 and followons) shows apirequests for CustomResourceDefinition from apiextensions v1beta1.
I checked on the hive-team cluster (4.10.15 / k8s v1.23.5+3afdacb at the time of this writing) and these requests exist there also. They're clearly not causing problems with the operator, since the API was removed in k8s 1.22. But it would be neat to figure out where they're coming from and get rid of them so folks don't see them and raise flags like in the BZ.
The command to check is:
oc get apirequestcounts customresourcedefinitions.v1beta1.apiextensions.k8s.io -o yaml
And you're looking for things like:
requestCount: 4 userAgent: hive-operator/v0.0.0 username: system:serviceaccount:hive:hive-operator
I.e. requestCount is anything other than zero; and username indicates the hive-operator service account.