Using the right port for the network watcher

Author: rennokki

charts/soketi/Chart.yaml

@@ -15,9 +15,9 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 1.0.1
+version: 1.0.2
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
 # follow Semantic Versioning. They should reflect the version the application is using.
-appVersion: 1.3.0
+appVersion: 1.4.0

charts/soketi/README.md

@@ -25,7 +25,7 @@ Install the soketi chart:
 ```bash
 $ helm upgrade soketi \
     --install \
-    --version=1.0.1 \
+    --version=1.0.2 \
     soketi/soketi
 ```
 

charts/soketi/templates/deployment.yaml

@@ -73,7 +73,7 @@ spec:
             - name: KUBE_CONNECTION
               value: cluster
             - name: SERVER_PORT
-              value: "{{ .Values.service.port }}"
+              value: "9601"
             - name: MEMORY_PERCENT
               value: "{{ .Values.networkWatcher.threshold }}"
             - name: CHECKING_INTERVAL

charts/soketi/values.yaml

@@ -19,7 +19,7 @@ app:
   image:
     repository: quay.io/soketi/soketi
     pullPolicy: IfNotPresent
-    tag: "1.3.0-16-alpine"
+    tag: "1.4-16-alpine"
     # You can use distroless to avoid Remote Code Execution attacks in-cluster.
     # https://github.com/soketi/soketi/pull/178
     # tag: "1.3-16-distroless"