Bug 1321101

Summary:	Source code suggested by template should support proxy
Product:	OKD	Reporter:	rodrigo ramalho <rdasilva>
Component:	Templates	Assignee:	kconner
Status:	CLOSED UPSTREAM	QA Contact:	XiuJuan Wang <xiuwang>
Severity:	low	Docs Contact:
Priority:	medium
Version:	3.x	CC:	aos-bugs, bparees, haowang, lionelve, mmccomas, plarsen, pweil, rdasilva, trankin
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	undefined	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-02-20 15:15:20 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 rodrigo ramalho 2016-03-24 16:30:42 UTC

Description of problem:
This is about Templates and Quickstarts. 

The quickstarts suggested by templates (eg: for EAP template it suggests kitchensink) doesn't have support to proxy, if the customer needs to use proxy he must adapt it or find another source code with STI configurations provided by default (eg: https://github.com/hodrigohamalho/openshift-jee-sample). 

IMHO all sources code suggested by templates should have proxy support. And the use of proxy should be on README of source code. 

eg: https://access.redhat.com/solutions/1758313 the source of this article should be on  kitchensink README.

Comment 1 Ben Parees 2016-03-24 17:14:19 UTC

The EAP images all support proxy via the HTTP_PROXY_* env variables, there may be a documentation problem here, but you should be able to configure the proxy by just adding the right env vars.

Over to Kevin to point to relevant doc or close when the doc is available.

Comment 2 rodrigo ramalho 2016-03-24 18:17:06 UTC

Yes, but as far as I Know this proxy variables is not included on maven build, because the source code (https://github.com/jboss-developer/jboss-eap-quickstarts/tree/7.0.x-develop/kitchensink) doesn't support STI.

Comment 6 rodrigo ramalho 2016-08-17 15:16:53 UTC

I'm reading it again, and I think it doesn't make sense anymore, because the S2i images has HTTP_PROXY_* env variables as Ben Parees said.

I will close it, thank you guys for your attention.

Regards,

Comment 7 Ben Parees 2016-08-17 15:18:33 UTC

i'd like to leave it open actually, we should make our images use the standard env variables (and continue to support this old env variable for backwards compatibility of course).

but severity is low since there is a valid way to make it work.

Comment 8 rodrigo ramalho 2016-08-17 15:24:01 UTC

The standard env variables that you refer are the listed below?

- http_proxy
- https_proxy
- ftp_proxy
- rsync_proxy
- no_proxy

Comment 9 Ben Parees 2016-08-17 15:34:14 UTC

yes, but i don't think ftp and rsync are relevant.

also we should support the uppercase versions of all of them.

Comment 11 kconner 2017-02-18 00:39:23 UTC

*** Bug 1349224 has been marked as a duplicate of this bug. ***

Comment 12 kconner 2017-02-18 00:48:26 UTC

*** Bug 1375416 has been marked as a duplicate of this bug. ***

Comment 13 Ben Parees 2017-02-20 15:15:20 UTC

closing as this is being tracked in JIRA now, which is the mechanism for middleware image issues.