Initially, it seemed like a good idea for the operator policy to report about all of the relevant InstallPlans of an operator: these resources are left on the cluster deliberately by OLM to provide some sense of a version history. However, this leads to two problems:

1. There is not a clear compliance value to be assigned to previous InstallPlans, which can be confusing to users.
2. The labels and references on InstallPlans to determine what Subscription it is for are not consistent (see OLM issue 3199) meaning the objects that OperatorPolicy can find and record may be inconsistent, incomplete, or irrelevant.

Recording only the current InstallPlan (found via a label that seems to be consistently applied and updated by OLM) will be more reliable, and allows the object to be reported as either Compliant or NonCompliant.