From a105387c0ead7a3e5013b50e81d96550ee505cde Mon Sep 17 00:00:00 2001
From: Ruben Hensen <ruben.hensen@protonmail.com>
Date: Sun, 9 Mar 2025 23:30:08 +0100
Subject: [PATCH] Change ingress mqtt

---
 owntracks/recorder.yaml | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/owntracks/recorder.yaml b/owntracks/recorder.yaml
index 312cf4e..46e43fb 100644
--- a/owntracks/recorder.yaml
+++ b/owntracks/recorder.yaml
@@ -234,13 +234,18 @@ spec:
             port:
               number: 8083
 ---
-# External access with Ingress for Mosquitto
+# Corrected MQTT Ingress:
+
 apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
-  name: mosquitto-ingress
+  name: mqtt-ingress
   annotations:
     cert-manager.io/cluster-issuer: prod-cluster-issuer
+    # Add NGINX TCP passthrough annotations
+    nginx.ingress.kubernetes.io/ssl-passthrough: "true"
+    nginx.ingress.kubernetes.io/backend-protocol: "TCP"
+    nginx.ingress.kubernetes.io/ssl-redirect: "false"
 spec:
   ingressClassName: nginx
   tls:
@@ -255,6 +260,11 @@ spec:
         pathType: Prefix
         backend:
           service:
-            name: mosquitto
+            name: mqtt
             port:
-              number: 8883
+              number: 1883
+
+# Note: For proper MQTT over TLS, consider these alternatives:
+# 1. Use a TCP Load Balancer instead of an Ingress
+# 2. Configure the MQTT broker to use TLS directly (port 8883)
+# 3. Use NGINX TCP ingress controller configuration
\ No newline at end of file