Reference secret in manifestwork instead of putting raw data in it.

[qiujian16]

relating to this issue

open-cluster-management-io/work#114

[qiujian16]

/assign @qiujian16

[bhperry]

This would be great. The Policy add-on I think partially solves this problem by supporting encrypted values, and I'm guessing if you bind your ManifestWorkReplicaSet and secret Policy to the same Placement then you would get the desired behavior of secret(s) being created for each ManifestWork that is distributed out to spoke clusters.

It would be nice to have support for this in OCM core though