-
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
db host fix #8
db host fix #8
Conversation
pull policy IfNotPresent when only latest tag is available makes it unable to update on 1-node cluster |
@JuniorJPDJ I think the consensus is that a particular version of a chart targets a certain version of the app and not "latest". If you want to track latest and update accordingly, there are solutions in the GitOps universe like ArgoCD, Flux, Keel etc. To summarize, switching from a pinned version to latest should be an explicit action by the user, and not the chart's default. |
This is true, but changing pull policy to achieve that is not the best idea as you have no control over when it updates anyway. |
The default config for db.host is "invidious-postgresql" which only works when the chart is installed with a release name of "invidious". Changed the default db.host value to "${release_name}-postgresql".
Ok then, I left only the db host fix. |
Can you please also bump the chart version? |
done. |
Thank you for your contribution! |
The default config for db.host is "invidious-postgresql" which only
works when the chart is installed with a release name of "invidious".
Changed the default db.host value to "${release_name}-postgresql". (could fix #3)
Also changed pullPolicy to IfNotPresent.