In CMO we have static yaml assets, that are added to our CMO container image and applied by CMO. We read them once from the file system and after that they are chached in memory.

Currently we use a loose unmarshal, i.e. fields that are spuperflous (not part of the type unmarshaled into) are silently dropped.

We should use strict unmarshaling in order to catch config mistakes like  https://issues.redhat.com//browse/OCPBUGS-24630.

Additionally we could consider adding the static assets to our CMO binary via golangs embed.

Discussed, probably not worth it.