From 9bb6865b5ceb301fa0f70aa6b9caa3b3adbfd31d Mon Sep 17 00:00:00 2001
From: Tyler Perkins <tyler@clortox.com>
Date: Sun, 26 May 2024 17:22:22 -0400
Subject: [PATCH] Add navidrome ingress

---
 navidrome/navidrome-ingress.yaml | 25 +++++++++++++++++++++++++
 navidrome/navidrome-service.yaml |  2 +-
 2 files changed, 26 insertions(+), 1 deletion(-)
 create mode 100644 navidrome/navidrome-ingress.yaml

diff --git a/navidrome/navidrome-ingress.yaml b/navidrome/navidrome-ingress.yaml
new file mode 100644
index 0000000..cdc0fb5
--- /dev/null
+++ b/navidrome/navidrome-ingress.yaml
@@ -0,0 +1,25 @@
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+  name: navidrome-ingress
+  namespace: navidrome-ns
+  annotations:
+    kubernetes.io/ingress.class: "nginx"
+    cert-manager.io/cluster-issuer: "letsencrypt-prod"
+spec:
+  tls:
+  - hosts:
+    - music.clortox.com
+    secretName: music-clortox-com-tls
+  rules:
+  - host: music.clortox.com
+    http:
+      paths:
+      - path: /
+        pathType: Prefix
+        backend:
+          service:
+            name: navidrome
+            port:
+              number: 80  # Ensure this is the correct port your Navidrome service listens on
+
diff --git a/navidrome/navidrome-service.yaml b/navidrome/navidrome-service.yaml
index 2f7f829..b90edef 100644
--- a/navidrome/navidrome-service.yaml
+++ b/navidrome/navidrome-service.yaml
@@ -4,7 +4,7 @@ metadata:
   name: navidrome-services
   namespace: navidrome-ns
 spec:
-  type: LoadBalancer
+  type: ClusterIP
   ports:
   - port: 80
     targetPort: 4533