different config owntracks

This commit is contained in:
Ruben Hensen
2025-03-10 08:37:42 +01:00
parent 976b6cbde5
commit c09aff0d7e
+17 -10
View File
@@ -87,11 +87,17 @@ spec:
- containerPort: 8083 - containerPort: 8083
env: env:
- name: OTR_HOST - name: OTR_HOST
value: "mqtt" value: "mqtt.hensen.io"
- name: OTR_PORT - name: OTR_PORT
value: "1883" value: "8083"
- name: OTR_USER - name: OTR_USER
value: "ruben" value: "ruben"
- name: TZ
value: "Europe/Berlin"
# - name: VIRTUAL_HOST
# value: "owntracks.hensen.io"
# - name: VIRTUAL_PORT
# value: 8883
# - name: OTR_CLIENTID # - name: OTR_CLIENTID
# value: "" # value: ""
- name: OTR_PASS - name: OTR_PASS
@@ -147,10 +153,11 @@ metadata:
name: mqtt-config name: mqtt-config
data: data:
mosquitto.conf: | mosquitto.conf: |
listener 1883 listener 8883
allow_anonymous false allow_anonymous false
password_file /mosquitto/config/password_file password_file /mosquitto/config/password_file
# Add other MQTT configuration options here # Add other MQTT configuration options here
listener 8083
protocol websockets protocol websockets
--- ---
# MQTT Deployment # MQTT Deployment
@@ -174,9 +181,9 @@ spec:
- name: mqtt - name: mqtt
image: eclipse-mosquitto:latest image: eclipse-mosquitto:latest
ports: ports:
- containerPort: 1883 - containerPort: 8883
name: mqtt name: mqtt
- containerPort: 9001 - containerPort: 8083
name: websocket name: websocket
volumeMounts: volumeMounts:
- name: config - name: config
@@ -203,11 +210,11 @@ spec:
selector: selector:
app: mqtt app: mqtt
ports: ports:
- port: 1883 - port: 8883
targetPort: 1883 targetPort: 8883
name: mqtt name: mqtt
- port: 9001 - port: 8083
targetPort: 9001 targetPort: 8083
name: websocket name: websocket
--- ---
# External access with Ingress for OwnTracks Recorder # External access with Ingress for OwnTracks Recorder
@@ -264,7 +271,7 @@ spec:
service: service:
name: mqtt name: mqtt
port: port:
number: 1883 number: 8083
# Note: For proper MQTT over TLS, consider these alternatives: # Note: For proper MQTT over TLS, consider these alternatives:
# 1. Use a TCP Load Balancer instead of an Ingress # 1. Use a TCP Load Balancer instead of an Ingress