Created attachment 1796798 [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.
Spreadsheet entry is:
HelmChartRepository redhat-helm-repo from 0000_50_console-operator_01-helm.yaml
We need to tackle this with care we still want HelmChartRepository redhat-helm-repo cause it has charts that has not been migrated to HelmChartRepository openshift-helm-charts. Once all the charts have been migrated with owner we can remove redhat-helm-repo
To be specific, there are currently 4 charts under https://github.com/redhat-developer/redhat-helm-charts/tree/master/charts that haven't migrated yet:
Quick update on this: charts referenced by Allen above has not yet been migrated, will work on this once IBM send those to the new repo https://github.com/openshift-helm-charts/charts
have been migrated