Bug 1404957

Summary:	[RFE] Configurable default docker registry used by oc new-app
Product:	OpenShift Container Platform	Reporter:	Kenjiro Nakayama <knakayam>
Component:	RFE	Assignee:	Michal Fojtik <mfojtik>
Status:	CLOSED DEFERRED	QA Contact:	Xiaoli Tian <xtian>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.3.0	CC:	aos-bugs, cewong, erich, jkaur, jokerman, knakayam, mbarrett, mfojtik, mmccomas
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
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-12 13:54:36 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 Kenjiro Nakayama 2016-12-15 08:38:34 UTC

1. Proposed title of this feature request

- [RFE] Configurable default docker registry used by oc new-app

3. What is the nature and description of the request?

- When oc new-app <GIT> and failed to search image in local imageStream nor registry.redhat.com, it will try to access docker.io to find it. We would like to configure the default registry docker.io with some other registries.

4. Why does the customer need this? (List the business requirements here)

- The customer uses OpenShift on disconnected environment and new-app always lookup docker.io and produces error as "no such host". They want to stop it.

5. How would the customer like to achieve this? (List the functional requirements here)

- Disable to lookup docker.io by default or configure to lookup other registries.

Comment 5 Cesar Wong 2017-08-18 12:04:09 UTC

Assigned to Michal, who should be able to answer about the registry lookup.

Comment 6 Michal Fojtik 2017-08-18 12:56:59 UTC

In more recent version of OpenShift (>3.5) we already added `imagePolicyConfig.AllowedRegistriesForImport` option in master config which can be used to whitelist registries for image import. The 'docker.io' is whitelisted by default, but by removing it from this list your should get nicer error message when trying to new-app using docker.io saying that importing the image is not allowed.

Comment 8 Eric Rich 2018-03-12 13:54:36 UTC

This bug has been identified as a dated (created more than 3 months ago) bug. 
This bug has been triaged (has a trello card linked to it), or reviewed by Engineering/PM and has been put into the product backlog, 
however this bug has not been slated for a currently planned release (3.9, 3.10 or 3.11), which cover our releases for the rest of the calendar year. 

As a result of this bugs age, state on the current roadmap and PM Score (being below 70), this bug is being Closed - Differed, 
as it is currently not part of the products immediate priorities.

Please see: https://docs.google.com/document/d/1zdqF4rB3ea8GmVIZ7qWCVYUaQ7-EexUrQEF0MTwdDkw/edit for more details.