Motivation

Potential implementation:

• Operator consumes the custom CA as a name of the configmap
• Operator has a flag which expects the name of the config map containing the trusted ca bundle (something like --trusted-ca-bundle-configmap)
• Operator implements a new controller which copies the CA configmap from the operator namespace to operand's (similar to what the existing credentials secret controller does)
• Operator creates a volume and volumeMounts for each operand container to place the CA into the per-defined trusted CA path
• Operator's documentation is updated with instructions of how to create a configmap containing trusted bundles ("config.openshift.io/inject-trusted-cabundle" annotation can be used for OpenShift)