Bug 1280503

Summary:	Registry docs: ImageStreams do not support 3rd party registries that require authentication
Product:	OpenShift Container Platform	Reporter:	Josep 'Pep' Turro Mauri <pep>
Component:	Documentation	Assignee:	Vikram Goyal <vigoyal>
Status:	CLOSED DUPLICATE	QA Contact:	Vikram Goyal <vigoyal>
Severity:	medium	Docs Contact:	Vikram Goyal <vigoyal>
Priority:	medium
Version:	3.0.0	CC:	aos-bugs, jokerman, mmccomas
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-30 01:12:06 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 Josep 'Pep' Turro Mauri 2015-11-11 22:46:26 UTC

Document URL: 
https://docs.openshift.com/enterprise/3.0/architecture/infrastructure_components/image_registry.html#authentication

Section Number and Name:

Architecture > Image Registry > Third Party Registries > Authentication

Describe the issue:

The section describes integration with 3rd party registries, and it seems to imply that ImageStreams work with 3rd party registries (with the caveat of manual import-image) even if they require authentication.

At this time, this is not the case though, see Bug 1271328: ImageStreams do not work with external registries that require authentication.

Suggestions for improvement:

In the Authentication section, explain that ImageStreams do not work. It can be possible to pull images from a registry by referencing them directly (not via an ImageStream) and providing credentials via a secret; this might also be worth mentioning as an alternative (with further reduced functionality) but I have not confirmed how it works.

Additional information:

The section would change again once changes for bug 1271328 are implemented.

Comment 1 Vikram Goyal 2016-05-30 01:12:06 UTC


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