[piped] Default Helm deployment results in broken setup, misconfiguration?

[aleksasiriski]

Helm chart name

piped

Helm chart version

2.0.1

Container name

frontend

Container tag

default

Description

After deploying with Helm to namespace community and setting up my Ingresses externally in the same namespace, I can get to the frontend but it results in always loading "Trending" and if I go to preferences it just flashes for a second and then disappears.

Expected result

A working setup or at least something in the logs to point me in the right direction.

Helm values to reproduce

frontend:
  env:
    BACKEND_HOSTNAME: pipedapi.piped.mydomain.com
backend:
  config:
    PROXY_PART: https://ytproxy.piped.mydomain.com
    API_URL: https://pipedapi.piped.mydomain.com
    FRONTEND_URL: https://piped.mydomain.com
    COMPROMISED_PASSWORD_CHECK: true
    DISABLE_REGISTRATION: true
    database:
      connection_url: jdbc:postgresql://cloudnative-pg-rw.cnpg-system.svc.cluster.local:5432/piped
      driver_class: org.postgresql.Driver
      dialect: org.hibernate.dialect.PostgreSQLDialect
      username: piped
      password: mypipeddbpassword
ingress:
  main:
    enabled: false
  backend:
    enabled: false
  ytproxy:
    enabled: false
postgresql:
  enabled: false

Additional Information

Here is my ingress:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: piped
  namespace: community
  annotations:
    cert-manager.io/cluster-issuer: letsencrypt-prod
    traefik.ingress.kubernetes.io/router.entryPoints: websecure
    traefik.ingress.kubernetes.io/router.tls: "true"
spec:
  tls:
  - hosts:
    - "piped.mydomain.com"
    - "*.piped.mydomain.com"
    secretName: piped-mydomain-com
  rules:
  - host: "piped.mydomain.com"
    http:
      paths:
      - pathType: Prefix
        path: "/"
        backend:
          service:
            name: piped-frontend
            port:
              number: 80
  - host: "pipedapi.piped.mydomain.com"
    http:
      paths:
      - pathType: Prefix
        path: "/"
        backend:
          service:
            name: piped-backend
            port:
              number: 8080
  - host: "ytproxy.piped.mydomain.com"
    http:
      paths:
      - pathType: Prefix
        path: "/"
        backend:
          service:
            name: piped-ytproxy
            port:
              number: 8080

Repo link

No response

[aleksasiriski]

I can see these in firefox:

[aleksasiriski]

Ok it started working with this config:

frontend:
  env:
    BACKEND_HOSTNAME: pipedapi.piped.mydomain.com
backend:
  config:
    PORT: 8080
    NUM_WORKERS: 2
    PROXY_PART: https://ytproxy.piped.mydomain.com
    API_URL: https://pipedapi.piped.mydomain.com
    FRONTEND_URL: https://piped.mydomain.com
    COMPROMISED_PASSWORD_CHECK: true
    DISABLE_REGISTRATION: true
    database:
      connection_url: jdbc:postgresql://cloudnative-pg-rw.cnpg-system.svc.cluster.local:5432/piped
      driver_class: org.postgresql.Driver
      dialect: org.hibernate.dialect.PostgreSQLDialect
      username: piped
      password: mypipeddbpassword
ingress:
  main:
    enabled: false
  backend:
    enabled: false
  ytproxy:
    enabled: false
postgresql:
  enabled: false

[samip5]

If you had used the ingress definitions inside the values, it would have worked out of the box.