There's no need to inject the proxy settings into the operator container because it doesn't access any external APIs/endpoints.
Verified pass with 1. Install cluster with proxy: $ oc get proxy cluster -o json | jq .spec { "httpProxy": "http://proxy-user1:JYgU8qRZV4DY4PXJbxJK@10.0.99.4:3128", "httpsProxy": "http://proxy-user1:JYgU8qRZV4DY4PXJbxJK@10.0.99.4:3128", "noProxy": "test.no-proxy.com", "trustedCA": { "name": "" } } 2. Proxy did not inject into snapshot pod $ oc -n openshift-cluster-storage-operator describe pod csi-snapshot-controller-operator-5c4db47864-p2cph | grep -i proxy $ oc -n openshift-cluster-storage-operator describe pod csi-snapshot-controller-757544df4d-wvgrn | grep -i proxy $ 3. Test snapshot test cases passed $ oc get pod,pvc NAME READY STATUS RESTARTS AGE pod/mypod-ori 1/1 Running 0 31m pod/mypod-restore-1 1/1 Running 0 15m NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE persistentvolumeclaim/pvc-ori Bound pvc-8b713809-a971-4c8f-92bf-170a329cc4e5 2Gi RWO managed-csi 31m persistentvolumeclaim/pvc-restore-1 Bound pvc-4a5bd754-d33f-4730-b041-05748ab32e2f 2Gi RWO managed-csi 15m $ oc get volumesnapshot NAME READYTOUSE SOURCEPVC SOURCESNAPSHOTCONTENT RESTORESIZE SNAPSHOTCLASS SNAPSHOTCONTENT CREATIONTIME AGE mysnapshot true pvc-ori 2Gi csi-azuredisk-vsc snapcontent-0356c110-cb65-426f-8283-e447b9e4e7d4 17m 17m Marked it as Verified.
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 (Moderate: OpenShift Container Platform 4.10.3 security update), 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/RHSA-2022:0056