Normal Description of problem:
https://docs.openshift.com/container-platform/4.11/operators/admin/olm-adding-operators-to-cluster.html#olm-installing-global-namespaces_olm-adding-operators-to-a-cluster "Next steps" in the above docs suggest using the OperatorHub web console for Operator installation, however you cannot choose a custom global namespace from the drop-down menu on the Operator installation page. Only the default "operator-operators" ns and any suggested-namespaces the Operator might be configured to use are available.
Version-Release number of selected component (if applicable):
4.11+
How reproducible:
Always
Steps to Reproduce:
1. Create custom global namespace w/ OperatorGroup. 2. Try to install Operator in AllNamespace mode via OperatorHub web console.
Actual results:
Custom global namespace is not available via web console during Operator installation.
Expected results:
Successful AllNamespaces Operator installation using custom global namespace.
Additional info:
Users should be instructed to use the CLI instead of web console for the Operator installation "Next steps".