Using Proxy Variables During Worker Node Installation

OneTrust Data Discovery offers optional proxy support if your infrastructure is configured to have network traffic from the installer virtual machine (from which the deployment script is executed to deploy) routed through a Proxy server.

In order to support proxy communication during the worker node installation, additional variables can be configured in the following:

  • During the given terminal session prior to triggering the installation scripts. The following variables are available to account for possible case sensitivity based on your chosen services and software:

    CODE 
    HTTPS_PROXY
HTTP_PROXY
NO_PROXY
https_proxy
http_proxy
no_proxy

  • During guided installation flow to establish custom options for worker node service properties

To configure proxy variables for installation

Prior to this configuration, the following proxy environment variable needs to be set for the pods to use to connect to our OneTrust cloud application:

CODE 
#Optional proxy server, used when connecting to OneTrust
export HTTP_PROXY=""
  1. In the etc/environment file, create a no_proxy variable.

    Installation Type

    Instruction

    localhost references

    These IP addresses are constant.

    CODE 
    localhost,127.0.0.1

    Onebox installations using proxy

    Add the following static IP addresses used by the microk8s cluster to the no_proxy and NO_PROXY variables:

    CODE 
    microk8s, 10.1.0.0/16,10.152.183.0/24

    Above IPs are constant for microk8s unless microk8s CIDR has been changed.
  2. Retrieve the virtual machine's internal IP and hostname:
    CODE 
    #Examples

$ hostname -i
172.18.0.27

$ hostname
onebox-auto-ubuntu-1804-qa
  3. Append all the values (comma separated) from the above steps to configure the variable:

    no_proxy

    CODE 
    no_proxy=localhost,127.0.0.1,172.18.0.27,onebox-auto-ubuntu-1804-qa

    NO_PROXY

    CODE 
    NO_PROXY=localhost,127.0.0.1,172.18.0.27,onebox-auto-ubuntu-1804-qa
  4. The remaining four (4) variables have the same value. The following example uses a no-auth proxy (http://<server>:<port>. Users can use an auth proxy as well (http://<user>:<pwd>@<server>:<port>).
    CODE 
    HTTPS_PROXY=http://40.85.184.25:3128
HTTP_PROXY=http://40.85.184.25:3128
http_proxy=http://40.85.184.25:3128
https_proxy=http://40.85.184.25:3128
  5. Combine all applicable variables:
    CODE 
    HTTPS_PROXY=http://40.85.184.25:3128
HTTP_PROXY=http://40.85.184.25:3128
http_proxy=http://40.85.184.25:3128
https_proxy=http://40.85.184.25:3128
no_proxy=localhost,127.0.0.1,10.0.3.5,onebox-auto-ubuntu-1804-qa
NO_PROXY=localhost,127.0.0.1,10.0.3.5,onebox-auto-ubuntu-1804-qa

    For Onebox, the variables should contain the two microk8s CIDRs that are appended to the no proxy variables, as listed above in Step 1:

    CODE 
    no_proxy=localhost,127.0.0.1,10.1.0.0/16,10.152.183.0/24,10.0.3.5,onebox-auto-ubuntu-1804-qa
NO_PROXY=localhost,127.0.0.1,10.1.0.0/16,10.152.183.0/24,10.0.3.5,onebox-auto-ubuntu-1804-qa
  6. Add all variables to the /etc/environment file with the following command:
    CODE 
    sudo vi /etc/environment
  7. Save the file, then source it with the following command:
    CODE 
    source /etc/environment

To configure installer customizations during Guided Installation

  1. Create a new worker node by following the guided installation path. For more information, see Guided Worker Node Installation Overview.
  2. In the Custom Options section in the Advanced Options screen, establish an environment variable for your service(s). Click the Add icon to add additional variables.
    CODE 
    -Dhttp.proxyHost= 
-Dhttp.proxyPort=
-Dhttps.proxyHost=
-Dhttps.proxyPort=
-Dhttp.proxyUser=
-Dhttp.proxyPassword=
-Dhttps.proxyUser=
-Dhttps.proxyPassword=
-Dhttp.nonProxyHosts=