The following operators need to be checked to see if they use GCP API and make them adopt this change:

1. operators installed out of the box (OSD-GCP)

• Managed OpenShift Addon Operator
• cloud-ingress-operator
• configure-alertmanager-operator
• custom-domains-operator
• Deployment Validation Operator
• managed-node-metadata-operator
• managed-upgrade-operator
• managed-velero-operator
• must-gather-operator
• Observability Operator
• ocm-agent-operator
• osd-metrics-exporter
• Package Server
• rbac-permissions-operator
• Route Monitor Operator
• splunk-forwarder-operator

1. day-2/optional operators and layered products that are critical and currently used by our customers. Ideally, all the day-2 operators and layered products that are currently compatible with OSD-GCP should leverage GCP WIF. If that's a heavy lift, we would like to prioritize the following. This includes the operators currently installed on the UPS clusters (source: TeleSense usage for UPS account)

• addon-operator
• amqstreams
• cluster-logging
• clusterkubedescheduleroperator
• db2u-operator
• dynatrace-operator
• ibm-licensing-operator
• loki-operator
• openshift-pipelines-operator-rh
• cloud-credential-operator        
• cloud-network-config-controller  
• openshift-cloud-controller-manager    
• cluster-image-registry-operator  
• cluster-ingress-operator        
• machine-api-operator 
• gcp-pd-csi-driver-operator  
• GCP Filestore CSI driver operator 
• OADP