Deployment on Kubernetes and dependencies

[codekoala]

I'm curious to try deploying this incredible tool in my personal k3s cluster. I've looked through the docker compose file, and I see most services are related to supabase. I have to ask: how dependent is Kurrier on these supabase services? Can it still function correctly if I only want to use postgres proper?

[krokhale]

I believe there are 6 Kurrier and 8 Supabase containers. Unfortunately there is tons of stuff including authentication/file management/secrets encryption etc that would have to be built (which isn't too hard but it does add more surface area for potential bugs and would consume more time).

I feel it would make more sense to push forward and build stuff like Kurrier Drive for storage (Upcoming soon) rather than reinvent the wheel with redoing what Supabase does anyway. So switching to vanilla postgres, though appealing might not be very practical considering what Kurrier plans to build/support in the longer term.

[codekoala]

That makes complete sense to me. Thank you for the response and context! It is easy enough to deploy supabase on kubernetes. Mostly I was asking because I already have a postgres instance on my NAS that I tend to use for things I deploy in my local k3s cluster.

I am going to try to sneak some time during the next few days to come up with a helm chart that can deploy Kurrier on kubernetes. I'll let you know how that goes :)