Description of problem:

I have been trying to get a certificate from a secret on the hub into a config map on managed clusters.  While I found a way to make this work, it does not work in many scenarios that I expected should work.

This requires a hub and separate managed cluster to recreate.  There are 3 main scenarios I am demonstrating.

1. policy-configmap.yaml - read a CA cert from a hub configmap. This leads to bad formatting
2. policy-cm-oneline.yaml - reading the CA cert from a hub secret.  The template function is on the same line as the configmap key and results in bad formatting.
3. policy-secret2configmap.yaml - reading the CA cert from a hub secret copied to the managed cluster and then copied into the configmap.  The configmap copy is a one liner. Shows error `illegal base64 data at input byte 0` in the ConfigMap instead of the correct value.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

1. Use the generator project I provided in the attachment that contains the policy files referenced

Actual results:

Expected results:

Better handling of certificates

Additional info: