Files
fog/immich/values.yaml.gotmpl
T
2026-10-23 17:23:29 -06:00

85 lines
2.4 KiB
Go Template

controllers:
main:
containers:
main:
image:
tag: v3.3.5
env:
DB_HOSTNAME: {{ exec "kubectl" (list "-n" "immich" "get" "secrets" "postgres-pguser-immich" "-ogo-template='{{.data.host | base64decode }}'") }}
DB_USERNAME: {{ exec "kubectl" (list "-n" "immich" "get" "secrets" "postgres-pguser-immich" "-ogo-template='{{.data.user | base64decode }}'") }}
DB_DATABASE_NAME: {{ exec "kubectl" (list "-n" "immich" "get" "secrets" "postgres-pguser-immich" "-ogo-template='{{.data.dbname | base64decode }}'") }}
DB_PASSWORD: {{ exec "kubectl" (list "-n" "immich" "get" "secrets" "postgres-pguser-immich" "-ogo-template='{{.data.password | base64decode }}'") }}
DB_VECTOR_EXTENSION: pgvector
immich:
persistence:
library:
existingClaim: immich-data
# NOTE: immich 0.12.0 embeds valkey as a bjw-s "common" library template
# (templates/valkey.yaml), not as a Bitnami subchart. The old `valkey.master.*`
# block was silently dropped: it set a 32Mi limit under a 64Mi request (an
# impossible pair that would have OOMKilled the container) and never reached the
# pod. The correct path is controllers.main.containers.main.*.
valkey:
enabled: true
persistence:
data:
annotations:
k8up.io/backup: 'false'
controllers:
main:
containers:
main:
resources:
requests:
cpu: 10m
memory: 48Mi
limits:
memory: 256Mi
server:
enabled: true
controllers:
main:
strategy: Recreate
containers:
main:
resources:
requests:
cpu: 10m
memory: 256Mi
limits:
# No CPU limit: limits do not change scheduler bin-packing and
# only cause CFS throttling. Memory limit is what protects the node.
memory: 1Gi
ingress:
main:
enabled: true
tls:
- secretName: photos-incngrnt-ca-tls
hosts:
- photos.incngrnt.ca
hosts:
- host: photos.incngrnt.ca
paths:
- path: "/"
service:
identifier: main
machine-learning:
enabled: true
controllers:
main:
containers:
main:
resources:
requests:
cpu: 10m
memory: 128Mi
limits:
memory: 2Gi