Fix Immich resource limits and probe timeouts

Resources were under wrong Helm value keys (server.resources,
machine-learning.resources) and never applied to pods. Move to correct
bjw-s chart paths (*.controllers.main.containers.main.resources).

Increase liveness/readiness probe timeouts from 1s to 5s to prevent
kubelet from killing healthy-but-busy pods during ML inference load.
Remove CPU limits (keep requests only) to avoid throttling.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Erich Blume 2026-03-27 22:36:32 -07:00
commit b632cd9ffb

View file

@ -37,19 +37,29 @@ immich:
# Machine Learning service # Machine Learning service
machine-learning: machine-learning:
enabled: true enabled: true
controllers:
main:
containers:
main:
resources:
requests:
memory: "512Mi"
cpu: "100m"
limits:
memory: "4Gi"
probes:
liveness:
spec:
timeoutSeconds: 5
readiness:
spec:
timeoutSeconds: 5
persistence: persistence:
cache: cache:
enabled: true enabled: true
type: persistentVolumeClaim type: persistentVolumeClaim
accessMode: ReadWriteOnce accessMode: ReadWriteOnce
size: 10Gi size: 10Gi
resources:
requests:
memory: "512Mi"
cpu: "100m"
limits:
memory: "4Gi"
cpu: "2000m"
# Valkey (Redis fork) - included in chart # Valkey (Redis fork) - included in chart
valkey: valkey:
@ -60,12 +70,22 @@ valkey:
type: emptyDir type: emptyDir
size: 1Gi size: 1Gi
# Server resources for minikube # Server configuration
server: server:
resources: controllers:
requests: main:
memory: "256Mi" containers:
cpu: "100m" main:
limits: resources:
memory: "2Gi" requests:
cpu: "2000m" memory: "256Mi"
cpu: "100m"
limits:
memory: "2Gi"
probes:
liveness:
spec:
timeoutSeconds: 5
readiness:
spec:
timeoutSeconds: 5