# T-read recall gate (read-only variant) — recall@10 + read p99 against an
# EXISTING corpus, no quorum writes.
#
# --skip-seed: the 100k/1536-dim corpus is already resident (deterministic
# bases), so the harness regenerates the same bases locally to build the
# brute-force oracle and queries the existing corpus — WITHOUT re-registering it.
# Used when the cluster's write/quorum path is unavailable (the 1536-dim seed
# write-burst trips the leader's partition detector) but reads are healthy on a
# replica. Targets tidaldb-1 (a healthy follower holding the full corpus).
apiVersion: batch/v1
kind: Job
metadata:
  name: tidal-recall-skipseed
  namespace: tidaldb-cluster
  labels:
    app.kubernetes.io/name: tidal-stress
    app.kubernetes.io/part-of: tidaldb
spec:
  backoffLimit: 0
  ttlSecondsAfterFinished: 7200
  template:
    metadata:
      labels:
        app.kubernetes.io/name: tidal-stress
        app.kubernetes.io/part-of: tidaldb
    spec:
      restartPolicy: Never
      automountServiceAccountToken: false
      securityContext:
        runAsNonRoot: true
        runAsUser: 1000
        runAsGroup: 1000
        seccompProfile:
          type: RuntimeDefault
      containers:
        - name: stress
          image: registry.threesix.ai/tidal/stress@sha256:4b21c1b89790f7a995f4d9e754fe0faf530079d7ad67a5ad74c15377dcc18ac2
          imagePullPolicy: IfNotPresent
          args:
            - --target
            - https://tidaldb-2.tidaldb-peers.tidaldb-cluster.svc.cluster.local:9500
            - --ca-cert
            - /etc/tidaldb/tls/ca.crt
            - --verify-recall
            - --skip-seed
            - --corpus
            - "100000"
            - --embedding-dim
            - "1536"
            - --recall-k
            - "10"
            - --recall-queries
            - "1000"
            - --read-p99-target-ms
            - "10"
            - --recall-target
            - "0.95"
            - --recall-ef-search
            - "64"
            - --ramp
            - "200:30,500:30,1000:30,2000:30"
          env:
            - name: TIDAL_API_KEY
              valueFrom:
                secretKeyRef:
                  name: tidaldb-credentials
                  key: TIDAL_API_KEY
            - name: TIDAL_STRESS_LOG
              value: warn
          resources:
            requests:
              cpu: 500m
              memory: 512Mi
            limits:
              cpu: "3"
              memory: 2Gi
          securityContext:
            allowPrivilegeEscalation: false
            readOnlyRootFilesystem: true
            capabilities:
              drop: ["ALL"]
          volumeMounts:
            - name: cluster-tls
              mountPath: /etc/tidaldb/tls
              readOnly: true
      volumes:
        - name: cluster-tls
          secret:
            secretName: tidaldb-cluster-tls
            items:
              - key: ca.crt
                path: ca.crt