# 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 `gitea:` key
#      (umbrella-chart convention — the dependency name from Chart.yaml is
#      the values namespace; the upstream chart's own internal `gitea:`
#      section appears as `gitea.gitea` here, which is correct).

catalystBlueprint:
  upstream: { chart: gitea, version: "10.5.0", repo: "https://dl.gitea.com/charts" }

# ─── Upstream chart values (subchart key: gitea) ──────────────────────────
# Generated by docs/PROVISIONING-PLAN.md tickets [F] chart Pass 105+.
gitea:
  gitea:
    admin:
      username: gitea_admin
      email: gitea-admin@catalyst.local
    config:
      APP_NAME: Catalyst Gitea
      server:
        DOMAIN: gitea.catalyst.local
        ROOT_URL: https://gitea.catalyst.local
    # Gitea built-in metrics + ServiceMonitor — DEFAULT OFF.
    #
    # Per docs/INVIOLABLE-PRINCIPLES.md #4 and
    # docs/BLUEPRINT-AUTHORING.md §11.2 (Observability toggles must
    # default false). The upstream gitea chart's
    # `gitea.gitea.metrics.serviceMonitor.enabled` renders a
    # monitoring.coreos.com/v1 ServiceMonitor which the apiserver rejects
    # on a fresh Sovereign before bp-kube-prometheus-stack ships the CRD.
    # Upstream already defaults to false — set explicitly so a future
    # upstream bump cannot regress this. Operator opts in via per-cluster
    # overlay (issue #182).
    metrics:
      enabled: false
      serviceMonitor:
        enabled: false
  postgresql-ha:
    enabled: false
  postgresql:
    enabled: true
    global:
      postgresql:
        auth:
          username: gitea
          database: gitea
    # PostgreSQL exporter + ServiceMonitor + PrometheusRule — DEFAULT OFF.
    # The bitnami postgresql subchart bundled inside gitea ships a
    # dedicated metrics exporter container that itself renders a
    # ServiceMonitor and PrometheusRule. Same circular-CRD reasoning
    # as above. Operator opts in via per-cluster overlay (issue #182).
    metrics:
      enabled: false
      serviceMonitor:
        enabled: false
      prometheusRule:
        enabled: false
  redis-cluster:
    enabled: false
  valkey-cluster:
    enabled: false
  persistence:
    enabled: true
    size: 20Gi
