-
Task
-
Resolution: Obsolete
-
Undefined
-
None
-
None
-
None
-
False
-
False
-
Undefined
-
Description
A concern of the OLM/catalog cannot still work after 4.9 GA when/if that be shipped with bundles/distributions that use the deprecated/removed APIs in 1.22 was raised in a discussion over this topic.
In this way, the goal of this task is only to ensure that the whole OLM/catalog will not be affected in this scenario and are prepared to deal with. The specific bundle/distribution will not work, but that must not affect or impact any other distributions or the catalog and the OLM itself.
PS.; We have initiatives to try to avoid this scenario as much as possible for OCP images, however, we cannot ensure the custom images.
Acceptance Criteria
- OLM as all compatible versions with k8s 1.22/ocp4.9 working well as expected when installed on OCP cluster version 4.9 and k8s cluster version 1.22 using any index image which has distributions with the removed APIs (https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-22)
- is blocked by
-
OPRUN-2222 Add a warning to validation for v1beta1 deprecations in an operator bundle
-
- Closed
-