-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
Logging 5.9.0
-
False
-
None
-
False
-
NEW
-
OBSDA-747 - [MCOA] Deliver CLO via ACM
-
NEW
-
Release Note Not Required
-
-
Description of problem:
Start from logging 5.8, the default deployment mode of CLO is all namespaces, however, on spoke cluster, the CLO is deployed in single namespace mode:
$ oc get og openshift-logging -oyaml apiVersion: operators.coreos.com/v1 kind: OperatorGroup metadata: annotations: olm.providedAPIs: ClusterLogForwarder.v1.logging.openshift.io,ClusterLogging.v1.logging.openshift.io,LogFileMetricExporter.v1alpha1.logging.openshift.io creationTimestamp: "2023-12-27T02:36:54Z" generation: 2 labels: app: loggingomcaddon chart: loggingomcaddon-1.0.0 og_label: openshift-logging release: logging-ocm-addon name: openshift-logging namespace: openshift-logging ownerReferences: - apiVersion: work.open-cluster-management.io/v1 kind: AppliedManifestWork name: fdddf556de92274141a74d046a41c4a841a02de8fdeceeeecea63bb5a36b3db5-addon-logging-ocm-addon-deploy-0 uid: ded0a175-3df5-4f5d-96ce-0e663de1caad resourceVersion: "88152" uid: e145be50-4b0c-46c9-bc0e-c03786c2ed39 spec: targetNamespaces: - openshift-logging upgradeStrategy: Default status: lastUpdated: "2023-12-27T05:28:31Z" namespaces: - openshift-logging
Version-Release number of selected component (if applicable):
logging-ocm-addon: quay.io/openshift-logging/logging-ocm-addon:0.0.1
How reproducible:
Always
Steps to Reproduce:
- Launch 2 OCP clusters on AWS, one is hub cluster, one is spoke cluster. Install ACM operator on hub cluster, then import spoke cluster.
- Install logging-ocm-addon follow the steps in https://github.com/ViaQ/logging-ocm-addon/blob/main/demo/README.md
- Check CLO on spoke cluster
Actual results:
CLO is deployed in singleNamespace mode on spoke cluster.
Expected results:
CLO should be deployed in allNamespace mode on spoke cluster.