Description of problem:

There are a number of places where no_proxy lists are being autogenerated to include all nodes/routers/masters during scale-up operations these aren't being updated.

After scaling up our cluster to add 'external' nodes we discovered that we couldn't access the pod logs for pods living on the new nodes.

After digging this was due to the requests being routed via our proxy (which doesn't allow port 10250).

We've manually added the new nodes to the various no_proxy lists on the masters and can now access the logs.

So far I've found the following files which need updating:

Masters:

    /etc/origin/master/master-config.yaml
    /etc/sysconfig/atomic-openshift-master
    /etc/sysconfig/atomic-openshift-master-api
    /etc/sysconfig/atomic-openshift-master-controllers

All Nodes:

    /etc/sysconfig/docker

Version

openshift 3.2


Steps To Reproduce

    stand up cluster including HTTP proxies, where the proxy won't allow port 10250 access
    Expand the cluster using the scaleup playbook
    Attempt to access log files for a pod on the new host

Current Result

Obscure permission denied errors


Expected Result : It should be able to add proxy configurations.