[Bug] Appsmith server is unavailable after installing with Kubernetes install script

Description

The home page dose not work after installing using k8s.install.sh.

[What happened] It can not display the editor page.

Steps to reproduce the behaviour:

1. install using k8s.install.sh
2. kubectl port-forward service/appsmith-editor 80:80
3. open the page: http://localhost
4. Allways a error page with “Appsmith server is unavailable”

All pods are ok.

redis-statefulset-0                         1/1     Running   0          17m
mongo-statefulset-0                         1/1     Running   0          17m
appsmith-internal-server-79c999fbb6-jf8jn   1/1     Running   0          10m
appsmith-editor-559b988c66-hnm5h            1/1     Running   0          10m

Important Details

[zdb999]

I had this issue. The problem is that the front end expects to talk to the back end service through from the browser on certain routes. This means that Appsmith doesn’t work on Kubernetes through port forwarding, you have to set up an ingress controller.

If you want to protect it from the outside world, you can disable account sign ups and/or use your reverse proxy to add another auth layer (I used basic auth, with TLS enabled.) If you have access to the actual machines in the Kubernetes cluster, you could also probably access it through a VPN that sits outside Kubernetes.

I have a Helm chart with my configuration. It’s not fit for public consumption right now, but I could probably clean it up and release it if people are interested.

[Hokwang]

@zdb999 please look at https://github.com/appsmithorg/appsmith/pull/2558 and you can provide helm chart first version.