From https://github.com/operator-framework/operator-lifecycle-manager/blob/v0.29.0/doc/design/building-your-csv.md

Resources: Your CRDs will own one or more types of Kubernetes objects. These are listed in the resources section to inform your end-users of the objects they might need to troubleshoot or how to connect to the application, such as the Service or Ingress rule that exposes a database.

It’s recommended to only list out the objects that are important to a human, not an exhaustive list of everything you orchestrate. For example, ConfigMaps that store internal state that shouldn’t be modified by a user shouldn’t appear here.

For each CRD owned by COO, we need to detail their owned resources (e.g. at least Prometheus and Alertmanager for MonitoringStack).