search

supabase-community / supabase-kubernetes

Helm 3 charts to deploy a Supabase on Kubernetes
Apache License 2.0
386 stars 110 forks source link

Replace Alpine for base images #40

Open jcoresongres opened 1 year ago

jcoresongres commented 1 year ago

Bug report

Describe the bug

Some of the Docker images used in the Helm chart are based on Alpine which has caused some connectivity (DNS) issues (see https://martinheinz.dev/blog/92) when trying out Supabase on one of our engineer's computers. Changing these Supabase images to something that wasn't based on Alpine solved the issue. This might be something to consider (or at least document) for the users.

The current error was:

supabase-db.default.svc.cluster.local:5432 - no response
Waiting for database to start...
supabase-db.default.svc.cluster.local:5432 - no response
Waiting for database to start...
TristisOris commented 11 months ago

got same problem. also that recomended for Stackgres cluster installation.

drpsyko101 commented 9 months ago

Does this related to k3s-io/k3s#6132? I couldn't replicate this issue on minikube on debian-based OS. Do you have a sample environment setup that I can replicate?