Bug 1873632

Summary:	Create a registry requirements section (outline registry reqirements)
Product:	OpenShift Container Platform	Reporter:	Eric Rich <erich>
Component:	Documentation	Assignee:	Vikram Goyal <vigoyal>
Status:	CLOSED DUPLICATE	QA Contact:	Xiaoli Tian <xtian>
Severity:	high	Docs Contact:	Vikram Goyal <vigoyal>
Priority:	unspecified
Version:	4.6	CC:	aos-bugs, jmalde, jokerman
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:	2020-08-31 19:48:55 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 Eric Rich 2020-08-28 20:11:13 UTC

Document URL: https://docs.openshift.com/container-platform/4.5/installing/install_config/installing-restricted-networks-preparations.html#installation-about-mirror-registry_installing-restricted-networks-preparations

Section Number and Name: NEW

Describe the issue: We need to better outline and explain the technical requirements required by a registry for our tools to mirror content to them. 

Suggestions for improvement: 

To day we say: 
> The mirror registry can be any container registry that supports the most recent container image API, which is referred to as schema2.

However we could do a better job highlighting the fill list of technical requirements as customer are still trying to mirror content to registries that don't provide the technical requirements necessary to host mirrored content. 

Additional information: