Bug 1740221

Summary: Better documentation around enabling registry.redhat.io
Product: OpenShift Container Platform Reporter: Brian J. Atkisson <batkisso>
Component: DocumentationAssignee: Vikram Goyal <vigoyal>
Status: NEW --- QA Contact: Xiaoli Tian <xtian>
Severity: unspecified Docs Contact: Vikram Goyal <vigoyal>
Priority: unspecified    
Version: unspecifiedCC: aos-bugs, 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: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Brian J. Atkisson 2019-08-12 13:45:44 UTC
Document URL: https://access.redhat.com/documentation/en-us/openshift_container_platform/4.1/html/registry/registry-options#registry-authentication-enabled-registry-overview_registry-options

Section Number and Name: 3.4. Authentication enabled Red Hat registry

Describe the issue: 

This section should include actual examples (yaml and all) of the steps required for enabling registry.redhat.io. It tells you at a high level what to do, but then it stops.


Suggestions for improvement: 

1. Instruct (or link) on how to get a terms-based-registry service account
2. Add sample yaml for each of these points:

- OpenShift namespace. Your credentials must exist in the OpenShift namespace so that the imagestreams in the OpenShift namespace can import.
    
- Your host. Your credentials must exist on your host because Kubernetes uses the credentials from your host when it goes to pull images. 

This second point (Your host) is entirely unclear as to what is actually required.


Additional information: 

Given enabling the ubi images is something every openshift admin has to do, this  process should be highly (even overly) documented.