-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
[piped] Default database results in non working piped, database config isn't read correctly #2
Comments
Hi, Thank you for reporting. I haven't tried cloudnative, but that error does indeed suggest that password at least is not getting to the backend config right. I will look into it. |
I've also tried with DigitalOcean Managed Postgres (ver 15, 14 and 11) |
I have located that the backend configmap is indeed missing username and password fields completely so the error makes perfect sense. |
Then again, my own deployment with the default database does work.
|
Should be fixed in chart 2.0.1, to be available shortly. |
Yep, username and password now work -> cloudnative-pg works! |
Helm chart name
piped
Helm chart version
2.0.0
Container name
piped-backend
Container tag
default
Description
Default database results in non working piped deployment. Frontend and ytproxy seem to work fine but backend doesn't return anything to front for it to display any content, so it's just stuck there.
Also, when trying to use external postgresql backend errors out with this:
The server requested SCRAM-based authentication, but no password was provided.
So it seems that the password field in values.yaml isn't being properly used.
Expected result
Helm chart with PROXY_PART, API_URL and FRONTEND_URL to just work™ OOTB. For Postgres config to work as well as the default.
Helm values to reproduce
Additional Information
No response
Repo link
No response
The text was updated successfully, but these errors were encountered: