Description of problem:
Customer has an OpenShift 3.1 cluster installed with multiple nodes. One is in a private data center and the other is in AWS. If customer attempts to specify a private git repo for use with an S2I, after specifying a secret, the pod never deploys, it hangs on pending waiting to talk with the repo. The node in the private data center is able to, using the same secret, specify the same private git repo for use with an S2I and the pod deploys.

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

How reproducible:
100% in their environment

Steps to Reproduce:
1. Create secret that allows for use with the private git repo
2. Start the S2I deployer 

Actual results:
AWS node deploy hangs

Expected results:
Deploy the node

Additional info:
The customer is able to ssh to each node and manually clone from the git repo in both the AWS and private data center nodes.