Site displays Service Unavailable after helm chart install

Self-host Installation
1

Screenshot 2025-03-04 115055
Screenshot 2025-03-04 1150551188×902 19.4 KB

After helm chart installation of penpot, this is a screenshot of what I get when I attempt to reach the site. As far as values… here’s what I’m passing… but essentially, I’m using AWS RDS - postgreSQL for database, S3 for assets (I replaced sensitive info with generic text). I’m using Istio for the Service Mesh… so I don’t enable ingress through the values file. I just manually create an istio virtual service that points to the penpot.penpot.svc.cluster.local on port 8080; Then I set DNS to point to my AWS NLB that then forwards the request to the virtualservcie for that https URL. All the logs for each of the pods… look clean on startup, no errors. However, I do get this error on the front-end pod, when attempting to reach the URL or click the login button:

penpot-frontend 127.0.0.6 - - [04/Mar/2025:17:49:13 +0000] "GET /api/rpc/command/get-profile HTTP/1.1" 503 95 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.0.0 Safari/537.36"

Values:

      global:
        postgresqlEnabled: false
        redisEnabled: true
      config:
        publicUri: "https://myURL"
        flags: "enable-registration enable-login-with-password disable-email-verification"
        apiSecretKey: "my-secret-key"
        telemetryEnabled: false
        postgresql:
          host: "AWS_HOST_ADDRESS"
          port: 5432
          username: "penpot_su"
          password: "penpot_password"
          database: "penpot"
        assets:
          storageBackend: "assets-s3"
          s3:
            accessKeyID: "access_key_id"
            secretAccessKey: "secret_key"
            region: "us-gov-east-1"
            bucket: "bucket_name"
            endpointURI: "s3://bucket_name.s3.us-gov-east-1.amazonaws.com/"
      backend:
        replicaCount: 1
      frontend:
        replicaCount: 1
      exporter:
        replicaCount: 1
      persistence:
        assets:
          enabled: true
          storageClass: gp3
          size: 20Gi
          accessModes:
            - ReadWriteOnce
        exporter:
          enabled: true
          storageClass: gp3
          size: 10Gi
          accessModes:
            - ReadWriteOnce
2

Ah… so I think it’s because I have to make multiple routes (path-based) in an Istio Virtual Service. Is there a good list of the different paths and target pods/ports? Or anybody that has deployed the nginx ingress… anybody know what the default routes are? I did find this… just don’t know if this is what I should use to reference: penpot-kubernetes/kubernetes.manifest.yaml at main · degola/penpot-kubernetes