Adds proxies to builders docs (quay#1132)

Co-authored-by: Steven Smith <[email protected]>

Author: stevsmit

modules/builders-virtual-environment.adoc

@@ -137,7 +137,7 @@ $ mv ca.crt build-cluster.crt
 
 .. Click *Actions* -> *Edit Secret*.
 
-.. Add an appropriate _virtual builds_ configuration with the following reference: 
+.. Add an appropriate _virtual builds_ configuration using the following as a reference: 
 +
 [source,yaml]
 ----
@@ -179,6 +179,9 @@ BUILD_MANAGER:
         NODE_SELECTOR_LABEL_VALUE: ""
         SERVICE_ACCOUNT_NAME: <sample_service_account_name>
         SERVICE_ACCOUNT_TOKEN: <sample_account_token> <11>
+        HTTP_PROXY: <http://10.0.0.1:80>
+        HTTPS_PROXY: <http://10.0.0.1:80>
+        NO_PROXY: <hostname.example.com>
 ----
 +
 <1> The build route is obtained by running `$ oc get route -n` with the namespace of your {productname-ocp} deployment. A port must be provided at the end of the route, and it should use the following format: `[quayregistry-cr-name]-quay-builder-[ocp-namespace].[ocp-domain-name]:443`.
@@ -234,6 +237,9 @@ BUILD_MANAGER:
         NODE_SELECTOR_LABEL_VALUE: ""
         SERVICE_ACCOUNT_NAME: quay-builder
         SERVICE_ACCOUNT_TOKEN: "eyJhbGciOiJSUzI1NiIsImtpZCI6IldfQUJkaDVmb3ltTHZ0dGZMYjhIWnYxZTQzN2dJVEJxcDJscldSdEUtYWsifQ"
+        HTTP_PROXY: <http://10.0.0.1:80>
+        HTTPS_PROXY: <http://10.0.0.1:80>
+        NO_PROXY: <hostname.example.com>
 ----
 
 .. Click *Save* on the *Edit Secret* page.

modules/prepare-ocp-for-bare-metal-builds.adoc

@@ -207,6 +207,9 @@ BUILD_MANAGER:
     SSH_AUTHORIZED_KEYS: <11>
     - <ssh-rsa 12345 [email protected]>
     - <ssh-rsa 67890 [email protected]>
+    HTTP_PROXY: <http://10.0.0.1:80>
+    HTTPS_PROXY: <http://10.0.0.1:80>
+    NO_PROXY: <hostname.example.com>
 ----
 <1> Obtained by running the following command: `$ oc get route quayregistry-quay-builder -n ${QUAY_PROJECT} -o jsonpath='{.spec.host}'`.
 <2> The hostname for your Redis service.

modules/setting-up-builds-aws.adoc

@@ -33,6 +33,9 @@ You can follow the steps in "Configuring bare metal builds for {productname-ocp}
       SSH_AUTHORIZED_KEYS: <2>
       - <ssh-rsa 12345 [email protected]>
       - <ssh-rsa 67890 [email protected]>
+      HTTP_PROXY: <http://10.0.0.1:80>
+      HTTPS_PROXY: <http://10.0.0.1:80>
+      NO_PROXY: <hostname.example.com>
 ----
 <1> Specifies an AMI name where _builds_ will be run. Unlike bare metal _builds_, these container _builds_ are done directly within an ephemeral EC2 instance. This AMI must utilize ignition and contain a docker. The AMI shown in this example is used by {quay.io} for its build system.
 <2> Allows public SSH keys to be added to the build environment for remote troubleshooting access. This key, or keys, should correspond to the private key that an admin or developer will use to SSH into the build worker for debugging purposes. This key can be obtained by establishing an SSH connection to the remote host using a specific SSH key and port. For example: `$ ssh -i /path/to/ssh/key/set/in/ssh_authorized_keys -p 9999 core@localhost`.