OSD-28131: Deploying COO in place of OBO on SC clusters

Author: Nikokolas3270

deploy/olm/syncselector-template.yaml

@@ -50,7 +50,6 @@ objects:
             operator: In
             values:
               - management-cluster
-              - service-cluster
       resourceApplyMode: Sync
       resources:
         - apiVersion: operators.coreos.com/v1alpha1
@@ -94,6 +93,41 @@ objects:
                 requests:
                   cpu: ${RESOURCE_REQUEST_CPU}
                   memory: ${RESOURCE_REQUEST_MEMORY}
+  - apiVersion: hive.openshift.io/v1
+    kind: SelectorSyncSet
+    metadata:
+      name: cluster-observability-operator-hypershift
+    spec:
+      clusterDeploymentSelector:
+        matchLabels:
+          api.openshift.com/managed: 'true'
+        matchExpressions:
+          - key: ext-hypershift.openshift.io/cluster-type
+            operator: In
+            values:
+              - service-cluster
+      resourceApplyMode: Sync
+      resources:
+        - apiVersion: operators.coreos.com/v1alpha1
+          kind: Subscription
+          metadata:
+            labels:
+              operators.coreos.com/cluster-observability-operator.openshift-operators: ""
+            name: cluster-observability-operator
+            namespace: openshift-operators
+          spec:
+            channel: development # This is the only channel available for now - To be replaced with ${CHANNEL} when possible
+            name: cluster-observability-operator
+            source: redhat-operators
+            sourceNamespace: openshift-marketplace
+            config:
+              resources:
+                limits:
+                  cpu: ${RESOURCE_LIMIT_CPU}
+                  memory: ${RESOURCE_LIMIT_MEMORY}
+                requests:
+                  cpu: ${RESOURCE_REQUEST_CPU}
+                  memory: ${RESOURCE_REQUEST_MEMORY}
   - apiVersion: hive.openshift.io/v1
     kind: SelectorSyncSet
     metadata: