Open
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 of api-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: ENTERPRISE
redis:
networkPolicy:
enabled: false
mongodb:
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/helm
helm upgrade --install -n poc lowcoder-test . -f values-test.yaml
-
Access Lowcoder in browser at URL
https://lowcoder-test.poc.<my-domain>.com -
Check logs of
lowcoder-test-api-servicePod (see the full logfilelowcoder-error.logattached)
Environment
$ kubectl version
Client Version: v1.33.1
Kustomize Version: v5.6.0
Server Version: v1.30.6+rke2r1
$ helm version
version.BuildInfo{Version:"v3.17.3", GitCommit:"e4da49785aa6e6ee2b86efd5dd9e43400318262b", GitTreeState:"clean", GoVersion:"go1.24.2"}
Additional Information
Same behavior happens when global.workspaceMode is set to SAAS.
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
Type
Projects
Status
👀 In review