Description of problem: Based on feedback from @deads2k, it's preferred to not automatically add cluster external endpoints (i.e. routes) to the default noProxy list. By doing so, we provide users the ability to choose whether or not to proxy these connections. Version-Release number of selected component (if applicable): 4.3.0-0.okd-2019-10-02-19155 How reproducible: Always Steps to Reproduce: 1. Create a cluster with proxy enabled 2. Check the status.noProxy and you will see the api-server external url: Actual results: $ oc get proxy/cluster -o yaml | grep status -A 2 status: httpProxy: http://ewolinet:5f6ccbbbafc66013d012839921ada773@35.196.128.173:3128 noProxy: .cluster.local,.svc,.us-west-2.compute.internal,10.0.0.0/16,10.128.0.0/14,127.0.0.1,169.254.169.254,172.30.0.0/16,api-int.proxy.devcluster.openshift.com,api.proxy.devcluster.openshift.com,etcd-0.proxy.devcluster.openshift.com,etcd-1.proxy.devcluster.openshift.com,etcd-2.proxy.devcluster.openshift.com,localhost Expected results: $ oc get proxy/cluster -o yaml | grep status -A 2 status: httpProxy: http://ewolinet:5f6ccbbbafc66013d012839921ada773@35.196.128.173:3128 noProxy: .cluster.local,.svc,.us-west-2.compute.internal,10.0.0.0/16,10.128.0.0/14,127.0.0.1,169.254.169.254,172.30.0.0/16,api-int.proxy.devcluster.openshift.com,etcd-0.proxy.devcluster.openshift.com,etcd-1.proxy.devcluster.openshift.com,etcd-2.proxy.devcluster.openshift.com,localhost Additional info:
Per deads2k recommendations, cluster external endpoints will not automatically be added to noProxy. This will provide users choice.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0062