Bug 1565034

Summary: [trello XzkI9of3][RFE] Add checkbox corresponding to `--insecure-registry` in 'Deploy Image' page
Product: OpenShift Container Platform Reporter: Xingxing Xia <xxia>
Component: RFEAssignee: Samuel Padgett <spadgett>
Status: CLOSED WONTFIX QA Contact: Xiaoli Tian <xtian>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.10.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: 2019-06-12 11:55:11 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 Xingxing Xia 2018-04-09 08:22:33 UTC 
Description of problem:
In 'Deploy Image' page beneath 'Image Name', search image from self-signed registry, it displays error (see below)

Version-Release number of selected component (if applicable):
v3.10.0-0.16.0

How reproducible:
Always

Steps to Reproduce:
1. Prepare secret
REGISTRY=<company-internal-registry> MYUSER=unused MYPASSWORD=<token> MYEMAIL=unused
oc  create secret docker-registry mysecret --docker-server=$REGISTRY  --docker-username=$MYUSER --docker-password=$MYPASSWORD  --docker-email=$MYEMAIL
oc secrets link default mysecret --for=pull

2. In 'Deploy Image' page beneath 'Image Name', search image <company-internal-registry>/xxia-proj/hello-openshift

3. Check CLI as comparison.
1> oc new-app <company-internal-registry>/xxia-proj/hello-openshift --name ho
2> oc new-app <company-internal-registry>/xxia-proj/hello-openshift --name ho --insecure-registry

Actual results:
2. It displays error:
Internal error occurred: Get https://<company-internal-registry>/v2/: x509: certificate signed by unknown authority
The image may not exist or it may be in a secure registry. Check that you have entered the image name correctly or create an image pull secret with your image registry credentials and try again.

3.
1> Without `--insecure-registry`, it displays similar error like web:
Docker registry lookup failed: Get https://<company-internal-registry>/v2/: x509: certificate signed by unknown authority

2> With `--insecure-registry`, it can succeed:
--> Found Docker image e1fdecf (12 days old) from <company-internal-registry> for "<company-internal-registry>/xxia-proj/hello-openshift"
...

Expected results:
2. Suggest web has checkbox corresponding to `--insecure-registry`

Additional info:
Comment 3 Kirsten Newcomer 2019-06-12 11:55:11 UTC 
With the introduction of OpenShift 4, Red Hat has delivered or roadmapped a substantial number of features based on feedback by our customers.  Many of the enhancements encompass specific RFEs which have been requested, or deliver a comparable solution to a customer problem, rendering an RFE redundant.

This bz (RFE) has been identified as a feature request not yet planned or scheduled for an OpenShift release and is being closed. 

If this feature is still an active request that needs to be tracked, Red Hat Support can assist in filing a request in the new JIRA RFE system, as well as provide you with updates as the RFE progress within our planning processes. Please open a new support case: https://access.redhat.com/support/cases/#/case/new 

Opening a New Support Case: https://access.redhat.com/support/cases/#/case/new 

As the new Jira RFE system is not yet public, Red Hat Support can help answer your questions about your RFEs via the same support case system.