Bug 2078901 - Alerts are not been raised when requests to apis which will be removed on 1.25 are done.
Summary: Alerts are not been raised when requests to apis which will be removed on 1.2...
Keywords:
Status: CLOSED DUPLICATE of bug 2067456
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: openshift-apiserver
Version: 4.11
Hardware: All
OS: All
urgent
urgent
Target Milestone: ---
: ---
Assignee: Abu Kashem
QA Contact: Rahul Gangwar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-26 13:02 UTC by Camila Macedo
Modified: 2022-04-26 16:53 UTC (History)
2 users (show)

Fixed In Version: 4.11
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-26 16:53:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Camila Macedo 2022-04-26 13:02:43 UTC
Description of problem:

Alerts are not been raised when requests to apis which will be removed on 1.25 are done. Openshift 4.11 should be raising these alerts so that Operator authors are able to check that their solutions use APIs which will be removed.

Note that we cannot ask for red hatters and outside authors to perform regression tests and communicate the needs until the alerts are working properly. 


Version-Release number of selected component (if applicable):


How reproducible:

- Deploy/install an Operator and create the CR instance of any Operator that uses the removed apis version on 1.25 ( i.e. cronjob v1beta1 )
- Then, we would expect to see events alerts raised notifying that apis which are deprecated and will get removed on the next release were used

Actual results:

No alerts are raised 

Expected results:

Alerts/events with the deprecation api usage info

Additional info:

The problem shows to be here: https://github.com/openshift/cluster-kube-apiserver-operator/blob/release-4.11/bindata/assets/alerts/api-usage.yaml#L19

It is not updated to raise the events for 1.25

Comment 5 Camila Macedo 2022-04-26 16:53:37 UTC

*** This bug has been marked as a duplicate of bug 2067456 ***


Note You need to log in before you can comment on or make changes to this bug.