It is in new-app. When the template broker is enabled in 3.6 you'll be able to parameterize that as an admin and have the catalog obey it.
On Mar 31, 2017, at 11:49 PM, Andrew Lau <[email protected]> wrote: >From earlier, it seems it's hard coded into the web console https://github.com/openshift/origin-web-console/blob/ce35daaa1c546b74161e15fc4a19c028fbb8d631/app/scripts/controllers/create/browseCategory.js#L104 I'm not sure about oc new-app though On Sat, 1 Apr 2017 at 06:57 Gaurav P <[email protected]> wrote: Mirroring the openshift project, I've been able to create a second project with the same shared-resource-viewer Role added to group system:authenticated. oc new-project common oc export role shared-resource-viewer -n openshift | oc create -f - oc policy add-role-to-group shared-resource-viewer system:authenticated --role-namespace=common Images and templates in this project can then be shared by other projects. However getting the UI to display these images and templates is proving to be a challenge: This *policyConfig *option in *master-config.yaml* seems promising: *OpenShiftSharedResourcesNamespace* (string): The namespace where shared OpenShift resources are located, such as shared templates. But when I change this from openshift (default) to common, and delete all the default images, imagestreams and templates in the openshift namespace, the UI catalog states that no images or templates were found in the openshift namespace. This leads me to believe the UI is not honoring the above setting, or my understanding of that parameter is incorrect. Further, if I take away the shared-resource-viewer role from system:authenticated in the openshift namespace, the following errors appear on the UI catalog: Failed to list templates/v1 (403) Failed to list imagestreams/v1 (403) Any pointers would be much appreciated - Gaurav On Wed, Mar 29, 2017 at 9:46 AM, Subhendu Ghosh <[email protected]> wrote: It would be good to allow for a installation specific namespace to be added to the search path for imagestream Subhendu On Mar 28, 2017 22:34, "Jordan Liggitt" <[email protected]> wrote: Images exist outside namespaces. They are accessed via imagestreams, which are namespaced. You can make imagestreams and templates available from namespaces other than the openshift namespace, but the CLI and UI only look in the current project and the openshift project by default. > On Mar 28, 2017, at 10:12 PM, Andrew Lau <[email protected]> wrote: > > Hi, > > Is it possible to create another global project similar to the `openshift` namespace for sharing images/imagestreams/template? > > Docs seem point out imagestreams and templates are made global but couldn't find reference to images. They are also made available if pushed to the registry? > > Thanks > _______________________________________________ > users mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/users _______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users _______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users _______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users _______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
