Bug 1788812
Summary: | Test cluster is firing large number of UsingDeprecatedAPIExtensionsV1Beta1 alerts. | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Xingxing Xia <xxia> |
Component: | kube-apiserver | Assignee: | Stefan Schimanski <sttts> |
Status: | CLOSED ERRATA | QA Contact: | Ke Wang <kewang> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 4.4 | CC: | aos-bugs, maszulik, mfojtik, pkrupa, tnozicka |
Target Milestone: | --- | ||
Target Release: | 4.4.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | 1768417 | Environment: | |
Last Closed: | 2020-05-04 11:23:07 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Xingxing Xia
2020-01-08 07:35:33 UTC
4.4 has disabled serving those deprecated apis, this should be happening there now s/should/shouldn't Verified with Server Version: 4.4.0-0.nightly-2020-01-13-220938. Created file daemonset-simple-hello-openshift.yaml with the following content, apiVersion: extensions/v1beta1 kind: DaemonSet metadata: name: hello-openshift-daemonset spec: selector: matchLabels: name: hello-openshift-daemonset template: metadata: labels: name: hello-openshift-daemonset spec: containers: - image: openshift/hello-openshift name: hello-openshift $ oc create -f daemonset-simple-hello-openshift.yaml error: unable to recognize "daemonset-simple-hello-openshift.yaml": no matches for kind "DaemonSet" in version "extensions/v1beta1" Check it on Prometheus UI -> Alerts page, searching UsingDeprecatedAPIExtensionsV1Beta1, there is no related log. Also check it on Monitoring -> Alerting page, there is no firing log of UsingDeprecatedAPIExtensionsV1Beta1. 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, 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/RHBA-2020:0581 |