Description of problem:
Services deployed by the openshift-data-foundation operator (ODF) in VSphere `noobaa-mgmt` and `s3` services are defined as type "LoadBalancer" and go into a Pending state 

noobaa-mgmt                                        LoadBalancer   172.30.13.121    <pending>     80:30455/TCP,443:32287/TCP,8445:30295/TCP,8446:32453/TCP   114m
s3                                                 LoadBalancer   172.30.254.11    <pending>     80:31212/TCP,443:30711/TCP,8444:30414/TCP,7004:30457/TCP   114m


OpenShift release version:
4.9.12, 4.7.32

RED HAT OPENSHIFT DATA FOUNDATION:
4.9

Cluster Platform:
vSphere, 

How reproducible:
100%

Is there any workaround available to the best of your knowledge?
For a workaround customer modified the service and changed the type to ClusterIP. 

Expected results: 

The service noobaa-mgmt and s3 should be provisioned as type ClusterIP instead of type LoadBalancer. 

Steps to Reproduce (in detail):
Followed documents: 

https://github.com/redhat-cop/gitops-catalog/tree/main/openshift-data-foundation-operator/operator/overlays/stable-4.9