Bug 1296609

Summary: [DOCS] [SME] Registry Service IP needed for Accessing the Registry
Product: OpenShift Container Platform Reporter: Josh Preston <jpreston>
Component: DocumentationAssignee: Vikram Goyal <vigoyal>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Vikram Goyal <vigoyal>
Severity: low Docs Contact: Vikram Goyal <vigoyal>
Priority: low    
Version: 3.1.0CC: aos-bugs, jokerman, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-28 05:36:46 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:

Description Josh Preston 2016-01-07 16:18:24 UTC 
Document URL: 

Section Number and Name: 

Section 2.5.5 Accessing the Registry

Describe the issue: 

The previous section shows the pods IP address and implies one should specify the pod ip when accessing the registry which when run, returns a CA insecure registry error when connecting.

Suggestions for improvement: 

It should be noted how one obtains the docker-registry service ip address with “oc get svc” command and then use that as the IP address.

Additional information: