- Notifications
You must be signed in to change notification settings - Fork254
Open
Assignees
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
When Lowcoder is deployed using Helm chart, 404 NOT_FOUND error appears in logs ofapi-service Pod when application is accessed.
Expected Behavior
No error appears in logs.
Steps to reproduce
- Create
values-test.yamlfile with following content:
global: config: workspaceMode: ENTERPRISEredis: networkPolicy: enabled: falsemongodb: networkPolicy: enabled: false architecture: standalone service: nameOverride: "lowcoder-test-mongodb"ingress: enabled: true className: nginx-private annotations: cert-manager.io/cluster-issuer: letsencrypt hosts: - host: lowcoder-test.poc.<my-domain>.com paths: - path: / pathType: ImplementationSpecific tls: - secretName: lowcoder-test-ingress-tls hosts: - lowcoder-test.poc.<my-domain>.com- Deploy Application using Helm chart with following command:
cd deploy/helmhelm upgrade --install -n poc lowcoder-test . -f values-test.yamlAccess Lowcoder in browser at URL
https://lowcoder-test.poc.<my-domain>.comCheck logs of
lowcoder-test-api-servicePod (see the full logfilelowcoder-error.logattached)
Environment
$ kubectl versionClient Version: v1.33.1Kustomize Version: v5.6.0Server Version: v1.30.6+rke2r1$ helm versionversion.BuildInfo{Version:"v3.17.3", GitCommit:"e4da49785aa6e6ee2b86efd5dd9e43400318262b", GitTreeState:"clean", GoVersion:"go1.24.2"}Additional Information
Same behavior happens whenglobal.workspaceMode is set toSAAS.
The error does not seem to break any application functionality, but it clutters the logs since it is almost 500 lines long.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
👀 In review