As per the e-mail

WARNING: Kubernetes API removals on 1.25/1.26 might impact your Operator

During the Kube 1.25, 1.26 timeframes more deprecated API's will be removed as per

Camila Macedo

8:58 AM (29 minutes ago)

to operatorframework-pm, aos-devel

Hi All,

Some APIs versions are deprecated and will NO longer be served on the Kubernetes version 1.25/1.26 and consequently on Openshift 4.12/4.13. For further information, check the guide[0].

💁 What does that mean for you:

You must ensure that you no longer use these API versions.

Otherwise, any operation of your project which requires these versions will fail.

🔥 We can NOT detect it as it was done for 4.9 to help you out. Resources using these APIs are not provided via the bundle manifests, then CVP will NOT be able to check them.

✨ We recommend you plan with your QA test your Operator on Openshift 4.11 and perform a full regression test looking for the usage of the deprecated APIs using the APIRequestCount[1] and checking the Operator logs as described below.

⚠️You MUST ensure that you provide solutions for OpenShift 4.11+ (at least) that don’t use the Kubernetes API versions removed in Openshift 4.12/k8s 1.25.

Keep in mind that cluster admins MUST have installed a version of your Operator that can work successfully in Openshift 4.12+ before upgrading the OCP cluster from 4.11 to 4.12.

Otherwise, they might face workflow issues.
.
.
.

We'll need to evaluate the operator against these API changes to ensure we are prepared to deal with them.

See Kubernetes Deprecation Guide