Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1704382

Summary:	[DOCS] Provide a way to find your registry
Product:	OpenShift Container Platform	Reporter:	Eric Rich <erich>
Component:	Documentation	Assignee:	Brandi Munilla <bmcelvee>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Wenjing Zheng <wzheng>
Severity:	high	Docs Contact:	Vikram Goyal <vigoyal>
Priority:	low
Version:	4.1.0	CC:	aos-bugs, jokerman, mmccomas
Target Milestone:	---
Target Release:	4.1.0
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-06-03 13:54:51 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:
Bug Depends On:	1704381
Bug Blocks:

Description Eric Rich 2019-04-29 15:58:50 UTC

Document URL: https://docs.openshift.com/container-platform/4.1/registry/accessing-the-registry.html

Section Number and Name: Accessing the Registry

Describe the issue: 

You tell people to run:

> podman login -u openshift -p $(oc whoami -t) <registry_ip>:<port>

But don't tell them how to find the registry_ip and or port 

Suggestions for improvement: 

You need to tell the user how to look up the route for the registry from the `openshift-image-registry` namespace. 

> oc get routes -n openshift-image-registry

It is likely going to be the `default-route` if you have the operator create this for you. 


Additional information:

Comment 1 Eric Rich 2019-04-29 15:59:36 UTC

Be aware of https://bugzilla.redhat.com/show_bug.cgi?id=1704381 as it needs to happen before addressing this bug.

Comment 2 Eric Rich 2019-04-29 16:43:46 UTC

We should document: 

> $ podman login -u openshift -p $(oc whoami -t) $(oc get route -n openshift-image-registry default-route -o jsonpath='{.status.ingress[*].host}{"\n"}')

We may need to provide a note about `--tls-verify=false` as the registry (by default may not use trusted certificate - this all depends on configuration). 

> $ podman login --tls-verify=false -u openshift -p $(oc whoami -t) $(oc get route -n openshift-image-registry default-route -o jsonpath='{.status.ingress[*].host}{"\n"}')

Comment 3 Brandi Munilla 2019-05-21 19:17:06 UTC

Thanks again, Eric! I'm addressing the "accessing" procedure in the following PR: 
https://github.com/openshift/openshift-docs/pull/14986

This is another one of the handful of registry-related bugs I'm addressing in the single PR.

Comment 4 Brandi Munilla 2019-05-21 20:43:53 UTC

Wenjing, would you mind please taking a look too? Thanks!

Comment 5 Wenjing Zheng 2019-05-22 06:12:58 UTC

Comments are added to pull request.

Comment 6 Wenjing Zheng 2019-05-29 05:54:56 UTC

Since some comments are not addressed, so move this bug to assigned.

Comment 7 Wenjing Zheng 2019-05-31 01:59:11 UTC

I think I can move this bug to verified, just a small issue which I have commented in the pr.

Comment 8 Brandi Munilla 2019-05-31 16:59:32 UTC

Thanks so much! PR merged.