When the catalogd and operator-controller pods start, it sometimes happens that the "service-ca" ConfigMap has not yet had its "service-ca.crt" data item populated yet. When this happens, a directory is mounted at /var/trusted-cas/service-ca.crt instead of the expected CA file.

The only way to resolve the problem is to manually delete the pod and let it be re-created AFTER the service-ca.crt data item is populated in the ConfigMap, at which point the file will mount correctly.

Not trivially reproducible because it is a race condition between the controller populating the ConfigMap and the OLMv1 controllers    

    1. 
    2.
    3.
    

When a Proxy CA is configured, catalogd and operator controller may be unable to communicate because they may fail to parse /var/trusted-cas/service-ca.crt (which is sometimes a directory)  

Operator controller and catalogd pods always wait to start until the "service-ca" is populated with "service-ca.crt", thus ensuring the correct mount type for the CA certs.