-
Feature Request
-
Resolution: Done
-
Normal
-
None
-
openshift-4.12.z
1. Proposed title of this feature request
OLM - Specify the version of operator on Web Console when upgrading operator
2. What is the nature and description of the request?
Currently, there is the way to install specific version of operator using openshift CLI(and Web Console in near future) but no ways to upgrade into specific operator version from CLI and OCP web Console. My customer would like to specify not only y-stream(Minior) but also z-stream
3. Why does the customer need this? (List the business requirements here)
My Customer has been using OpenShift 4.12 with 3scale for API gateway platform since last year. The service has already launched in May this year.
They have two OpenShift environments.(Test and production)
As their internal rule, they firstly need to upgrade the test environment and test applications to make sure that the system works as intended, and then they upgrade the production environment.
At this time, they have upgraded in the manner described above but operator's version differences happened between the test and production environments because upgrade timing was different. The customer's internal policy does not allow to have different Operator versions between the test and production environments. If they upgrade the Operators of the test environment to have the same Operator versions of the production, they are needed to test applications on the test environment again and they can not ensure the stability of the production environment during the test is conducted.
- ODF
Test :4.12.3-rhodf
Production:4.12.4-rhodf - LocalStorage
Test:4.12.0-202305101515
Production:4.12.0-202306261055 - Logging
Test:5.7.1
Production:5.7.2 - Elasticsearch
Test:5.7.1
Production:5.7.2
- relates to
-
OCPSTRAT-812 [PRD scope] OLM 1.0 - Extension updates (F10)
- New