Bug 2085326

Summary: kube-state-metrics is tripping APIRemovedInNextEUSReleaseInUse
Product: OpenShift Container Platform Reporter: Sunil Thaha <sthaha>
Component: MonitoringAssignee: Sunil Thaha <sthaha>
Status: CLOSED ERRATA QA Contact: Junqi Zhao <juzhao>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.10CC: amuller, anpicker, juzhao, spasquie, wking
Target Milestone: ---   
Target Release: 4.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 2085329 (view as bug list) Environment:
Last Closed: 2022-08-10 11:11:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2085329    

Description Sunil Thaha 2022-05-13 02:01:59 UTC
kube-state-metrics is tripping APIRemovedInNextEUSReleaseInUse in 4.10 clusters because it's watching poddisruptionbudgets.v1beta1.policy.


How reproducible: always

Comment 1 Junqi Zhao 2022-05-13 04:00:04 UTC
checked with 4.11.0-0.nightly-2022-05-11-054135, 
# oc -n openshift-monitoring get pod | grep kube-state-metrics
kube-state-metrics-645b85779b-bqdzh                      3/3     Running   0          23h
# oc -n openshift-monitoring exec -c kube-state-metrics kube-state-metrics-645b85779b-bqdzh -- kube-state-metrics --version
kube-state-metrics, version v2.4.2 (branch: rhaos-4.11-rhel-8, revision: da804f8)
  build user:       root@620f48f25802
  build date:       2022-05-10T12:11:02Z
  go version:       go1.17.5
  platform:         linux/amd64

checked the alerts, the APIRemovedInNextEUSReleaseInUse is triggered by openshift-logging, not by kube-state-metrics, see the attached file

Comment 3 Simon Pasquier 2022-05-17 15:05:44 UTC
*** Bug 2079314 has been marked as a duplicate of this bug. ***

Comment 7 errata-xmlrpc 2022-08-10 11:11:36 UTC
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