Description of problem: Use GA version in KAS/OAS/OauthAS to avoid: "audit.k8s.io/v1beta1" is deprecated and will be removed in a future release, use "audit.k8s.io/v1" instead Version-Release number of selected component (if applicable): 4.8.0-0.nightly-2021-06-01-002052 How reproducible: Always Steps to Reproduce: 1. Check KAS/OAS/OauthAS pod logs, they all have: 021-05-27T04:17:41.879714167Z W0527 04:17:41.879663 1 reader.go:82] "audit.k8s.io/v1beta1" is deprecated and will be removed in a future release, use "audit.k8s.io/v1" instead Actual results: As above Expected results: Now that v1 is GA https://kubernetes.io/docs/reference/config-api/apiserver-audit.v1/, let's use this bug as tracker to update our KAS/OAS/OauthAS to use v1. Additional info:
This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Keywords if you think this bug should never be marked as stale. Please consult with bug assignee before you do that.
The LifecycleStale keyword was removed because the bug moved to QE and the bug got commented on recently. The bug assignee was notified.
(In reply to Xingxing Xia from comment #0) > Steps to Reproduce: > 1. Check KAS/OAS/OauthAS pod logs, they all have: > 021-05-27T04:17:41.879714167Z W0527 04:17:41.879663 1 reader.go:82] "audit.k8s.io/v1beta1" is deprecated and will be removed in a future release, use "audit.k8s.io/v1" instead To clarify, Comment 0 was not talking about audit logs. KAS means kube-apiserver, so KAS pod logs mean: oc get po -n openshift-kube-apiserver; oc logs -n openshift-kube-apiserver <kube-apiserver-... pod> -c kube-apiserver OAS means openshift-apiserver, so OAS pod logs mean: oc get po -n openshift-apiserver; oc logs -n openshift-apiserver <apiserver-... pod> -c openshift-apiserver OauthAS means oauth-apiserver, so its pod logs mean: oc get po -n openshift-oauth-apiserver; oc logs -n openshift-oauth-apiserver <apiserver-... pod>
Hi Emily, Still getting warning messages in logs as below. oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.8.0-0.nightly-2021-08-12-174317 True False 29m Cluster version is 4.8.0-0.nightly-2021-08-12-174317 for i in `oc get po -n openshift-kube-apiserver|grep kube|awk '{print $1}'`; do oc logs -n openshift-kube-apiserver $i -c kube-apiserver|grep audit.k8s.io/v1beta;done; W0816 06:46:50.277587 18 reader.go:82] "audit.k8s.io/v1beta1" is deprecated and will be removed in a future release, use "audit.k8s.io/v1" instead W0816 06:50:36.954245 19 reader.go:82] "audit.k8s.io/v1beta1" is deprecated and will be removed in a future release, use "audit.k8s.io/v1" instead W0816 06:54:14.069699 20 reader.go:82] "audit.k8s.io/v1beta1" is deprecated and will be removed in a future release, use "audit.k8s.io/v1" instead for i in `oc get po -n openshift-oauth-apiserver|grep -v NAME|awk '{print $1}'`; do oc logs -n openshift-oauth-apiserver $i |grep audit.k8s.io/v1beta;done; W0816 06:38:15.679824 1 reader.go:82] "audit.k8s.io/v1beta1" is deprecated and will be removed in a future release, use "audit.k8s.io/v1" instead W0816 06:38:14.828489 1 reader.go:82] "audit.k8s.io/v1beta1" is deprecated and will be removed in a future release, use "audit.k8s.io/v1" instead W0816 06:38:21.567402 1 reader.go:82] "audit.k8s.io/v1beta1" is deprecated and will be removed in a future release, use "audit.k8s.io/v1" instead for i in `oc get po -n openshift-apiserver|grep -v NAME|awk '{print $1}'`; do oc logs -n openshift-apiserver $i -c openshift-apiserver|grep audit.k8s.io/v1beta;done; W0816 06:47:01.522108 1 reader.go:82] "audit.k8s.io/v1beta1" is deprecated and will be removed in a future release, use "audit.k8s.io/v1" instead W0816 06:44:02.122023 1 reader.go:82] "audit.k8s.io/v1beta1" is deprecated and will be removed in a future release, use "audit.k8s.io/v1" instead W0816 06:48:40.644890 1 reader.go:82] "audit.k8s.io/v1beta1" is deprecated and will be removed in a future release, use "audit.k8s.io/v1" instead
Checked in latest payload and not getting warning message oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.9.0-0.nightly-2021-08-14-065522 True False 3m4s Cluster version is 4.9.0-0.nightly-2021-08-14-065522 for i in `oc get po -n openshift-apiserver|grep -v NAME|awk '{print $1}'`; do oc logs -n openshift-apiserver $i -c openshift-apiserver|grep audit.k8s.io;done; for i in `oc get po -n openshift-oauth-apiserver|grep -v NAME|awk '{print $1}'`; do oc logs -n openshift-oauth-apiserver $i |grep audit.k8s.io/v1beta;done; for i in `oc get po -n openshift-kube-apiserver|grep kube|awk '{print $1}'`; do oc logs -n openshift-kube-apiserver $i -c kube-apiserver|grep audit.k8s.io/v1beta;done;
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.10.3 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:0056