-
Notifications
You must be signed in to change notification settings - Fork 2k
Description
Is your feature request related to a problem? Please describe.
Description:
- Using the NGINX Operator v3.1.0 in production environment and v3.2.3 in test environment
- We were unable to use the image 'private-registry.nginx.com/nginx-ic-nap-dos/nginx-plus-ingress:3.7.2-ubi' with their NGINX Ingress since it is not compatible with the new operator version.
- Why earlier version of the operator (e.g. 2.4.2) are not available to deploy?
Initial problem:
"We are using the NGINX Operator 3.1.0 in our production environment and the new 3.2.3 in our test environment. Unfortunately, we cannot revert to the previous version in the test environment because we only have one available in the OperatorHub.
This causes many additional problems. For example, we want to upgrade our IC Image image: 'private-registry.nginx.com/nginx-ic-nap-dos/nginx-plus-ingress:3.7.2-ubi' to the new 5.x versions, but we cannot do this because the new operator cannot handle the old images, and we cannot use the old operator.
We have received a new license type. We also believe that with this license, we cannot pull old images.
The operator enters a crash loop when we use old secret types, and the image does not pull version 3, as the operator probably no longer supports it (assumption)."
References:
File-based catalogs (FBC) https://redhat-openshift-ecosystem.github.io/operator-pipelines/users/fbc_onboarding/
https://olm.operatorframework.io/docs/reference/file-based-catalogs/
Metadata
Metadata
Assignees
Labels
Type
Projects
Status