Bug 1975544 - [Operator SDK] Remove stale cruft installed by CVO in earlier releases
Summary: [Operator SDK] Remove stale cruft installed by CVO in earlier releases
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Operator SDK
Version: 4.9
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Jesus M. Rodriguez
QA Contact: Fan Jia
Depends On:
TreeView+ depends on / blocked
Reported: 2021-06-23 21:39 UTC by Jack Ottofaro
Modified: 2022-02-17 00:28 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1975533
Last Closed: 2022-02-17 00:28:17 UTC
Target Upstream Version:

Attachments (Terms of Use)
Spreadsheet containing leaked resources. (11.48 KB, text/plain)
2021-06-23 21:39 UTC, Jack Ottofaro
no flags Details

Description Jack Ottofaro 2021-06-23 21:39:52 UTC
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.

Comment 2 Fan Jia 2021-10-27 03:04:35 UTC
Seemed the operator-sdk is not among them.

Comment 3 Jesus M. Rodriguez 2022-02-17 00:28:17 UTC
Looking at the list there is no mention of anything operator-sdk related.

Note You need to log in before you can comment on or make changes to this bug.