This bug was initially created as a copy of Bug #2067384 I am copying this bug because: In 4.11 we also need to ensure that APIRemovedInNextReleaseInUse starts firing for APIs removed in 4.12. So once we fix and backport Bug 2067384 to 4.10 we should follow up by applying the alerting rule changes for 4.11 too. Description of problem: APIRemovedInNextReleaseInUse should fire for APIs removed in 1.25 / 4.12. Version-Release number of selected component (if applicable): 4.11.x How reproducible: 100% Steps to Reproduce: 1. Install 4.11 2. Use any of the APIs here https://github.com/openshift/kubernetes/blob/master/openshift-kube-apiserver/filters/deprecatedapirequest/deprecated.go#L39-L46 3. Don't get APIRemovedInNextReleaseInUse Actual results: No APIRemovedInNextReleaseInUse Expected results: Should get APIRemovedInNextReleaseInUse firing
*** Bug 2078901 has been marked as a duplicate of this bug. ***
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 (Important: OpenShift Container Platform 4.11.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-2022:5069