Description of problem:
Any places should not use deprecated APIs that will trigger APIRemovedInNextReleaseInUse alert. Otherwise:
 If the places are product components, we need file bug on the related Component and link it under 1947719 "Depends On" field;
 If the places are only testing files, the testing files should update.
For https://github.com/openshift/console/pull/9131 , it replaced v1beta1 with v1 for below:
But I checked latest 4.8 env  that has deployed logging and elasticsearches.logging.openshift.io, I did not see elasticsearch is accessed via deprecated v1beta1 CRD. This means elasticsearch itself is good. I guess jaegers.jaegertracing.io is same (I don't know how to deploy jaegers.jaegertracing.io to have a test).
 I checked it using the bug 1947797#c7 steps which can see all accesses to deprecated APIs.
Given above test result, and considering https://github.com/openshift/console/pull/9131 is only about testing files, this PR fix is a kind of above , not really a component defect, or 3rd party workload defect (like tracked via bug 1958296 / bug 1966508). But per Slack conversation with Jakub Hadvig, that PR needs a valid bug in its title to make PR robot happy, so opening this bug just for it.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
the test resources are now updated to use latest v1 version of CRD
Moving to Verified
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.8.2 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.