-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
4.17
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
the documentation is inconsistent of the behaviour when both "[watch] All namespaces" and "install in specific namespace" are used together: in this case the operator is installed in the specified namespace and not into the default "openshift-operators" global namespace as stated in the "All namespaces": https://docs.openshift.com/container-platform/4.17/operators/admin/olm-adding-operators-to-cluster.html#olm-installing-global-namespaces_olm-adding-operators-to-a-cluster
Version-Release number of selected component (if applicable):
4.17
How reproducible:
see https://docs.openshift.com/container-platform/4.17/operators/admin/olm-adding-operators-to-cluster.html#olm-installing-global-namespaces_olm-adding-operators-to-a-cluster
Steps to Reproduce:
1. read documentation
2. be confused, as your workmates
3. try it out in a testcluster to discover the actual behavior
Actual results:
documentation specifies that "all namespaces" means that the operator will be always installed into the "openshift-operators" global namespace.
Expected results:
documentation specifies that the operator will be installed in the user-specified namespace; if none is specified then "openshift-operators" will be used by default
Additional info:
