Components deployed by HCO 1.4.1 on OKD 4.8 are still reported as using k8s 1.22 deprecated APIs

[Simone Tiraboschi]

Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug

/kind enhancement

What happened:
Components deployed by HCO 1.4.1 on OKD 4.8 are still reported as using k8s 1.22 deprecated APIs:
{"kind":"Event","apiVersion":"audit.k8s.io/v1","level":"Metadata","auditID":"7f673d47-21c8-41c0-98f9-14d53136ed5e","stage":"ResponseComplete","requestURI":"/apis/extensions/v1beta1/ingresses?allowWatchBookmarks=true\u0026resourceVersion=6552407\u0026timeoutSeconds=316\u0026watch=true","verb":"watch","user":{"username":"system:serviceaccount:kubevirt-hyperconverged:cdi-sa","uid":"2b50ba88-2a0f-451a-9a30-2ff0997c69c6","groups":["system:serviceaccounts","system:serviceaccounts:kubevirt-hyperconverged","system:authenticated"],"extra":{"authentication.kubernetes.io/pod-name":["cdi-deployment-7cdb7fd7b6-h4z7n"],"authentication.kubernetes.io/pod-uid":["a9d40e5c-a42e-40f2-b733-9d277ee05c28"]}},"sourceIPs":["10.46.11.90"],"userAgent":"cdi-controller/v0.0.0 (linux/amd64) kubernetes/$Format","objectRef":{"resource":"ingresses","apiGroup":"extensions","apiVersion":"v1beta1"},"responseStatus":{"metadata":{},"status":"Success","message":"Connection closed early","code":200},"requestReceivedTimestamp":"2021-10-01T07:23:07.590460Z","stageTimestamp":"2021-10-01T07:23:31.038696Z","annotations":{"authorization.k8s.io/decision":"allow","authorization.k8s.io/reason":"RBAC: allowed by ClusterRoleBinding \"cdi-sa\" of ClusterRole \"cdi\" to ServiceAccount \"cdi-sa/kubevirt-hyperconverged\"","k8s.io/deprecated":"true","k8s.io/removed-release":"1.22"}}

What you expected to happen:
No warnings about deprecated APIs on OKD 4.8

How to reproduce it (as minimally and precisely as possible):
Deploy HCO 1.4.1 on OKD 4.8 and then run something like:

for i in `oc adm node-logs --role=master --path=kube-apiserver/|cut -f 2 -d\ |grep audit`; do oc adm node-logs master0... --path=kube-apiserver/$i | grep "\"k8s.io/deprecated\":\"true\"" | grep "1\.22"; done`

Anything else we need to know?:

Environment:

• HCO version (use oc get csv -n kubevirt-hyperconverged): 1.4.1
• Kubernetes version (use kubectl version): OKD 4.8
• Cloud provider or hardware configuration:
• Install tools:
• Others:

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[Simone Tiraboschi]

Fixed in v1.4.2