# Scale the whole chart down without uninstalling it: scaleDown: true renders
# every Deployment/StatefulSet with replicas: 0 (and suspends CronJobs) and
# takes precedence over any per-workload replicas value. PVCs, Secrets and
# Services stay in place; scaleDown: false brings the workloads back up.
scaleDown: false

secrets:
  databaseSecretRef: null
  ziplineSecretRef: null

config:
  storage: 50Gi
  storageClass: longhorn
  # The request-body cap, and it lives entirely in the INGRESS: the chart
  # renders it into nginx.ingress.kubernetes.io/proxy-body-size and
  # nginx.org/client-max-body-size, so it is enforced by the nginx-family
  # controllers and by nothing inside Zipline. In Ingress mode it is the
  # ceiling that actually bites, far below the app's own UPLOADER_ADMIN_LIMIT
  # of 500mb (pinned in the template, not a value).
  #
  # With ingress.enabled: false it does nothing at all, and in GATEWAY MODE
  # (httpRoute.enabled) it is NOT ENFORCED either: the Gateway API has no
  # body-size field, the ceiling becomes the Gateway's, and this chart
  # deliberately renders no implementation-specific policy object to set it
  # (Gitea #114). For an upload service that is the value to check before
  # switching modes; NOTES.txt prints it.
  maxUploadFileSize: 30m

zipline:
  # Replica count for this workload; 0 is allowed and scales it down.
  # The chart-global scaleDown flag takes precedence.
  replicas: 1
  # The upstream image ships no dedicated user, but the Node.js server runs
  # fine as an arbitrary non-root uid; fsGroup makes the uploads PVC writable.
  securityContext:
    pod:
      runAsNonRoot: true
      runAsUser: 1000
      runAsGroup: 1000
      fsGroup: 1000
      fsGroupChangePolicy: Always
      # RuntimeDefault applies the container runtime's default seccomp filter,
      # which blocks the syscalls a normal workload never makes. It sits in the
      # pod context on purpose: from here it covers every container in the pod
      # including init containers, while a container-level seccompProfile would
      # have to be repeated for each one (and silently missed on the next one
      # added). A container that genuinely needs a different filter can still
      # override it under securityContext.container, which wins over this value.
      seccompProfile:
        type: RuntimeDefault
    container:
      allowPrivilegeEscalation: false
      readOnlyRootFilesystem: true
      runAsNonRoot: true
      capabilities:
        drop:
          - ALL
  # Zipline v4 exposes /api/healthcheck (checks server and database health);
  # the endpoint is enabled by default (config.features.healthcheck). Since it
  # includes the database, it is used for readiness/startup only; liveness
  # uses "/" so a database outage does not restart the pod.
  livenessProbe:
    httpGet:
      path: /
      port: zipline-server
    periodSeconds: 10
    timeoutSeconds: 5
    failureThreshold: 3
  readinessProbe:
    httpGet:
      path: /api/healthcheck
      port: zipline-server
    periodSeconds: 10
    timeoutSeconds: 5
    failureThreshold: 3
  # The startup probe gates liveness/readiness. Zipline runs database
  # migrations on startup, so grant a generous budget: 10s * 30 = 300s.
  startupProbe:
    httpGet:
      path: /api/healthcheck
      port: zipline-server
    periodSeconds: 10
    timeoutSeconds: 5
    failureThreshold: 30
  resources:
    # Limits are optional: memory and ephemeral-storage limits default to
    # limitFactor x the request, an explicitly set limit always wins, and a
    # CPU limit is only set when configured explicitly under "limits".
    limitFactor: 3
    requests:
      cpu: 0.1
      memory: 265Mi
      ephemeralStorage: 100Mi
  # Extra environment variables, appended to the ones the chart always sets.
  # Rendered through tpl; value, secretKeyRef and configMapKeyRef forms are
  # supported (see template-chart).
  env: []

ingress:
  # Set to false to omit the Ingress entirely. Note that ingress.domain stays
  # required even then: it is also the app's default domain for generated
  # share links (CORE_DEFAULT_DOMAIN), not just the Ingress host. Only
  # clusterIssuer becomes unnecessary.
  #
  # Mutually exclusive with httpRoute.enabled below (Gitea #114): with both
  # true the render aborts, naming both values.
  enabled: true
  clusterIssuer: null
  # The public hostname of this release. Read by the Ingress, by
  # CORE_DEFAULT_DOMAIN in the StatefulSet (with its own required()), and -
  # when httpRoute.hostnames is empty - by the HTTPRoute. Required in every
  # mode.
  domain: null
  className: nginx
  # Extra annotations for the Ingress; merged with the cert-manager
  # cluster-issuer and upload-size annotations the chart always sets.
  #
  # THESE HAVE NO COUNTERPART IN GATEWAY MODE. The Gateway API has no
  # annotation channel for controller behaviour, so anything configured here is
  # simply gone when httpRoute.enabled is used instead - it is then the
  # Gateway's business, or that of an implementation-specific policy object
  # this chart deliberately does not render. For THIS chart that includes the
  # upload cap: see config.maxUploadFileSize above.
  annotations: {}

# Gateway-API alternative to the Ingress above (Gitea #114). Off by default, so
# an existing release is unaffected; exactly one of ingress.enabled and
# httpRoute.enabled may be true.
#
# The chart renders ONLY an HTTPRoute with parentRefs - no Gateway, no
# gatewayClassName, no Certificate and no implementation-specific policy
# object. Class and certificate belong to the Gateway and therefore to the
# platform, which is what keeps this chart independent of whether the cluster
# runs nginx-gateway-fabric, Cilium, Envoy Gateway or Istio.
#
# WHAT THIS MODE COSTS HERE: config.maxUploadFileSize is not enforced, so the
# upload ceiling is the Gateway's. This is a file-upload service - that is the
# one value to check before switching, and an oversized upload then fails as a
# proxy error rather than as a message from Zipline.
#
# The Gateway-API CRDs must be installed in the cluster: the chart does not and
# cannot detect them (.Capabilities.APIVersions is unreliable at template
# time), so with httpRoute.enabled: true and no CRDs the INSTALL fails.
httpRoute:
  enabled: false
  # The Gateway(s) this route attaches to - a platform object, usually in
  # another namespace, which must allow this namespace in its listener's
  # allowedRoutes. One entry per parent, the fields are the Gateway API's
  # ParentReference (name, and optionally namespace, sectionName, port, group,
  # kind), passed through unchanged:
  #
  #   parentRefs:
  #     - name: public
  #       namespace: gateway
  #       sectionName: https
  #
  # REQUIRED while httpRoute.enabled is true - the render aborts on an empty
  # list, because a route without a parent is created, is valid and routes
  # nothing, with no event to say so.
  parentRefs: []
  # Empty means [ingress.domain], so the hostname has one source of truth. Set
  # explicitly only to publish under a different or an additional name - which
  # is how a migration from the Ingress runs: the HTTPRoute takes a second
  # hostname while the Ingress keeps ingress.domain.
  #
  # For THIS chart, mind that a second hostname does not move
  # CORE_DEFAULT_DOMAIN with it: every share link Zipline hands out keeps
  # naming ingress.domain until that value is changed too.
  hostnames: []