values.ci.yaml

# CI e2e overlay for the canary proof (.github/workflows/canary-e2e.yml).
#
# Layered on top of values.dev.yaml. Same real Rollout + AnalysisTemplate +
# Prometheus success-rate gate as production — only the *timing* is compressed
# so a genuine 25→50→75→100 canary fits a GitHub runner budget. Nothing here
# fakes the gate: the analysis still queries a real Prometheus computing a real
# 2xx success ratio from the workload's http_requests_total counter.

replicaCount: 2

rollout:
  enabled: true
  canary:
    pauseDuration: 10s          # prod 30s
  analysis:
    prometheusAddress: http://prometheus-operated.monitoring.svc:9090
    window: 1m                  # prod 2m rate() window
    interval: 15s               # prod 30s
    count: 2                    # prod 3 → 2 × 15s analysis
    initialDelay: 20s           # prod 30s
    successThreshold: "0.95"    # unchanged — the real gate
    failureLimit: 2

# CI Prometheus scrapes via endpoints service-discovery (ci/prometheus.yaml),
# not the kube-prometheus-stack operator, so the operator ServiceMonitor CRD
# isn't present — disable it to keep helm install clean.
serviceMonitor:
  enabled: false

resources:
  requests:
    cpu: "25m"
    memory: "48Mi"
  limits:
    cpu: "150m"
    memory: "96Mi"