_Music Assistant_ is pretty straightforward to deploy, despite upstream's apparent opinion otherwise. It just needs a small persistent volume for its media index and customization. It does need to use the host network namespace, though, in order to receive multicast announcements from e.g. AirPlay players, as it doesn't have any way of statically configuring them.
21 lines
436 B
YAML
21 lines
436 B
YAML
apiVersion: networking.k8s.io/v1
|
|
kind: Ingress
|
|
metadata:
|
|
name: music-assistant
|
|
labels:
|
|
app.kubernetes.io/name: music-assistant
|
|
app.kubernetes.io/component: music-assistant
|
|
spec:
|
|
ingressClassName: nginx
|
|
rules:
|
|
- host: music.pyrocufflink.blue
|
|
http:
|
|
paths:
|
|
- path: /
|
|
pathType: Prefix
|
|
backend:
|
|
service:
|
|
name: music-assistant
|
|
port:
|
|
name: http
|