-
Feature Request
-
Resolution: Unresolved
-
Undefined
-
None
-
openshift-4.20
-
None
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
-
None
1. Proposed title of this feature request
Allow OLM-operator maintainers to define a minimum OpenShift Version necessary.
2. What is the nature and description of the request?
For any Operator that is implementing new functionality which is not compatible with previous versions, a minOpenShiftVersion would allow the Operator to signal the incompatibility.
This Feature is specifically requesting Semantic X.Y.Z versioning.
Note: There is a minKubeVersion, but that is specifically not what is necessary in this instance as the versioning needed is at the OpenShift Product level.
3. Why does the customer need this? (List the business requirements here)
Without, the new functionality could cause breakage in end installations. One such example being:
- Operators shipping with network policies may require OCP cluster upgrade before they can be upgraded
If this Feature were delivered, the associated minor Versions could have been specified in Operators that were making use of the new NetworkPolicy.
4. List any affected packages or components.
I believe OLMv0 + OLMv1.