[RFE] Allow Cluster admins to see what is installed as a dependency

[awgreene]

Feature Request

Is your feature request related to a problem? Please describe. OpenShift administrators discover the dependency relationships of installed Operators.

What is the problem: Today cluster administrators are surprised by additional Operators popping up when they install a certain Operator (usually a layered product offering). There is nothing at the API level that makes the relationship obvious.

Why is this important: Without any observable relationship between two Operators an admin might accidentally delete a dependency at a later point. Since OLM does not take into account the health of dependent Operators this would go unnoticed until the dependent Operator is used and fails (maybe even silently) to serve requests, since the dependency is gone.

Describe the solution you'd like

• Operator API surfaces information if an Operator is a dependency of another Operator
• InstallPlan API surfaces information if an Operator has been installed as a result of installing another Operator
• Surfaced information is something that OpenShift console can easily process to visualize dependencies
• Surfaced information is something that OpenShift console can easily process to warn an admin if they are trying to uninstall an actively used dependency
• Dependency information is removed when the last dependent Operator is removed

[jianzhangbjz]

/cc

[stale[bot]]

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contribution. For more help on your issue, check out the olm-dev channel on the kubernetes slack [1] and the OLM Dev Working Group [2] [1] https://kubernetes.slack.com/archives/C0181L6JYQ2 [2] https://github.com/operator-framework/community#operator-lifecycle-manager-wg