bug: wrong default port 7575 vs 3000

[ZashIn]

Chart Version

8.16.1

Bug Description

The default port in values.yaml is set to 7575, but the homarr image is actually exposing port 3000, the NextJS default port.
So with the default values in this chart, the ready-/livenessProbe and the connection to the UI fails.
The log showing port 3002 did also not not help debugging this:

Related: homarr-labs/homarr#2154

PR follows

values.yaml

apiVersion: helm.cattle.io/v1
kind: HelmChart
metadata:
  name: homarr
  namespace: kube-system
  labels:
    app.kubernetes.io/name: homarr
spec:
  repo: https://homarr-labs.github.io/charts/
  chart: homarr
  targetNamespace: homarr
  valuesContent: |-
    image:
      repository: ghcr.io/homarr-labs/homarr
      pullPolicy: IfNotPresent
      tag: "latest"

    securityContext:
      runAsNonRoot: true
      # runAsUser: ...
      # runAsGroup: ...

    persistence:
      homarrDatabase:
        enabled: true
        storageClassName: "shared-folder"
        size: "50Mi"

    envSecrets:
      dbEncryption:
        existingSecret: "db-encryption"
        key: "db-encryption-key"

    containerPorts:
      http:
        port: 7575
        protocol: TCP

    service:
        enabled: true
        type: ClusterIP
        ports:
          app:
            port: 7575
            targetPort: http
            protocol: TCP

    livenessProbe:
      failureThreshold: 3
      initialDelaySeconds: 20
      timeoutSeconds: 1
      periodSeconds: 20
      httpGet:
        path: /api/health/live
        port: 7575

    readinessProbe:
      failureThreshold: 3
      initialDelaySeconds: 20
      timeoutSeconds: 1
      periodSeconds: 20
      httpGet:
        path: /api/health/ready
        port: 7575

Relevant log output

# homarr pod log:
Tasks web server started successfully module="tasksMain" port="3002"

# Kubernetes Event:
Readiness probe failed: Get "http://<pi>:7575/api/health/ready": dial tcp <ip>:7575: connect: connection refused

[oben01]

@ZashIn thank you for raising this issue. @manuel-rw did u guys change the default port ?

[manuel-rw]

No, we changed no ports. I don't believe you must update any ports. 3000 will be wrong. With 3000 you'll break WebSocket. Use the Ngingx Port (7575 by default)

[ZashIn]

Ngingx could be the problem, similar to this issue, since I am running the pod with a security context and as non root. I will double check later and test if the proxy runs correctly.