manifests: create CMO Service to trigger secret creation

We can then drop the `optional` in the CMO deployment volume spec and
have CMO wait till the requested TLS assets are created.

Signed-off-by: Jan Fajerski <jfajersk@redhat.com>

manifests/0000_50_cluster-monitoring-operator_03-service.yaml

@@ -0,0 +1,20 @@
+apiVersion: v1
+kind: Service
+metadata:
+  annotations:
+    service.beta.openshift.io/serving-cert-secret-name: cluster-monitoring-operator-tls
+    include.release.openshift.io/ibm-cloud-managed: "true"
+    include.release.openshift.io/self-managed-high-availability: "true"
+    include.release.openshift.io/single-node-developer: "true"
+  labels:
+    app: cluster-monitoring-operator
+  name: cluster-monitoring-operator
+  namespace: openshift-monitoring
+spec:
+  clusterIP: None
+  ports:
+  - name: https
+    port: 8443
+    targetPort: https
+  selector:
+    app: cluster-monitoring-operator

manifests/0000_50_cluster-monitoring-operator_05-deployment-ibm-cloud-managed.yaml

@@ -101,5 +101,4 @@ spec:
         name: telemetry-config
       - name: cluster-monitoring-operator-tls
         secret:
-          optional: true
           secretName: cluster-monitoring-operator-tls

manifests/0000_50_cluster-monitoring-operator_05-deployment.yaml

@@ -47,7 +47,6 @@ spec:
       - name: cluster-monitoring-operator-tls
         secret:
           secretName: cluster-monitoring-operator-tls
-          optional: true
       containers:
       - args:
         - --logtostderr