Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1552453

Summary: [RFE] Installer to support import control on imagestream and template
Product: OpenShift Container Platform Reporter: Takayoshi Kimura <tkimura>
Component: RFEAssignee: Paul Weil <pweil>
Status: CLOSED DUPLICATE QA Contact: Xiaoli Tian <xtian>
Severity: low Docs Contact:
Priority: low    
Version: 3.7.0CC: aos-bugs, jokerman, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-07 08:05:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Takayoshi Kimura 2018-03-07 07:57:44 UTC
Description of problem:

It'd would be nice to have more control on which imagestream and template imported at installation time. Users don't want to misuse products which needs another subscription, and don't want these items listed on the web console catalog.

xpaas templates includes both supported and extra subscription required products. JWS and SSO are supported, others products are not supported by OpenShift subscription.

quickstart includes various pure examples and also 3scale amp (API management platform).

Version-Release number of selected component (if applicable):

openshift-ansible-3.7.23-1.git.0.bc406aa.el7.noarch

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:

All ImageStream and Template imported, extra effort is needed to organize them

Expected results:

Able to specify which products will be imported at installation time. At least an option to disable all products out of OpenShift subsription support scope.

Additional info:

Comment 1 Takayoshi Kimura 2018-03-07 08:05:41 UTC
Found duplicate BZ, closing.

*** This bug has been marked as a duplicate of bug 1375455 ***