Hide Forgot
Description of problem: It would be nice to have a Docker image that comes with the xPaaS registry so that customers didn't have to set that up themselves Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
What are you defining as the "xpaas registry"? With 3.4 you can now choose to start oc cluster up with either the centos imagestreams or the rhel imagestreams, if you choose the rhel imagestreams, the xpaas imagestreams will be available, but it does not affect what templates/quickstarts will be available.
I would like to have the templates available for EAP, BRMS, etc. Is this the flag, "# Use a different set of images oc cluster up --image="registry.example.com/origin" --version="v1.1"" I started 3.4 with the centos7 image stream. What would I enter for the RHEL image? I can move this to documentation if the functionality is already there. Thanks, Jeremy
the new flag is --image-streams='centos7': Specify which image streams to use, centos7|rhel7 but that won't get you the templates, only the imagestreams.
Could we add a flag to pull in imagestreams?
I'd rather not add one off flags just to import additional imagestreams (or templates) when we already have commands to do that (oc create). it's easy enough to wrap a script around cluster up to import additional artifacts once the cluster is up, if you want to do that. No to mention the potential maintenance headache if the xpaas team relocates their artifacts (or your cluster up environment doesn't have network connectivity). Also I believe using the xpaas images requires specific licensing, so making it trivial to use them from oc cluster up means people may use them w/o realizing they are not licensed to do so.
We discussed this and feel that including xPaaS imagestreams and templates makes more sense as a CDK feature than an oc cluster up feature, so we are transferring this RFE to that product/component.