Files
helm-charts/zipline/values.yaml
T
jklein 48cb5c01de Zipline chart: ingress standard, secret ref structure (conventions batch 3)
Repo-standard flexible ingress (required clusterIssuer instead of the
hardcoded letsencrypt-issuer, domain moved from config.domain to
ingress.domain, className value, annotations merge, standard TLS secret
name), secrets.<name>SecretRef structure, core secret renamed to the
standard -secret name, additive tpl-rendered env block, documented PVC
naming exception. Major bump 4.1.2+up4.7.0 -> 5.0.0+up4.7.0.
2026-08-22 19:01:04 +02:00

84 lines
2.6 KiB
YAML

# 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
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
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:
clusterIssuer: null
domain: null
className: nginx
# Extra annotations for the Ingress; merged with the cert-manager
# cluster-issuer and upload-size annotations the chart always sets.
annotations: {}