That makes sense. Thank you!
Verified this bug with 4.3.0-0.nightly-2019-12-18-224446, and PASS. Trigger an install on aws behind proxy, succeed. # oc get dnsrecords.ingress.operator.openshift.io -o yaml -n openshift-ingress-operator apiVersion: v1 items: - apiVersion: ingress.operator.openshift.io/v1 kind: DNSRecord metadata: creationTimestamp: "2019-12-19T09:26:22Z" finalizers: - operator.openshift.io/ingress-dns generation: 1 labels: ingresscontroller.operator.openshift.io/owning-ingresscontroller: default name: default-wildcard namespace: openshift-ingress-operator ownerReferences: - apiVersion: operator.openshift.io/v1 blockOwnerDeletion: true controller: true kind: IngressController name: default uid: 3e74d28c-6ef9-402b-98d5-75af69215e87 resourceVersion: "9101" selfLink: /apis/ingress.operator.openshift.io/v1/namespaces/openshift-ingress-operator/dnsrecords/default-wildcard uid: 29b1ffa7-5744-4f2a-88e8-fddb5ed3060d spec: dnsName: '*.apps.jialiu43awsbz1.qe.devcluster.openshift.com.' recordTTL: 30 recordType: CNAME targets: - a7ab1d9ee07674b44b4b9210c23dca47-36094194.us-east-2.elb.amazonaws.com status: zones: - dnsZone: tags: Name: jialiu43awsbz1-8ll74-int kubernetes.io/cluster/jialiu43awsbz1-8ll74: owned - dnsZone: id: Z3B3KOVA3TRCWP kind: List metadata: resourceVersion: "" selfLink: "" # oc -n openshift-ingress-operator exec ingress-operator-744b944985-brh4l -- env | grep -i proxy Defaulting container name to ingress-operator. Use 'oc describe pod/ingress-operator-744b944985-brh4l -n openshift-ingress-operator' to see all of the containers in this pod. HTTP_PROXY=http://ec2-18-222-23-12.us-east-2.compute.amazonaws.com:3128 HTTPS_PROXY=http://ec2-18-222-23-12.us-east-2.compute.amazonaws.com:3128 NO_PROXY=.cluster.local,.svc,.us-east-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.jialiu43awsbz1.qe.devcluster.openshift.com,etcd-0.jialiu43awsbz1.qe.devcluster.openshift.com,etcd-1.jialiu43awsbz1.qe.devcluster.openshift.com,etcd-2.jialiu43awsbz1.qe.devcluster.openshift.com,localhost,test.no-proxy.com
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