Bug 1718163
Summary: | Docs about Exposing the Openshift internal registry are not correct for 4.1.0 | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Praveen Kumar <prkumar> |
Component: | Documentation | Assignee: | Brandi Munilla <bmcelvee> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Wenjing Zheng <wzheng> |
Severity: | high | Docs Contact: | Vikram Goyal <vigoyal> |
Priority: | unspecified | ||
Version: | 4.1.0 | CC: | adam.kaplan, aos-bugs, bmcelvee, jokerman, mmccomas, obulatov, sponnaga, ssadeghi, wzheng |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | 4.1.z | ||
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: | 2019-08-02 19:32:34 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: | |
Embargoed: |
Description
Praveen Kumar
2019-06-07 06:53:39 UTC
Pulling comment from Github issue: https://github.com/openshift/openshift-docs/issues/15113#event-2396784723 Which section(s) is the issue in? Exposing a non-secure registry manually What needs fixing? As of now when you follow this section you are not able to expose the unsecured registry also the registry service is part of openshift-image-registry namespace but in the document it shows default namespace. Does this document tested or still in the progress ? Adam and I met to start overhauling this content. Draft PR open: https://github.com/openshift/openshift-docs/pull/15370 Need validation so putting in 4.1.3 but can be validated anytime Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:1589 *** Bug 1717297 has been marked as a duplicate of this bug. *** |