Files
helm-charts/zipline/values.yaml
T
jklein 91a2fbcb05 Compute memory/ephemeral-storage limits from requests, drop default CPU limits
Every chart now renders its container resources through a duplicated
_helpers.tpl helper (reference implementation in template-chart): requests
ship as chart defaults, missing memory and ephemeral-storage limits are
computed as resources.limitFactor x the request (default 3, satisfactory
keeps 2 to preserve its previously published 8Gi limit), an explicitly set
limit always wins, and a CPU limit is only rendered when set explicitly.
Fixed limit defaults are removed from all values.yaml files; teamspeak-server
gains a values-driven resources block instead of hardcoded template values.
Major version bump for all published charts.
2026-08-21 23:34:09 +02:00

61 lines
1.8 KiB
YAML

config:
storage: 50Gi
storageClass: longhorn
secretRef:
db: null
zipline: null
domain: null
maxUploadFileSize: 30m
zipline:
# 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