Passing the torch on supabase-kubernetes

[arpagon]

Hey everyone,

I’ve been maintaining supabase-kubernetes, but I want to be transparent: I no longer have the time to properly maintain the project. Because of that, issues and PRs haven’t been getting the attention they deserve.

The good news is that Supabase has always been very supportive of self-hosting (I can say this from first-hand experience), and recently they even brought in a Head of Self-Hosting @kiwicopple https://x.com/kiwicopple/status/1971677845824106700

I’d like to open the door for new maintainers from the community who’d like to continue building on this work.
I’m also happy to provide context, review contributions when possible, and help transition things smoothly.

Thanks a lot to everyone who has contributed so far. If you’re interested in maintaining or contributing more actively, please comment here

[bartcode]

I might be able to help out, since I've actually made a working Supabase Helm chart myself.

[nilgaar]

I've been willing to contribute and get involved in this repo for a long time. Count me in. 🛫💪

[kastakhov]

Since I'm working on a supabase helm chart fork as well, I might help with maintaining here as well as merge some improvements from my side.

[ryanotella]

I'd be keen as well. I'd commit to 12 months at least.

[aantti]

Hey, more like a "lead" (of self-hosting) here :) Appreciate your work @arpagon and thanks everyone for chiming in. Has anyone here been part of Supabase contributors yet? (If so - reach out via Slack.) Otherwise, could I possibly ask potential maintainers to apply/leave contacts via https://supabase.com/open-source/contributing/supasquad#why-supasquad ? Please include some minimal context referring this issue 🖖

[aantti]

Ok, if anyone has applied and didn't have a reply, let me know. In the meantime, I'd be happy to spend some of my timeslots on this as an interim maintainer. We are getting more and more requests for this repo to be solid, and I'd prefer to start moving things forward. Notably, PR #131 via @luizfelmach looks great as a restart.

[aantti]

Quick update: Very happy to announce that @luizfelmach has officially joined as a SupaSquad community maintainer for this repository. We have already started work on Luiz' PR #131 to address the accumulated issues.

To bring this repository back to a usable state as quickly as possible, we are planning to merge PR #131 very soon. This PR addresses a significant number of broken services and has already received positive feedback from the community.

Luiz will then review older issues and PRs to see what remains to be done on top of this new baseline.

To everyone who has been waiting - appreciate your patience. We know this update is long overdue, and we're excited to get this repo working for you again.

[luizfelmach]

Thank you, @aantti. really appreciate the trust and the support.

I agree that merging #131 as a new baseline makes sense, and I’m happy to help move things forward from there. After that, I’ll start reviewing the older issues and PRs to see what still applies on top of this new state.

Excited to get this repo back into a solid and usable shape 🚀

[aantti]

Ok, the repo has been updated with @luizfelmach's changes :)