This is a clone of issue OCPBUGS-38059. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-36932. The following is the description of the original issue:
—
Description of problem:

Customer defines proxy in its HostedCluster resource definition. The variables are propagated to some pods but not to oauth one:

 oc describe pod kube-apiserver-5f5dbf78dc-8gfgs | grep PROX
      HTTP_PROXY:   http://ocpproxy.corp.example.com:8080
      HTTPS_PROXY:  http://ocpproxy.corp.example.com:8080
      NO_PROXY:     .....
oc describe pod oauth-openshift-6d7b7c79f8-2cf99| grep PROX
      HTTP_PROXY:   socks5://127.0.0.1:8090
      HTTPS_PROXY:  socks5://127.0.0.1:8090
      ALL_PROXY:    socks5://127.0.0.1:8090
      NO_PROXY:     kube-apiserver

apiVersion: hypershift.openshift.io/v1beta1
kind: HostedCluster

...

spec:
  autoscaling: {}
  clusterID: 9c8db607-b291-4a72-acc7-435ec23a72ea
  configuration:

   .....
    proxy:
      httpProxy: http://ocpproxy.corp.example.com:8080
      httpsProxy: http://ocpproxy.corp.example.com:8080

Version-Release number of selected component (if applicable): 4.14