Description of problem:
Install aws-load-balancer-operator in UPI on AWS cluster and get error:
1.6518190784357512e+09	ERROR	setup	failed to get VPC ID	{"error": "no VPC with tag \"kubernetes.io/cluster/hongli-upi-5jtvq\" found"}


OpenShift release version:
4.11.0-0.nightly-2022-05-05-015322
aws-load-balancer-operator-bundle-container-0.0.1-3


Cluster Platform:
UPI on AWS

How reproducible:
100%

Steps to Reproduce (in detail):
1. Install aws-load-balancer-operator in UPI on AWS cluster
2. $ oc -n aws-load-balancer-operator get pod
NAME                                                             READY   STATUS             RESTARTS      AGE
aws-load-balancer-operator-controller-manager-784477df6d-8mjgr   1/2     CrashLoopBackOff   2 (13s ago)   52s
 

Actual results:
$ oc -n aws-load-balancer-operator logs aws-load-balancer-operator-controller-manager-784477df6d-8mjgr -c manager
I0506 06:37:56.624304       1 request.go:665] Waited for 1.036635711s due to client-side throttling, not priority and fairness, request: GET:https://172.30.0.1:443/apis/apiextensions.k8s.io/v1?timeout=32s
1.6518190783266642e+09	INFO	controller-runtime.metrics	Metrics server is starting to listen	{"addr": "127.0.0.1:8080"}
1.6518190784357512e+09	ERROR	setup	failed to get VPC ID	{"error": "no VPC with tag \"kubernetes.io/cluster/hongli-upi-5jtvq\" found"}
main.main
	/remote-source/workspace/app/main.go:133
runtime.main
	/usr/lib/golang/src/runtime/proc.go:255



Expected results:
aws-load-balancer-operator-controller-manager pod should be running.

Impact of the problem:


Additional info:
workaround: Go to AWS console and manually add the tag to the VPC.


** Please do not disregard the report template; filling the template out as much as possible will allow us to help you. Please consider attaching a must-gather archive (via `oc adm must-gather`). Please review must-gather contents for sensitive information before attaching any must-gathers to a bugzilla report.  You may also mark the bug private if you wish.