blumeops/argocd/manifests/navidrome/deployment.yaml
Erich Blume b349a415fb Document container build pattern and port navidrome to custom image
Add a how-to guide covering the full container build workflow (Dagger build,
mise release task, Forgejo CI pipeline) and port navidrome from the upstream
deluan/navidrome image to a custom-built image in the zot registry.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-15 07:56:38 -08:00

63 lines
1.5 KiB
YAML

---
apiVersion: apps/v1
kind: Deployment
metadata:
name: navidrome
namespace: navidrome
spec:
replicas: 1
selector:
matchLabels:
app: navidrome
template:
metadata:
labels:
app: navidrome
spec:
containers:
- name: navidrome
image: registry.ops.eblu.me/blumeops/navidrome:v1.0.0
ports:
- containerPort: 4533
name: http
env:
- name: ND_SCANNER_SCHEDULE
value: "@every 1h"
- name: ND_LOGLEVEL
value: "info"
- name: ND_MUSICFOLDER
value: "/music"
- name: ND_DATAFOLDER
value: "/data"
volumeMounts:
- name: music
mountPath: /music
readOnly: true
- name: data
mountPath: /data
resources:
requests:
memory: "128Mi"
cpu: "100m"
limits:
memory: "512Mi"
cpu: "500m"
livenessProbe:
httpGet:
path: /ping
port: 4533
initialDelaySeconds: 10
periodSeconds: 30
readinessProbe:
httpGet:
path: /ping
port: 4533
initialDelaySeconds: 5
periodSeconds: 10
volumes:
- name: music
persistentVolumeClaim:
claimName: navidrome-music
- name: data
persistentVolumeClaim:
claimName: navidrome-data