Description

Customers may configure their clusters with a cluster-wide egress proxy in order to securely access resources outside their network. Proxy settings are defined and managed by users through a global Proxy object.

This story covers setting the 3 proxy variables (HTTP_PROXY, HTTPS_PROXY, NO_PROXY) on Windows instances. 

Engineering Details

Since OLM injects these values into the WMCO pod, WMCO can read them from its own environment. WMCO will then publish the environment variables into the windows-services ConfigMap. WICD will compare the value of each variable in the ConfigMap to the value on the instance. If there is a discrepancy, WICD will update the values and reboot the instance so Windows services inherit the desired values. See enhancement proposal for more details.

Note that on Windows, the NO_PROXY hostname list should be separated by semicolons rather than the Linux default of commas.

Acceptance Criteria

• Proxy vars are set on the Windows instances by WICD (the same vars/values present in the global cluster Proxy resource)
• Proxy vars are picked up by Windows services
• If proxy vars change, the values are updated properly on all Windows instances
• Verify traffic is actually passing through the proxy