-
Task
-
Resolution: Done
-
Normal
-
ACM 2.8.0, Submariner 0.15.0
-
False
-
None
-
False
-
-
-
Submariner Sprint 23-4, Submariner Sprint 23-5
-
No
Converting second comment of the following ticket into a separate Jira task:
https://issues.redhat.com/browse/ACM-2241
During deployment of Submariner via cli we are able to specify CatalogSource that should be used during the deployment of Submariner.
UI is missing such option.
As a result, deployment of Submariner via UI always tries to fetch the version from the official red hat registry.
The following scenarios could benefit from adding selection of CatalogSource to the Submariner UI:
- Customer in deployment of disconnected environment when official registry is not available will be able to specify alternative location for the deployment of Submariner.
- QE testing of downstream Submariner deployment via UI during the testing pre-release lifecycle currently is unavailable as the addon automatically tries to fetch the Submariner from the official registry and in pre-release testing it's not available.