Let's say your ArgoCD pods contain proxy environment variables, perhaps something like this.

~]$ oc get pod openshift-gitops-server-7744cbb479-7w8xd --output yaml
spec:
  containers:
    env:
    - name: HTTPS_PROXY
      value: https://proxy.example.com
    - name: HTTP_PROXY
      value: http://proxy.example.com
    - name: NO_PROXY
      value: .cluster.local,.example.com,access.redhat.com,localhost,quay.io,registry.connect.redhat.com,registry.redhat.io

Likewise your ArgoCD deployment may also contain proxy environment variables.

~]$ oc get deployment openshift-gitops-server --output yaml
spec:
  containers:
    env:
    - name: HTTPS_PROXY
      value: https://proxy.example.com
    - name: HTTP_PROXY
      value: http://proxy.example.com
    - name: NO_PROXY
      value: .cluster.local,.example.com,access.redhat.com,localhost,quay.io,registry.connect.redhat.com,registry.redhat.io

And if you try to remove the proxy environment variables from the deployment the proxy environment variable may immediately be re-added to the deployment. This probably means that your Kubernetes or OpenShift cluster has a proxy resource. The kubectl (Kubernetes) or oc (OpenShfit) get proxy command can be used to determine if the cluster has a proxy resource. In this example, there is a proxy resource named "cluster".

~]$ oc get proxy
NAME      AGE
cluster   622d

And the proxy resource should contain the same proxy environment variables as listed in the ArgoCD pods and deployments.

~]$ oc get proxy cluster --output yaml
spec:
  httpProxy: http://proxy.example.com
  httpsProxy: https://proxy.example.com
  noProxy: .cluster.local,.example.com,access.redhat.com,localhost,quay.io,registry.connect.redhat.com,registry.redhat.io