Description of problem:

If the http/https proxy is defined during ansible installation of OpenShift in master config, it is saved in as HTTP_PROXY <IPADDRESS>:<PORT>. 
Unfortunately, when you try to install new application in OpenShift the build fails as the npm repository is not accessible. 

npm http fetch GET https://registry.npmjs.org/gulp-rename/-/gulp-rename-1.2.2.tgz
npm info retry will retry, error on last attempt: Error: tunneling socket could not be established, cause=connect EINVAL 0.0.31.144:80 - Local (0.0.0.0:0)

I1103 10:10:33.107943       1 sti.go:585] ---> Setting npm http proxy to <IPADDRESS>:<PORT>
I1103 10:10:34.019025       1 sti.go:585] ---> Setting npm https proxy to <IPADDRESS>:<PORT>

This is caused, because OpenShift will pass the proxy information to deployment as http_proxy is only <IPADDRESS>:<PORT>. However, the build expects to be http_proxy=http://<IPADDRESS>:<PORT>.
The workaround would be to set the all http_proxy parameters in master config to http:// (or https:// ). 

Question is there possibility to configure it so it will be automatically passed with http.

Version-Release number of selected component (if applicable):

OpenShift Container Platform 3.X

How reproducible:

Set in master-config.yaml current parameters;

kubernetesMasterConfig:
  admissionConfig:
    pluginConfig:
      BuildDefaults:
        configuration:
          apiVersion: v1
          env:
          - name: HTTP_PROXY
            value: http://<IPADDRESS>:<PORT>
          - name: HTTPS_PROXY
            value: http://<IPADDRESS>:<PORT>
          - name: NO_PROXY
            value: .cluster.local,10.84.0.0,10.85.0.0,172.30.133.28,0.0.0.0
          - name: http_proxy
            value: http://<IPADDRESS>:<PORT>
          - name: https_proxy
            value: http://<IPADDRESS>:<PORT>
          - name: no_proxy
            value: .cluster.local,10.84.0.0,10.85.0.0,172.30.133.28,0.0.0.0
          kind: BuildDefaultsConfig
  apiServerArguments:



Actual results:


Expected results:


Additional info: