- argocd/manifests/immich-ringtail/: full port of the immich stack
(server, ML, valkey, services, ingress, pvc-ml-cache) from
argocd/manifests/immich/, with ringtail-specific tweaks:
- deployment-ml: runtimeClassName=nvidia, nvidia.com/gpu:1 limit,
-cuda image tag
- deployment-valkey + kustomization: drop the
registry.ops.eblu.me/blumeops/valkey mirror (arm64-only), use
upstream docker.io/valkey/valkey:8.1.6 (multi-arch)
- ingress-tailscale: tls.hosts=[photos-ringtail] for staging
- argocd/apps/immich-ringtail.yaml: new ArgoCD app (manual sync,
ringtail destination)
- argocd/manifests/nvidia-device-plugin/time-slicing-config.yaml:
bump replicas 2 -> 4 so the ringtail GPU can be shared by
frigate + ollama + immich-ml
The immich-db Secret in the immich namespace is created manually
(matching minikube pattern) — see argocd/apps/immich-ringtail.yaml
header for the procedure.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
28 lines
754 B
YAML
28 lines
754 B
YAML
apiVersion: kustomize.config.k8s.io/v1beta1
|
|
kind: Kustomization
|
|
|
|
namespace: immich
|
|
|
|
resources:
|
|
- deployment-server.yaml
|
|
- deployment-ml.yaml
|
|
- deployment-valkey.yaml
|
|
- service.yaml
|
|
- service-ml.yaml
|
|
- service-valkey.yaml
|
|
- pvc-ml-cache.yaml
|
|
- pv-nfs.yaml
|
|
- pvc.yaml
|
|
- ingress-tailscale.yaml
|
|
|
|
images:
|
|
- name: ghcr.io/immich-app/immich-server
|
|
newTag: v2.6.3
|
|
- name: ghcr.io/immich-app/immich-machine-learning
|
|
# CUDA variant of the same release — ringtail has an RTX 4080
|
|
newTag: v2.6.3-cuda
|
|
# Using upstream multi-arch valkey image directly; the
|
|
# registry.ops.eblu.me/blumeops/valkey mirror is arm64-only (built
|
|
# on indri) and would crashloop on ringtail.
|
|
- name: docker.io/valkey/valkey
|
|
newTag: "8.1.6"
|