infra/stacks/nextcloud/chart_values.yaml
Viktor Barzin c6beefc845 [ci skip] nextcloud: increase resource limits to prevent OOM crash loop
Default LimitRange (256Mi) was too low — pod was using 227Mi/256Mi and
getting OOM killed under sync client load, causing 500s and blank web UI.
2026-02-28 16:26:19 +00:00

73 lines
1.4 KiB
YAML

nextcloud:
host: nextcloud.viktorbarzin.me
trustedDomains:
- nextcloud.viktorbarzin.me
# mail:
# enabled: true
# # the user we send email as
# fromAddress: nextcloud@viktorbarzin.me
# # the domain we send email from
# domain: viktorbarzin.me
# smtp:
# host: mail.viktorbarzin.me
# secure: starttls
# port: 587
# authtype: LOGIN
# name: nextcloud@viktorbarzin.me
# password:
extraEnv:
- name: TRUSTED_PROXIES
value: "10.0.0.0/8"
# - name: mail_smtpdebug
# value: "true"
# - name: loglevel
# value: "0"
# internalDatabase:
# enabled: false
externalRedis:
enabled: true
host: ${redis_host}
# Currently not in use; we use the nextcloud.db sqlite3
externalDatabase:
enabled: false
type: mysql
host: ${mysql_host}
user: nextcloud
password: ${db_password}
databse: nextcloud
persistence:
enabled: true
existingClaim: nextcloud-data-pvc
accessMode: ReadWriteOnce
size: 100Gi
startupProbe:
enabled: true
initialDelaySeconds: 10
periodSeconds: 10
timeoutSeconds: 5
failureThreshold: 30
successThreshold: 1
podAnnotations:
diun.enable: "true"
diun.include_tags: "^[0-9]+(?:.[0-9]+)?(?:.[0-9]+)?.*"
collabora:
enabled: false # Using onlyoffice instead
resources:
limits:
cpu: "2"
memory: 1Gi
requests:
cpu: 100m
memory: 256Mi
cronjob:
enabled: true