Bug 1390471 - [DOCS] Fix issues with exposing a non-secure registry section
Summary: [DOCS] Fix issues with exposing a non-secure registry section
Keywords:
Status: CLOSED DUPLICATE of bug 1387371
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Ashley Hardin
QA Contact: zhou ying
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-01 07:22 UTC by Vikram Goyal
Modified: 2017-03-08 18:43 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-01 12:41:28 UTC
Target Upstream Version:


Attachments (Terms of Use)

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 ***


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