Say release A had manifest M that lead the CVO to reconcile resource R. But then the component maintainers decided they didn't need R anymore, so they dropped manifest M in release B. The new CVO will no longer reconcile R, but clusters updating from A to B will still have resource R in-cluster, as an unmaintained orphan. Without OTA-222, it was possible to have some non-CVO component remove R, but because of the effort involved, that rarely happened. Once we have OTA-222 implemented, we should go back through and create deletion manifests for these leaked resources. This ticket is tracking that work.

As part of the Jira we are planning to create Jira cards, Bugzilla's  for respective components and teams to work on fixing the issue.