Add probes and rollout strategy to component-monitor deployment (openshift#79354)

Wire up startup, readiness, and liveness probes against the new /health
endpoint. Add RollingUpdate strategy with maxUnavailable 0 and
minReadySeconds 60 so the old pod keeps running until the new one is
confirmed ready, preventing monitoring gaps during rollouts.

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

Author: 2 people

clusters/app.ci/ship-status-dash/component-monitor/deployment.yaml

@@ -12,6 +12,12 @@ metadata:
     keel.sh/pollSchedule: "@every 5m"
 spec:
   replicas: 1
+  strategy:
+    type: RollingUpdate
+    rollingUpdate:
+      maxUnavailable: 0
+      maxSurge: 1
+  minReadySeconds: 60
   selector:
     matchLabels:
       app: component-monitor
@@ -63,6 +69,27 @@ spec:
           - "--dashboard-url=https://protected.ship-status.ci.openshift.org"
           - "--kubeconfig-dir=/etc/kubeconfig"
           - "--report-auth-token-file=/etc/kubeconfig/sa.component-monitor.app.ci.token.txt"
+        startupProbe:
+          httpGet:
+            path: /health
+            port: 8080
+          initialDelaySeconds: 10
+          periodSeconds: 5
+          failureThreshold: 24
+        readinessProbe:
+          httpGet:
+            path: /health
+            port: 8080
+          initialDelaySeconds: 5
+          periodSeconds: 10
+          failureThreshold: 3
+        livenessProbe:
+          httpGet:
+            path: /health
+            port: 8080
+          initialDelaySeconds: 30
+          periodSeconds: 15
+          failureThreshold: 5
         volumeMounts:
           - name: release
             mountPath: /var/repo