In 4.4, OpenShift console added support for two ClusterServiceVersion annotations: * operatorframework.io/suggested-namespace - console will suggest and create the suggested namespace for the operator * operatorframework.io/cluster-monitoring=true - console will ask the user if they want to enable monitoring the operator and apply the label to the created namespace Operators that require a specific namespace and need to enable monitoring should add these annotations to give the UI hints. This will avoid extra steps requiring users to create and label the namespace outside of the UI. More details in this enhancement: https://github.com/openshift/enhancements/blob/master/enhancements/olm/olm-managed-operator-metrics.md#fulfilling-namespace-and-rbac-requirements Here is the console PR: https://github.com/openshift/console/pull/3862
The suggested namespace annotation and cluster monitoring annotation documentation can be found here [1]. [1] https://docs.google.com/document/d/1Mru7pqkpx2gmxMxK6AYOLVphWW0mzwZG-R8_HBVxLwI/edit
Verified. anli@preserve-docker-slave 81366]$ oc get csv elasticsearch-operator.4.4.0-202002142031 -o json |jq '.metadata.annotations."olm.operatorNamespace"' "openshift-operators-redhat" [anli@preserve-docker-slave 81366]$ oc get csv clusterlogging.4.4.0-202002170216 -o json |jq '.metadata.annotations."olm.operatorNamespace"' "openshift-logging"
#oc get csv clusterlogging.4.4.0-202002170216 -o json |jq '.metadata.annotations."operatorframework.io/suggested-namespace"' "openshift-logging" #oc get csv elasticsearch-operator.4.4.0-202002142031 -o json |jq '.metadata.annotations."operatorframework.io/suggested-namespace"' "openshift-operators-redhat"
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0581