Unable to connect to Default Project

[lopes221]

Bug report

Describe the bug

Supabase keeps loading but never connect to default project.

To Reproduce

Follow this steps
https://github.com/supabase-community/supabase-kubernetes/blob/main/charts/supabase/README.md

Everything is deployed nicely.
Then I portforward my supabase-studio to see the interface, then I click on default project and and keeps "connecting to Default Project" but never finishes, so I decided in Google Chrome check the network and I've got the below.
I tried updating this variable which is SUPABASE_PUBLIC_URL, but still keep same issue.

Expected behavior

I expected to be able to load the default project.

Screenshots

System information

• OS: [e.g. macOS, Windows]
• Browser (if applies) [e.g. chrome, safari]
• Version of supabase-js: [e.g. 6.0.2]
• Version of Node.js: [e.g. 10.10.0]

Additional context

helm version
version.BuildInfo{Version:"v3.13.1", GitCommit:"3547a4b5bf5edb5478ce352e18858d8a552a4110", GitTreeState:"clean", GoVersion:"go1.20.8"}

[DeanHnter]

Hi, im basically reviewing this issue myself. I think the issue resides in the configuration of the ingresses as the front-end is sending requests to the localhost in the example helm-chart which obviously can only happen if youre running it all on a local kubernetes cluster and wont work once deployed somewhere in production. Like you mentioned I think you must make sure your nginx ingresses that are in the example are configured/deployed and working correctly before also and then subsequently changing the url from http://localhost.

The other similar issue im having related to yours is also that once the ingresses are configured correctly it seems the default kong setup has routing issues:

{"message":"no Route matched with those values"}

I imagine there is a few flaws somewhere in the example provided but i might be wrong maybe someone could clear this up

[lopes221]

Hi @DeanHnter
I fixed the issue by using the newest supabase image rather than one included here in this chart, just take the newest tag.

[RaphaelBossek]

This related to supabase/supabase#10707 because the tag for sperbase-reset is set to v9.0.1.20220717 which is too old.