# Catalyst Blueprint umbrella metadata — the upstream chart is now resolved
# as a Helm subchart via Chart.yaml `dependencies:`. This values.yaml carries
# both:
#   1. The catalystBlueprint metadata block (provenance + version) so
#      observability/audit pipelines can inspect the artifact and report
#      which upstream chart + version is bundled.
#   2. The upstream subchart values overlay under the `nats:` key
#      (umbrella-chart convention — the dependency name from Chart.yaml is
#      the values namespace).

catalystBlueprint:
  upstream: { chart: nats, version: "1.2.0", repo: "https://nats-io.github.io/k8s/helm/charts" }

# ─── Upstream chart values (subchart key: nats) ───────────────────────────
# Generated by docs/PROVISIONING-PLAN.md tickets [F] chart Pass 105+.
nats:
  config:
    cluster:
      enabled: true
      replicas: 3
    jetstream:
      enabled: true
      fileStore:
        pvc:
          size: 10Gi
  container:
    resources:
      requests: { cpu: 100m, memory: 256Mi }
      limits: { memory: 1Gi }
  # Prometheus exporter + PodMonitor — DEFAULT OFF.
  #
  # Per docs/INVIOLABLE-PRINCIPLES.md #4 and docs/BLUEPRINT-AUTHORING.md
  # §11.2 (Observability toggles must default false). The upstream nats
  # chart's `promExporter.podMonitor.enabled` renders a
  # monitoring.coreos.com/v1 PodMonitor which the apiserver rejects on a
  # fresh Sovereign before bp-kube-prometheus-stack ships the CRD.
  # Upstream already defaults both to false — set explicitly so a
  # future upstream bump cannot regress this. Operator opts in via
  # per-cluster overlay (issue #182).
  promExporter:
    enabled: false
    podMonitor:
      enabled: false
