Description of problem:

Usually, Policies are the vehicle for template types like ConfigurationPolicy. But there is nothing preventing a user from installing a ConfigurationPolicy (or another type) directly, without the ownership of a Policy. If this happens, and then a Policy is distributed to that managed cluster that would create the same template, then the framework addon pod crashes on that managed cluster.

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

How reproducible:

Yes

Steps to Reproduce:

1. Create a ConfigurationPolicy directly on a managed cluster
2. Create a Policy wrapping that ConfigurationPolicy and distribute it to that cluster
3. Panic

Actual results:

Panic

Expected results:

No Panic

Additional info: