Created attachment 1793640 [details]
Spreadsheet containing leaked resources.
+++ This bug was initially created as a clone of Bug #1975533 +++
This "stale cruft" is created as a result of the following scenario. Release A had manifest M that lead the CVO to reconcile resource R. But then the component maintainers decided they didn't need R any longer, 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.
Now that https://issues.redhat.com/browse/OTA-222 has been implemented teams can go back through and create deletion manifests for these leaked resources.
The attachment delete-candidates.csv contains a list of leaked resources as compared to a freshly installed 4.9 cluster. Use this list to find your component's resources and use the manifest delete annotation (https://github.com/openshift/cluster-version-operator/pull/438) to remove them.
Note also that in the case of a cluster-scoped resource it may not need to be removed but simply be modified to remove namespace.
Seemed the operator-sdk is not among them.
Looking at the list there is no mention of anything operator-sdk related.