Bug 1740221 - Better documentation around enabling registry.redhat.io
Summary: Better documentation around enabling registry.redhat.io
Keywords:
Status: NEW
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Vikram Goyal
QA Contact: Xiaoli Tian
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-12 13:45 UTC by Brian J. Atkisson
Modified: 2019-08-12 13:45 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.