Every time CNV (or kubevirt in general) is upgraded, a new kubevirt-install-strategy config map is being created, which contains a binary, gzipped data of a very not negligible size (>400KB), and it is not cleaned up after subsequent upgrades on the same cluster.
This results in non-relevant resources stacked up on the openshift-cnv namespace without any use, which overloads the etcd for no good reason.

All versions since the very beginning

100%

1. Have CNV installed on the cluster
2. Observe there is a kubevirt-install-strategy config map in the installation namespace (openshift-cnv)
3. Upgrade CNV

Notice a new kubevirt-install-strategy config map was created, and the old one is still there.

the old, obsolete and irrelevant kubevirt-install-strategy CM should be removed automatically.