Operator resource remain after subscription is deleted.

[jackson-chris]

Bug Report

What did you do? Adding a subscription for an operator will cause OLM to create a few resources, namely a Subscription, csv, installplan and Operator resource. When I delete a subscription the corresponding csv and installplan are cleaned up; however the Operator resource remains.

What did you expect to see? I expect that OLM will manage the complete lifecycle of the Operator resource and delete it after any subscriptions related to the Operator are removed.

What did you see instead? Under which circumstances? The Operator resource was not cleaned up.

Environment

• operator-lifecycle-manager version:

4.9.15

• Kubernetes version information:

# kubectl version
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v0.21.0-beta.1", GitCommit:"96e95cef877ba04872b88e4e2597eabb0174d182", GitTreeState:"clean", BuildDate:"2021-12-15T01:45:40Z", GoVersion:"go1.16.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.3+e790d7f", GitCommit:"3a0f2c90b43e6cffd07f57b5b78dd9f083e47ee2", GitTreeState:"clean", BuildDate:"2021-12-14T02:10:38Z", GoVersion:"go1.16.6", Compiler:"gc", Platform:"linux/amd64"}
WARNING: version difference between client (0.21) and server (1.22) exceeds the supported minor version skew of +/-1

• Kubernetes cluster kind:

Possible Solution

Additional context Add any other context about the problem here.