Bug 1390471

Summary: [DOCS] Fix issues with exposing a non-secure registry section
Product: OpenShift Container Platform Reporter: Vikram Goyal <vigoyal>
Component: DocumentationAssignee: Ashley Hardin <ahardin>
Status: CLOSED DUPLICATE QA Contact: zhou ying <yinzhou>
Severity: medium Docs Contact: Vikram Goyal <vigoyal>
Priority: medium    
Version: 3.3.0CC: aos-bugs, jokerman, mmccomas
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: 2016-11-01 12:41:28 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 Vikram Goyal 2016-11-01 07:22:30 UTC 
From: https://access.redhat.com/documentation/en/openshift-container-platform/3.3/paged/installation-and-configuration/chapter-3-setting-up-the-registry#comment-1111071

"3.4.2.2. Exposing a Non-Secure Registry - A few things need to be changed here in the documentation

Check the health of the registry in your web browser: http://registry.example.com/healthz does not return any results. It is just a blank page. just HTTP 200/OK

About entry - OPTIONS='--selinux-enabled --insecure-registry=172.30.0.0/16 --insecure-registry registry.ose-node.openshift.com:443'

The above should be added on the client box from which you are trying to login. If you are reading the previous section, you may confuse and add this to master and all nodes. That is not required. Just add it to the client.

--insecure-registry registry.ose-node.openshift.com:443 should be --insecure-registry registry.ose-node.openshift.com:80. When you expose insecure registry you are not using https."

Once fixed, please leave a comment letting the reader know.
Comment 1 Ashley Hardin 2016-11-01 12:41:28 UTC 

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