Bug 1387371

Document URL: 

https://docs.openshift.com/container-platform/3.3/install_config/registry/securing_and_exposing_registry.html#access-insecure-registry-by-exposing-route

Section Number and Name: 

Use the above url

Describe the issue: 


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

Issue 1
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
So asking to check in browser is misleading.

Instead ask for curl -v http://registry.example.com/healthz and expect a HTTP 200/OK is good enough

Issue 2:
 - 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. so be clear. Just say add it to the client. BTW, adding another statement that docker should be running on the client box.


Issue 3: 
--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.

Suggestions for improvement: 

Additional information: