-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
1.3.0
-
None
-
None
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Install COO, under any namespaces, operator.operators.coreos.com is created
% oc -n coo get operator.operators.coreos.com NAME AGE cluster-observability-operator.openshift-cluster-observability 6m28s
According to olm formal doc, the resource created with package name cluster-observability-operator.
OLM will then the update the operator’s status.Components.Refs array to include all resources associated with the operator. Let’s consider OLM’s behavior after creating the operator CR named cluster-observability-operator:
- All resources associated with the cluster-observability-operator{{ operator}} CR will have the operators.coreos.com/cluster-observability-operator label applied to it. From the following we can see, all the CRs have no related labels
% oc get uiplugins.observability.openshift.io --show-labels
NAME AGE LABELS
distributed-tracing 12s <none>
logging 13s <none>
monitoring 67m <none>
troubleshooting-panel 67m <none>
% oc get monitoringstacks.monitoring.rhobs -A --show-labels
NAMESPACE NAME AGE LABELS
e2e-tests multi-ns 24m mso=example
% oc get prometheuses.monitoring.rhobs -A --show-labels
NAMESPACE NAME VERSION DESIRED READY RECONCILED AVAILABLE AGE LABELS
e2e-tests multi-ns 2 2 True True 25m app.kubernetes.io/managed-by=observability-operator,app.kubernetes.io/name=multi-ns,app.kubernetes.io/part-of=multi-ns