Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement Service Binding Mechanism #41

Open
jcoresongres opened this issue Apr 3, 2023 · 0 comments
Open

Implement Service Binding Mechanism #41

jcoresongres opened this issue Apr 3, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@jcoresongres
Copy link

Feature request

Supabase could implement Kubernetes' Service Binding mechanism (https://servicebinding.io/) to avoid having to explicitly add the credentials to Supabase configuration, and instead having Kubernetes inject them, materializing inside of Supabase's container as files with a specific structure and path. Service Binding is harmless on non-K8s environments (Supabase only needs to add some trivial code to detect if configuration files with Service Binding conventions exist, and if so reading them). This would enhance the UX as no credentials need to be hardcoded anywhere nor stored in vaults.

@jcoresongres jcoresongres added the enhancement New feature or request label Apr 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant